This is not related to the release this thread is about
I disagree.
Revive has been added as a new pallet to the Polkadot Hub, this did not introduce breaking changes.
I don’t know if you don’t know that Polkadot Developers are shipping breaking changes all the time, or simply don’t care… But things breaks ALL the time.
Last year people were in despair because stopped receiving staking rewards, block explorer like subscan froze, people saw their staking disappeared from third-party wallets, Coinbase DOT withdraws and transfers stopped working.. caos… what happened? Well the asset-hub migration happened, a complete disaster from the user perspective.
In November one professor asked for my help, the ink! v6 examples he prepared and tested a week early stopped working… what happened? Revive.map_account() happened… which was released in ink-node right before his class, all front-end UI and polkadot-api scripts stopped working at once.
- Error: AccountUnmapped when using Ink! 6.0.0-beta.1 · Issue #32 · use-ink/ink-node · GitHub
- pallet_revive: Only enforce EIP-3607 for dispatchables by athei · Pull Request #10100 · paritytech/polkadot-sdk · GitHub
- Map account button · Issue #580 · use-ink/contracts-ui · GitHub
Notice the user don’t care if the guilty is from revive or ink!, he simply want things to work, by the end it damages Polkadot anyway because the regular user don’t distinct both…