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

[Jumbley]

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.

Why does individual algo block time matter here? It doesn't!
DGB block time is 15 secs, right?

I'd like to stop the bullshitting and fudding in favor of discussing about the facts. Anyone?


Besides that - i like DGB. It's great for trading, good pump cycle, awesome marketing.

15 seconds is not set in stone as the DigiByte block time. It is made up from 5 algorithms each with averaged block time of 75s. So the averaged time for the whole of Digibyte is a block being found every 15s. You cannot debunk JCs basic math problem but you can say there are variables that come into play that are more than likely going to defeat it because it is a future problem for DigiByte that he is asking you to solve with today’s tools, where nothing on the network is capable of verifying the transactions fast enough. I don’t think this is actually true today and it will be even less so in the future. This is why he wants to stick us to an imaginary constant flow of 43 second transactions but think about what that actually means. It means we would be running at full capacity constantly where nothing had a chance to catch up, it’s just ridiculous really and we would be competing with VISA today. 

[Jumbley]

....

Why are you still here if the only thing you want to do is FUD on DGB?
There's a lot of other thread that might be interested in your comments.

i'm waiting john-connor crash DGB lolll

You are wasting everyone else’s time as well as your own because that isn’t going to happen.

[wurstgelee]

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.

Why does individual algo block time matter here? It doesn't!
DGB block time is 15 secs, right?

I'd like to stop the bullshitting and fudding in favor of discussing about the facts. Anyone?


Besides that - i like DGB. It's great for trading, good pump cycle, awesome marketing.

15 seconds is not set in stone as the DigiByte block time. It is made up from 5 algorithms each with averaged block time of 75s. So the averaged time for the whole of Digibyte is a block being found every 15s. You cannot debunk JCs basic math problem but you can say there are variables that come into play that are more than likely going to defeat it because it is a future problem for DigiByte that he is asking you to solve with today’s tools, where nothing on the network is capable of verifying the transactions fast enough. I don’t think this is actually true today and it will be even less so in the future. This is why he wants to stick us to an imaginary constant flow of 43 second transactions but think about what that actually means. It means we would be running at full capacity constantly where nothing had a chance to catch up, it’s just ridiculous really and we would be competing with VISA today.  

Thanks for the reply.

I think his initial point was that DGB isn't as scalable as it claims it is (today). So yes, it seems he is technically right here (today).

[DARKHOLDER]

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.

Why does individual algo block time matter here? It doesn't!
DGB block time is 15 secs, right?

I'd like to stop the bullshitting and fudding in favor of discussing about the facts. Anyone?


Besides that - i like DGB. It's great for trading, good pump cycle, awesome marketing.

15 seconds is not set in stone as the DigiByte block time. It is made up from 5 algorithms each with averaged block time of 75s. So the averaged time for the whole of Digibyte is a block being found every 15s. You cannot debunk JCs basic math problem but you can say there are variables that come into play that are more than likely going to defeat it because it is a future problem for DigiByte that he is asking you to solve with today’s tools, where nothing on the network is capable of verifying the transactions fast enough. I don’t think this is actually true today and it will be even less so in the future. This is why he wants to stick us to an imaginary constant flow of 43 second transactions but think about what that actually means. It means we would be running at full capacity constantly where nothing had a chance to catch up, it’s just ridiculous really and we would be competing with VISA today. 

How fast is DGB transaction from one wallet to another?

[Jumbley]

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.

Why does individual algo block time matter here? It doesn't!
DGB block time is 15 secs, right?

I'd like to stop the bullshitting and fudding in favor of discussing about the facts. Anyone?


Besides that - i like DGB. It's great for trading, good pump cycle, awesome marketing.

15 seconds is not set in stone as the DigiByte block time. It is made up from 5 algorithms each with averaged block time of 75s. So the averaged time for the whole of Digibyte is a block being found every 15s. You cannot debunk JCs basic math problem but you can say there are variables that come into play that are more than likely going to defeat it because it is a future problem for DigiByte that he is asking you to solve with today’s tools, where nothing on the network is capable of verifying the transactions fast enough. I don’t think this is actually true today and it will be even less so in the future. This is why he wants to stick us to an imaginary constant flow of 43 second transactions but think about what that actually means. It means we would be running at full capacity constantly where nothing had a chance to catch up, it’s just ridiculous really and we would be competing with VISA today.  

Thanks for the reply.

I think his initial point was that DGB isn't as scalable as it claims it is (today). So yes, it seems he is technically right here (today).

There is only one way to prove that and that is by breaking it today but that would be pointless and very expensive and DigiByte would not fall down unless you were able to continuously maintain the stress at which point we would have to admit that it wasn't as scalable as presently programmed, if it did fall over. But then we would change the code and move on. The scalability of DigiByte is layed out in a 20 year plan, we are expecting much to change in this time. So DigiByte is as scalable as described!

[Jumbley]

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.

Why does individual algo block time matter here? It doesn't!
DGB block time is 15 secs, right?

I'd like to stop the bullshitting and fudding in favor of discussing about the facts. Anyone?


Besides that - i like DGB. It's great for trading, good pump cycle, awesome marketing.

15 seconds is not set in stone as the DigiByte block time. It is made up from 5 algorithms each with averaged block time of 75s. So the averaged time for the whole of Digibyte is a block being found every 15s. You cannot debunk JCs basic math problem but you can say there are variables that come into play that are more than likely going to defeat it because it is a future problem for DigiByte that he is asking you to solve with today’s tools, where nothing on the network is capable of verifying the transactions fast enough. I don’t think this is actually true today and it will be even less so in the future. This is why he wants to stick us to an imaginary constant flow of 43 second transactions but think about what that actually means. It means we would be running at full capacity constantly where nothing had a chance to catch up, it’s just ridiculous really and we would be competing with VISA today. 

How fast is DGB transaction from one wallet to another?

I can’t answer this definitively but fast enough to buy coffee with.   

[Tortoise75]

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.

Why does individual algo block time matter here? It doesn't!
DGB block time is 15 secs, right?

I'd like to stop the bullshitting and fudding in favor of discussing about the facts. Anyone?


Besides that - i like DGB. It's great for trading, good pump cycle, awesome marketing.

15 seconds is not set in stone as the DigiByte block time. It is made up from 5 algorithms each with averaged block time of 75s. So the averaged time for the whole of Digibyte is a block being found every 15s. You cannot debunk JCs basic math problem but you can say there are variables that come into play that are more than likely going to defeat it because it is a future problem for DigiByte that he is asking you to solve with today’s tools, where nothing on the network is capable of verifying the transactions fast enough. I don’t think this is actually true today and it will be even less so in the future. This is why he wants to stick us to an imaginary constant flow of 43 second transactions but think about what that actually means. It means we would be running at full capacity constantly where nothing had a chance to catch up, it’s just ridiculous really and we would be competing with VISA today.  

Thanks for the reply.

I think his initial point was that DGB isn't as scalable as it claims it is (today). So yes, it seems he is technically right here (today).

Well, I guess it depends. For example how many average transactions do you need to get an average block size of roughly 1GB? Or the other way round, would the amount of average TX DGB claims to scale up to grow the block size to an amount that can't be processed in that 15s time frame? DGB didn't claims it would handle any filled with rubbish blocks made up to attack the network, although it should claim it handles without breaking down.
Then there is the assumption that nodes go completely haywire if they don't validate blocks in time. Now by logic they would indeed start to lag behind and get unsynchronized with the network. But they normally won't shatter the network, else every node experiencing network troubles, having to sync up after a downtime or run on a RaspPi with a bad day would say farewell mainbranch and walk off on their own every time. A question remains: How good are block generating/mining nodes at noticing they lag behind and are invalid blocks securely being orphaned in such a scenario?

Quite a bit surprising was DigiBytes answer that each algo has 75s time to get settled between blocks, though. How does that work? Something like each algo running its own mini-blockchain tied together I don't know how to form the full chain? Or am I mistaken that on normal blockchains blocks refer to the one in front and if DGB didn't change that all miners on all algos would have to update their hashing job every time a new block gets mined regardless of which algo it was mined on?

[wurstgelee]

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.

Why does individual algo block time matter here? It doesn't!
DGB block time is 15 secs, right?

I'd like to stop the bullshitting and fudding in favor of discussing about the facts. Anyone?


Besides that - i like DGB. It's great for trading, good pump cycle, awesome marketing.

15 seconds is not set in stone as the DigiByte block time. It is made up from 5 algorithms each with averaged block time of 75s. So the averaged time for the whole of Digibyte is a block being found every 15s. You cannot debunk JCs basic math problem but you can say there are variables that come into play that are more than likely going to defeat it because it is a future problem for DigiByte that he is asking you to solve with today’s tools, where nothing on the network is capable of verifying the transactions fast enough. I don’t think this is actually true today and it will be even less so in the future. This is why he wants to stick us to an imaginary constant flow of 43 second transactions but think about what that actually means. It means we would be running at full capacity constantly where nothing had a chance to catch up, it’s just ridiculous really and we would be competing with VISA today.  

Thanks for the reply.

I think his initial point was that DGB isn't as scalable as it claims it is (today). So yes, it seems he is technically right here (today).

There is only one way to prove that and that is by breaking it today but that would be pointless and very expensive and DigiByte would not fall down unless you were able to continuously maintain the stress at which point we would have to admit that it wasn't as scalable as presently programmed, if it did fall over. But then we would change the code and move on. The scalability of DigiByte is layed out in a 20 year plan, we are expecting much to change in this time. So DigiByte is as scalable as described!

I guess we could argue whether a product is scalable if you have to alter it to be scalable or not, but i agree that it's no big deal to alter it.

[Crash95]

The best one 

[Jumbley]

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.

Why does individual algo block time matter here? It doesn't!
DGB block time is 15 secs, right?

I'd like to stop the bullshitting and fudding in favor of discussing about the facts. Anyone?


Besides that - i like DGB. It's great for trading, good pump cycle, awesome marketing.

15 seconds is not set in stone as the DigiByte block time. It is made up from 5 algorithms each with averaged block time of 75s. So the averaged time for the whole of Digibyte is a block being found every 15s. You cannot debunk JCs basic math problem but you can say there are variables that come into play that are more than likely going to defeat it because it is a future problem for DigiByte that he is asking you to solve with today’s tools, where nothing on the network is capable of verifying the transactions fast enough. I don’t think this is actually true today and it will be even less so in the future. This is why he wants to stick us to an imaginary constant flow of 43 second transactions but think about what that actually means. It means we would be running at full capacity constantly where nothing had a chance to catch up, it’s just ridiculous really and we would be competing with VISA today.  

Thanks for the reply.

I think his initial point was that DGB isn't as scalable as it claims it is (today). So yes, it seems he is technically right here (today).

There is only one way to prove that and that is by breaking it today but that would be pointless and very expensive and DigiByte would not fall down unless you were able to continuously maintain the stress at which point we would have to admit that it wasn't as scalable as presently programmed, if it did fall over. But then we would change the code and move on. The scalability of DigiByte is layed out in a 20 year plan, we are expecting much to change in this time. So DigiByte is as scalable as described!

I guess we could argue whether a product is scalable if you have to alter it to be scalable or not, but i agree that it's no big deal to alter it.

Hardware technology is not stagnant; it’s advancing all the time as you probably know, strongly linked to moore’s law. I expect it to outpace demand for DigiByte to alter to cope with this particular scenario if it has not already but I have no crystal ball. DigiByte has a road map towards specific targets that will eventually supersede VISA capabilities and beyond. These targets have not just been plucked out of thin air but calculated/estimated(bit of both) to keep DigiByte at the cutting edge of what is achievable using this technology but what is the point of software if you can’t alter it when you need to?   

[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.

Why does individual algo block time matter here? It doesn't!
DGB block time is 15 secs, right?

I'd like to stop the bullshitting and fudding in favor of discussing about the facts. Anyone?


Besides that - i like DGB. It's great for trading, good pump cycle, awesome marketing.

15 seconds is not set in stone as the DigiByte block time. It is made up from 5 algorithms each with averaged block time of 75s. So the averaged time for the whole of Digibyte is a block being found every 15s. You cannot debunk JCs basic math problem but you can say there are variables that come into play that are more than likely going to defeat it because it is a future problem for DigiByte that he is asking you to solve with today’s tools, where nothing on the network is capable of verifying the transactions fast enough. I don’t think this is actually true today and it will be even less so in the future. This is why he wants to stick us to an imaginary constant flow of 43 second transactions but think about what that actually means. It means we would be running at full capacity constantly where nothing had a chance to catch up, it’s just ridiculous really and we would be competing with VISA today. 

How fast is DGB transaction from one wallet to another?

testing send 100.000 dgb to my wallet, on 10 sec tx can see on pending tx, less than a minute,  all tx already confirmation

[Kiritsugu]

Does anyone know when the fix for the Chrome wallet extension will be finished?  Mine's been broken for almost a week now.

[Telenong]

Does anyone know when the fix for the Chrome wallet extension will be finished?  Mine's been broken for almost a week now.

check out some of the previous page it ever discussed

[Jumbley]

Does anyone know when the fix for the Chrome wallet extension will be finished?  Mine's been broken for almost a week now.

check out some of the previous page it ever discussed

DigiByte gaming site suggests using chrome beta to skip loading page and says they are working to resolve the issue.
https://www.google.com/chrome/browser/beta.html
idk if that helps.

[minhtito]

Does Digibyte plan to expand their game titles?

[TTE]

Does Digibyte plan to expand their game titles?

According to rumors, Dota 2 is on the plan as next game.

[24hralttrade]

Does Digibyte plan to expand their game titles?

According to rumors, Dota 2 is on the plan as next game.

Rumors rumors rumors.....

[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.

Why does individual algo block time matter here? It doesn't!
DGB block time is 15 secs, right?

I'd like to stop the bullshitting and fudding in favor of discussing about the facts. Anyone?


Besides that - i like DGB. It's great for trading, good pump cycle, awesome marketing.

15 seconds is not set in stone as the DigiByte block time. It is made up from 5 algorithms each with averaged block time of 75s. So the averaged time for the whole of Digibyte is a block being found every 15s. You cannot debunk JCs basic math problem but you can say there are variables that come into play that are more than likely going to defeat it because it is a future problem for DigiByte that he is asking you to solve with today’s tools, where nothing on the network is capable of verifying the transactions fast enough. I don’t think this is actually true today and it will be even less so in the future. This is why he wants to stick us to an imaginary constant flow of 43 second transactions but think about what that actually means. It means we would be running at full capacity constantly where nothing had a chance to catch up, it’s just ridiculous really and we would be competing with VISA today. 

How fast is DGB transaction from one wallet to another?

testing send 100.000 dgb to my wallet, on 10 sec tx can see on pending tx, less than a minute,  all tx already confirmation

Did you use the web wallet because the web wallet still isn't working.  Hopefully the fix comes out soon, or they pick up enough new people at these "conferences" to move some of us new suckers---investors off the bottom of the pyramid.

I never keep bitcoin, digibyte or other on web wallet, because it is not safe. as i know dgb web wallet has long time shut down. digibyte dev give warning 3-4 month ago. they ask member to move all coin from there

[kreatoralex]

wallet stuck on 2499016

[kreatoralex]

wallet stuck on 2499016

all ok