R0gueN1nja

Every two weeks, the difficulty adjustment algorithm checks how many blocks were created in that time compared to what it expected, based on a target of ten minutes per block. If too many blocks are mined, it raises the…

I'm not saying we stop checking signatures. Only that they not be include in blocks, to save space. Signatures are big and excluding them would save a lot of space. The next block is only valid if it respects original…

The Merkle tree permits pruning, but doesn't improve TPS. It requires you to download full transaction data before pruning which is a waste of bandwidth. And VOUT is just an index value. OGH is a checksum.

For new transactions to be validated, nodes gotta do a few things: 1. track down where each input is coming from (like block:txid:vout), 2. find that output in the blockchain, 3. check every input in every transaction…

I have finally addressed the glaringly obvious oversight of my previous scheme.

I have greatly altered the original idea.

So here's the deal: work goes into crafting a block hash to make it super hard to produce a valid hash if anything's changed. But this means we end up doing work after the block's made, causing those annoying delays.…

So, competitive mining has its perks but comes with serious downsides. There’s no time limit, just a floor for difficulty. Block production can be all over the place, but over time and a lot of blocks, it averages out.…

not much going on here

In the unlikely event that an attacker manages to flood the mempool with so many of his own addresses that he ends up owning all of the addresses in the priority list of an output that he also owns, despite random…

Sybil attacks are used to subvert reputation and voting systems. The random selection of addresses into priority lists is not a reputation or voting system. As long as the opportunity to cosign transactions is randomly…

I just want to say thanks for all the insights and criticisms. In response, I have made substantial changes to the protocol. Check it out and let me know what you think.

By using a verifiable random function. It's only typical for consumers to create transactions that split coins. Merchants typically create transactions that merge coins. Sometimes the number of inputs will be less than…

You have to cosign something before you can spend your coins. Fake transactions are invalid, and nodes won't even propagate invalid transactions. Option 1 is to sign nothing. When this happens, a sender can republish…

The issue with double spending isn't that network nodes can't independently deal with it. The real problem is there's no universal way to keep consensus that can't be manipulated. Like, if the rule is to consider the…