Bitcoin Stack Exchange is a question and answer site for Bitcoin users, developers, and enthusiasts. It only takes a minute to sign up.
Sign up to join this community
I know soft fork which is compatible with older rules, but how are the older nodes going to the verify new transaction?
for example :
block#100 there is a new rule transaction.
the miner who created block#100, it must be a new rule's miner? and how the older nodes verify new transaction?
You're confusing what happens during a soft fork and a hard fork slightly.
A soft fork is backwards compatible, meaning old nodes will still accept the softfork transactions.
Hard forks are not backwards compatible, meaning old nodes will reject the new hardfork transactions.
Think of it like this: there is a list of consensus rules. If you want to change the rules, there are two fundamental ways to do this: make the rules more strict (no longer allow something that was allowed before), or make the rules less strict (allow something new).
If you make the rules more strict, then all of the old nodes will still accept everything you are doing. This would be a soft fork.
If you make the rules less strict, then all of the old nodes will reject the new things you are doing. This would be a hard fork.
