Replying to Avatar nicnym

You truly are retarded. I respect that.

The code is not “dangerous”

It’s the mempool policy change that is the problem. It is a drastic and contentious change.

On one side- we have people who will UPDATE to the upcoming Core v30 nodes (no filter)

On the other side- Every other version of Core and Knots that have the mempool filter default in place at 40 bytes or 80 bytes.
Avatar
Dave🐸 4mo ago

Luke and Mechanic can do this 👇🏽

OR cry harder. The end.

Reply to this note

Please Login to reply.

Discussion

Avatar
nicnym 4mo ago

No they can’t bro.

Let’s say they hard forked the knots client and you were “tricked” as a user into updating and using the brand new coin “bitcoin-K”

1. Your new hardforked node would be kicked off the Bitcoin network and only connect with other hardfork nodes.

2. If you tried to send or sell any your new “bitcoin-K” coins, no exchange would accept them unless the coin was listed and a market established. If you wanted to sell them peer to peer, the person receiving them would have to also be using a “Bitcoin-k” node.

3. You would realize what happened and switch back to consensus Bitcoin software.

Literally zero damage to Bitcoin. Even people who attempted the hard fork would still have their Bitcoin. Just have to use a regular Bitcoin node (old version) to spend them.

You realize people who won the block size war PROFITED from it right?

The people who stuck with the real Bitcoin, got to double their coins and sell all the B Cash coins to buy more Bitcoin.

Of course many retards “believed” in B cash, and sold their Bitcoin instead. Some people sold both, some kept both.