As far we know, some payment processors and users accepts 0/unconfirmed transactions. But this solution is not secure, because it’s possible to create two transactions with the same inputs, but different outputs.

Attacker is able to send a first transaction directly to victim, and then broadcast a second transaction over the network. This couldn’t be prevented using the proof-of-work design, but it’s possible to fight with such manipulations through using an extension for our proof-of-stake system, and we even don’t need a chain fork to implement this.

Continue reading

Valid XHTML 1.0 Transitional Valid XHTML 1.0 Transitional Valid CSS Valid CSS      I find a bug/typo or I have a suggestion
Adapted for Lynx-like browsers
2013-2017 © Zloy & Co
For donations: 4ZLoY6T8wXKgrbZM9gL8fQt48NUzGo2yAg