★★DigiByte|极特币★★[DGB]✔ Core v6.16.5.1 - DigiShield, DigiSpeed, Segwit

[Jumbley]

Resuming: "We have no f*cking idea and our reply has nothing to do with the ticket you submitted"

Edit: poking around I found a file that contains a heck of data and something that resembles a privkey; yet, when importing it into DGB core it returns "Invalid private key encoding (code -5)"

%AppData%\Local\Google\Chrome\User Data\WHATEVER_YOUR_PROFILE_IS\Local App Settings\lpmijfncbdjhcbockhipcncnhfgghkoj\000003.LOG

There's several "keys" in there, including endryption ones. Perhaps someone can guide me into what encryption it's applied to my key?
(Very frikking crappy if my key and encryption file are stored at the same file)

Here's how to get a backup of your chrome app wallet:
- Download Chrome Beta 52.0.2743.33
- Open Chrome App for the Digi wallet
- You'll get an error "Error at wallet service: insight error", click ok
- Click on the gear icon in the upper right hand corner
- Click Advanced, Export Wallet, pick a password, confirm password, click on Download.
- The json file with the encrypted key/s will be in your windows download folder.

Hope that helps someone else as well  

Yes, now I've a json encrypted file that is not imported by any wallet. Great.

Any tool where I can put the salt, password and string at to get MY FUCKING PRIVKEY? (and finally be able to import it at DGB core)

See, that’s what I don’t get. Someone attempts to help another community member and in return is repaid with abuse and bad language. This kind of attitude is soul destroying as well as futile.

[1714747643]

1714747643

[1714747643]

1714747643

[1714747643]

1714747643

[1714747643]

1714747643

[1714747643]

1714747643

[RenzoARG]

Resuming: "We have no f*cking idea and our reply has nothing to do with the ticket you submitted"

Edit: poking around I found a file that contains a heck of data and something that resembles a privkey; yet, when importing it into DGB core it returns "Invalid private key encoding (code -5)"

%AppData%\Local\Google\Chrome\User Data\WHATEVER_YOUR_PROFILE_IS\Local App Settings\lpmijfncbdjhcbockhipcncnhfgghkoj\000003.LOG

There's several "keys" in there, including endryption ones. Perhaps someone can guide me into what encryption it's applied to my key?
(Very frikking crappy if my key and encryption file are stored at the same file)

Here's how to get a backup of your chrome app wallet:
- Download Chrome Beta 52.0.2743.33
- Open Chrome App for the Digi wallet
- You'll get an error "Error at wallet service: insight error", click ok
- Click on the gear icon in the upper right hand corner
- Click Advanced, Export Wallet, pick a password, confirm password, click on Download.
- The json file with the encrypted key/s will be in your windows download folder.

Hope that helps someone else as well 

Yes, now I've a json encrypted file that is not imported by any wallet. Great.

Any tool where I can put the salt, password and string at to get MY FUCKING PRIVKEY? (and finally be able to import it at DGB core)

See, that’s what I don’t get. Someone attempts to help another community member and in return is repaid with abuse and bad language. This kind of attitude is soul destroying as well as futile.

Telling me to get a backup is not helping... It's stating that air is for breathing. Obviously, any crypto user makes backups of their keys 30 seconds after getting a wallet. Obvious.

I didnt expect that this shittocurrency would have no cross compatibility in their wallets (cmon, copying any other crypto scheme of work is not that hard; why get original and fail at it?)

[CryR]

Digibyte again on the road.

[Jumbley]

My point obviously wasted, thank you for your suggestion.

[Jumbley]

New CPU available for your miners and wallets guys. 
http://www.ebay.co.uk/itm/Xeon-E5-2698-v4-20x-2-20GHz-Socket-2011-3-/282019105739?_trksid=p2141725.m3641.l6368

[Telenong]

Quick update! After officially partnering with Microsoft (Biz Spark +) we have received $120K USD in free hosting over the next 12 months on Azure. We are migrating all DigiByte servers to more improved hardware! This includes, DigiByte Gaming, DigiHash, DigiExplorer, Wallet services, Seed nodes and more! Stay tuned as we progress on these services and others.

And yes core protocol upgrades are underway!

This service is free to any startup: https://blogs.microsoft.com/firehose/2015/06/16/120000-per-year-of-free-azure-cloud-credits-will-go-to-startups-in-bizspark-plus-program/#sm.001ymx2gs1cfndafzcn1734q0erct

if all easy as you say, so when vcash join with bizspark? i want see your claim dude

Now that M$ suckered you into deploying onto their centralized architecture what happens after 12 months? Who pays these costly M$ bills? Are you aware of the cost of M$ servers?

Why do you want to know the people's business?, i think you knew really happen but want people confused about that

Lastly, any input on this? https://v.cash/forum/threads/basic-math-proves-digibyte-cannot-scale-debunk-it.447/#post-6509

I'm not known for trolling, just truth seeking, I own digibyte for years and seek some simple answers and explanations. Regards.

I heard DGB team already answered anything your question, but you actually block them, you are very unprofessional behavior at all.

[Telenong]

Quick update! After officially partnering with Microsoft (Biz Spark +) we have received $120K USD in free hosting over the next 12 months on Azure. We are migrating all DigiByte servers to more improved hardware! This includes, DigiByte Gaming, DigiHash, DigiExplorer, Wallet services, Seed nodes and more! Stay tuned as we progress on these services and others.

And yes core protocol upgrades are underway!

This service is free to any startup: https://blogs.microsoft.com/firehose/2015/06/16/120000-per-year-of-free-azure-cloud-credits-will-go-to-startups-in-bizspark-plus-program/#sm.001ymx2gs1cfndafzcn1734q0erct

Will you share a copy of your mutual NDA as proof of partnership?

Now that M$ suckered you into deploying onto their centralized architecture what happens after 12 months? Who pays these costly M$ bills? Are you aware of the cost of M$ servers?

FYI: Your SSL website is accessing plaintext data: https://www.digibyte.co/

Lastly, any input on this? https://v.cash/forum/threads/basic-math-proves-digibyte-cannot-scale-debunk-it.447/#post-6509

I'm not known for trolling, just truth seeking, I own digibyte for years and seek some simple answers and explanations. Regards.

One thing is for sure if I ever wanted to sell my underwear with skid marks on I am sure Jared could find a buyer.

Do not be jealous , marketing it sells, including your underwear

[RenzoARG]

Now, after installing chrome beta as recommended the wallet starts, yet does not work (Insight error).

 

Seriously. I need a simple wallet backup aes.json decryptor. I have the password, but the file can only be imported into the chrome extension wallet. Technically they are lost if the wallet does not work.

[bugsywugsy]

Well it would be nice to get the facts straight on the transaction limitations because if there is something even half as sever as mr connor is claiming, then the network is indeed vulnerable.

Can't we use an example situation and discuss how it would play out?

[DigiByte]

This service is free to any startup: https://blogs.microsoft.com/firehose/2015/06/16/120000-per-year-of-free-azure-cloud-credits-will-go-to-startups-in-bizspark-plus-program/#sm.001ymx2gs1cfndafzcn1734q0erct

Will you share a copy of your mutual NDA as proof of partnership?

This was shared long ago on Twitter. Same agreement used for Azure BaaS.

Lastly, any input on this? https://v.cash/forum/threads/basic-math-proves-digibyte-cannot-scale-debunk-it.447/#post-6509
I'm not known for trolling, just truth seeking, I own digibyte for years and seek some simple answers and explanations. Regards.
"
DigiByte has a 15 second block timing. I can create a single DigiByte transaction that is 998,000 Kilobytes (@ zero cost) in size that takes a modern computer 43 seconds to validate. That said, if you run these types of performance tests against DigiByte's network slower nodes will get backed up further and further forking off onto their own chains. The only nodes on the "main chain" would be extremely fast nodes that can validate these blocks in < 15 seconds. This would split the network into 100's of disagreeing networks.

Disclaimer: This is a 100% technical post and I'd like someone to debunk it with provable technical facts. Thanks!"

First thank you for your concern and for supporting DigiByte. Now let's answer your question.

1) You cannot create a single 998,000 KB TX for free and expect any node to relay it. Every DGB client out there has this code in it: https://github.com/digibyte/digibyte/blob/master/src/main.h#L74

Code:

/** The maximum size for transactions we're willing to relay/mine */
static const unsigned int MAX_STANDARD_TX_SIZE = 100000;

In case you are wondering that is 100 KB or 0.1 MB. No way you could actually create a TX that large and get it relayed.

Bloating the network with multiple transactions gets very expensive very fast (as will be demonstrated below). 

2) Each algo has a block timing of 1 min 15 seconds. Microsoft research showed on the BTC network it takes an average of 6.5 seconds for 50% of nodes to receive a new block. 95% in 40 seconds with a mean of 12 seconds. So our 1 min 15 second individual algo block time is well within this time frame.

http://www.tik.ee.ethz.ch/file/49318d3f56c1d525aabf7fda78b23fc0/P2P2013_041.pdf

In order to 51% attack DGB and fork the chain you would need to take over 93% of SHA256 and 51% of the other 4 algos at the same time. (virtually impossible) or else the difficulty adjustment (Multi-Shield) will easily prevent it.

3) With future modifications to DigiByte core things will get even faster as far as block validations are concerned (secp256k1)

Finally here is a screen shot from the live DigiByte network test after DigiSpeed (we did many similar tests internally on a test network before releasing the hard fork).

It is very difficult and expensive to send this many TX's in such a short amount of time. We pushed through almost 10,000 TX's in just over a minute and the network handled it just fine. In fact, the main worldwide DigiByte network performed better than our internal test network.

Check these blocks for yourself on DigiExplorer: http://digiexplorer.info/block/e5ff5243c291d088e286bbe5ea449100487c6346667fcfc84f89d85971074880



Now compare that to this recent snap shot of BTC blockchain with full blocks. It took over an hour just to process 5,000 TX's.

So DGB easily hits 10,000 TX's in 1 min.  BTC takes over an hour for 5,000 TX's. 

The proof is in the Blockchain.

[DigiByte]

Now, after installing chrome beta as recommended the wallet starts, yet does not work (Insight error).

 

Seriously. I need a simple wallet backup aes.json decryptor. I have the password, but the file can only be imported into the chrome extension wallet. Technically they are lost if the wallet does not work.

Insight error should be fixed Are you on Android?

You can try this: https://github.com/bitpay/copay-recovery

Although we have never tried, but in theory it should work. We will look into forking this.

[IloveDigibyte]

This service is free to any startup: https://blogs.microsoft.com/firehose/2015/06/16/120000-per-year-of-free-azure-cloud-credits-will-go-to-startups-in-bizspark-plus-program/#sm.001ymx2gs1cfndafzcn1734q0erct

Will you share a copy of your mutual NDA as proof of partnership?

This was shared long ago on Twitter. Same agreement used for Azure BaaS.

Lastly, any input on this? https://v.cash/forum/threads/basic-math-proves-digibyte-cannot-scale-debunk-it.447/#post-6509
I'm not known for trolling, just truth seeking, I own digibyte for years and seek some simple answers and explanations. Regards.
"
DigiByte has a 15 second block timing. I can create a single DigiByte transaction that is 998,000 Kilobytes (@ zero cost) in size that takes a modern computer 43 seconds to validate. That said, if you run these types of performance tests against DigiByte's network slower nodes will get backed up further and further forking off onto their own chains. The only nodes on the "main chain" would be extremely fast nodes that can validate these blocks in < 15 seconds. This would split the network into 100's of disagreeing networks.

Disclaimer: This is a 100% technical post and I'd like someone to debunk it with provable technical facts. Thanks!"

First thank you for your concern and for supporting DigiByte. Now let's answer your question.

1) You cannot create a single 998,000 KB TX for free and expect any node to relay it. Every DGB client out there has this code in it: https://github.com/digibyte/digibyte/blob/master/src/main.h#L74

Code:

/** The maximum size for transactions we're willing to relay/mine */
static const unsigned int MAX_STANDARD_TX_SIZE = 100000;

In case you are wondering that is 100 KB or 0.1 MB. No way you could actually create a TX that large and get it relayed.

Bloating the network with multiple transactions gets very expensive very fast (as will be demonstrated below). 

2) Each algo has a block timing of 1 min 15 seconds. Microsoft research showed on the BTC network it takes an average of 6.5 seconds for 50% of nodes to receive a new block. 95% in 40 seconds with a mean of 12 seconds. So our 1 min 15 second individual algo block time is well within this time frame.

http://www.tik.ee.ethz.ch/file/49318d3f56c1d525aabf7fda78b23fc0/P2P2013_041.pdf

In order to 51% attack DGB and fork the chain you would need to take over 93% of SHA256 and 51% of the other 4 algos at the same time. (virtually impossible) or else the difficulty adjustment (Multi-Shield) will easily prevent it.

3) With future modifications to DigiByte core things will get even faster as far as block validations are concerned (secp256k1)

Finally here is a screen shot from the live DigiByte network test after DigiSpeed (we did many similar tests internally on a test network before releasing the hard fork).

It is very difficult and expensive to send this many TX's in such a short amount of time. We pushed through almost 10,000 TX's in just over a minute and the network handled it just fine. In fact, the main worldwide DigiByte network performed better than our internal test network.

Check these blocks for yourself on DigiExplorer: http://digiexplorer.info/block/e5ff5243c291d088e286bbe5ea449100487c6346667fcfc84f89d85971074880



Now compare that to this recent snap shot of BTC blockchain with full blocks. It took over an hour just to process 5,000 TX's.

So DGB easily hits 10,000 TX's in 1 min.  BTC takes over an hour for 5,000 TX's. 

The proof is in the Blockchain.

Jared you are the best. Best marketing person and the best developer. Crypto_beast will be put to rest. I was getting worried he might be telling the truth.

[Telenong]

This service is free to any startup: https://blogs.microsoft.com/firehose/2015/06/16/120000-per-year-of-free-azure-cloud-credits-will-go-to-startups-in-bizspark-plus-program/#sm.001ymx2gs1cfndafzcn1734q0erct

Will you share a copy of your mutual NDA as proof of partnership?

This was shared long ago on Twitter. Same agreement used for Azure BaaS.

Lastly, any input on this? https://v.cash/forum/threads/basic-math-proves-digibyte-cannot-scale-debunk-it.447/#post-6509
I'm not known for trolling, just truth seeking, I own digibyte for years and seek some simple answers and explanations. Regards.
"
DigiByte has a 15 second block timing. I can create a single DigiByte transaction that is 998,000 Kilobytes (@ zero cost) in size that takes a modern computer 43 seconds to validate. That said, if you run these types of performance tests against DigiByte's network slower nodes will get backed up further and further forking off onto their own chains. The only nodes on the "main chain" would be extremely fast nodes that can validate these blocks in < 15 seconds. This would split the network into 100's of disagreeing networks.

Disclaimer: This is a 100% technical post and I'd like someone to debunk it with provable technical facts. Thanks!"

First thank you for your concern and for supporting DigiByte. Now let's answer your question.

1) You cannot create a single 998,000 KB TX for free and expect any node to relay it. Every DGB client out there has this code in it: https://github.com/digibyte/digibyte/blob/master/src/main.h#L74

Code:

/** The maximum size for transactions we're willing to relay/mine */
static const unsigned int MAX_STANDARD_TX_SIZE = 100000;

In case you are wondering that is 100 KB or 0.1 MB. No way you could actually create a TX that large and get it relayed.

Bloating the network with multiple transactions gets very expensive very fast (as will be demonstrated below). 

2) Each algo has a block timing of 1 min 15 seconds. Microsoft research showed on the BTC network it takes an average of 6.5 seconds for 50% of nodes to receive a new block. 95% in 40 seconds with a mean of 12 seconds. So our 1 min 15 second individual algo block time is well within this time frame.

http://www.tik.ee.ethz.ch/file/49318d3f56c1d525aabf7fda78b23fc0/P2P2013_041.pdf

In order to 51% attack DGB and fork the chain you would need to take over 93% of SHA256 and 51% of the other 4 algos at the same time. (virtually impossible) or else the difficulty adjustment (Multi-Shield) will easily prevent it.

3) With future modifications to DigiByte core things will get even faster as far as block validations are concerned (secp256k1)

Finally here is a screen shot from the live DigiByte network test after DigiSpeed (we did many similar tests internally on a test network before releasing the hard fork).

It is very difficult and expensive to send this many TX's in such a short amount of time. We pushed through almost 10,000 TX's in just over a minute and the network handled it just fine. In fact, the main worldwide DigiByte network performed better than our internal test network.

Check these blocks for yourself on DigiExplorer: http://digiexplorer.info/block/e5ff5243c291d088e286bbe5ea449100487c6346667fcfc84f89d85971074880



Now compare that to this recent snap shot of BTC blockchain with full blocks. It took over an hour just to process 5,000 TX's.

So DGB easily hits 10,000 TX's in 1 min.  BTC takes over an hour for 5,000 TX's. 

The proof is in the Blockchain.

a good explanation dev, thank you

[mhbays]

Now compare that to this recent snap shot of BTC blockchain with full blocks. It took over an hour just to process 5,000 TX's.

So DGB easily hits 10,000 TX's in 1 min.  BTC takes over an hour for 5,000 TX's. 

DigiByte rocket speed

[Tyke]

I am the author who wrote the book "DigiByte - History of the First Year" in 2015:

https://www.amazon.co.uk/DigiByte-History-First-Christopher-Thompson/dp/1519602804?ie=UTF8&refRID=1VX5RJPJ3J61T1VP11GS&ref_=pd_rhf_ee_p_img_9

Please message me if you would like a more extended history book to be embarked upon. 

Thank you

[Telenong]

techtank.news interview about digibyte

http://techtank.news/digibyte-and-the-rise-of-blockchain/

[john-connor]

You are ignoring the question, in fact you changed it. Here it is:

If I can form a block with 10 transactions that takes 43 seconds to validate how does the 15 second block timing not cause a network collapse due to block backup?

I appreciate the "test" but I will be forging multiple 43 second blocks to get the answer myself.

Good day.

[Telenong]

You are ignoring the question, in fact you changed it. Here it is:

If I can form a block with 10 transactions that takes 43 seconds to validate how does the 15 second block timing not cause a network collapse due to block backup?

I appreciate the "test" but I will be forging multiple 43 second blocks to get the answer myself.

Good day.

when announced vcash join with bizspark? you say every startup can joined, i think professional attitude is if your coin has a greater achievement or at least the same, and you can correct your competitors.

[Telenong]

2) Each algo has a block timing of 1 min 15 seconds. Microsoft research showed on the BTC network it takes an average of 6.5 seconds for 50% of nodes to receive a new block. 95% in 40 seconds with a mean of 12 seconds. So our 1 min 15 second individual algo block time is well within this time frame.

wowwowwow you really dont even understand how your own coin works do you? the block target of each algo is not relevant at all in this situation what is relevant is the gap between blocks as they actually come in regardless of algo, if blocks come in a few seconds apart which is common for digibyte and those blocks take longer than a few seconds to validate then the entire system falls apart, the reality here is that you changed the block target to 15 seconds without any proper understanding of what you are doing.

so system falls apart? can you give proof please? everyone can talk nonsense like you dude

[Jumbley]

You are ignoring the question, in fact you changed it. Here it is:

If I can form a block with 10 transactions that takes 43 seconds to validate how does the 15 second block timing not cause a network collapse due to block backup?

I appreciate the "test" but I will be forging multiple 43 second blocks to get the answer myself.

Good day.

How long do you think it will take DigiByte to create streams of full blocks through organic growth?
We would be guessing to answer, is the truth. When we get to that stage my money says technology will lead the way through organic improvement but in the meantime I welcome your white hack probes at the Digibyte network and so do the miners.