Replying to Avatar highperfocused ⚡

I'm thinking about your hard fork definition.

Because a soft fork is backwards compatible and when another soft fork comes in, it's not a hard fork but only yet another soft fork, isn't it?

In my definition, a hard fork is when I for example have to update my Fullnode (Bitcoin Core) in order to receive the "new" Blockchain. If I don't upgrade, I will only get block valid with the old version but not with the new one.

A hard fork only appears, when the blockchain itself splits, isn't it?
Avatar
BTCapsule 🏴 2y ago

For example, say I soft fork the Bitcoin Core version before Taproot. This would be a "soft fork" because it’s compatible with everything prior to Taproot. Nodes are currently doing this now.

However, since transactions have already been mined with Taproot, if I add additional features to my soft fork that don’t include Taproot, then this is a hard fork. It is no longer backwards compatible with the longest timechain. Does that make sense?

Reply to this note

Please Login to reply.

Discussion

No replies yet.