1 second is really to low: latency of the network is in some case comparable to that. But a 30second block can teoretically works.
It can fill the gap that makes bitcoin not so usable in brick and mortar shop: 20 or 30 minutes of wait in bitcoin network to have a couple of confirm of the payment will be too long to wait but in quickcoin is faster than POS payment in a lot of case.
Topic: QUICKCOIN - 1 block per second! - page 2. (Read 2300 times)
I'm for it. The orphan rate will be jaw-dropping, and if nothing else that will give us great insight into how the protocol behaves when pushed hard. I suspect it'd work.
One per second is perhaps too extreme, but it might have an interesting positive effect: pools would be unnecessary for a very long time since anyone could jump in and reasonably expect to strike coins several times a day even on a Bitcoin-scale network.
One per second is perhaps too extreme, but it might have an interesting positive effect: pools would be unnecessary for a very long time since anyone could jump in and reasonably expect to strike coins several times a day even on a Bitcoin-scale network.
Ok, so I don't have anything created or compiled or made, but I think it would be extremely interesting to see how a bitcoin-clone with blocks confirming every second would actually work. Sure, confirmations would get reversed all the time, then rebuilt, then reversed again, but eventually, a transaction would make its way into a generally accepted longest chain. And, it might take a lot less time than it does to get 1 solid confirmation from Bitcoin.
It's been theorized to be a terrible idea, but is it so terrible in practice? Let's try it for fun anyway!
It's been theorized to be a terrible idea, but is it so terrible in practice? Let's try it for fun anyway!
Jump to: