@devtooligan Kind of irrelevant, since self-destruct doesn't work anymore.
But even when it did, it wouldn't have to iterate to clear all the slots. Just dumb the state for that address.
@devtooligan I wouldn't expect the EVM to delete all 2^256-1 possible records. Expecting that would be stupid. The only way you'd expect it to delete that much potential data is if you don't actually understand how computers work.
@MatthijsDeVries As for how to handle code releases from the core team, it's a tough problem.
Deploy packages, not protocols. The users compose protocols from the packages.
We're completing a framework for on-chain packages to secure the supply chain.
@MatthijsDeVries Thanks for the measured reply.
To clarify, my issue is upgradable logic in public code, like DEX pools. It violates self-sovereignty. Upgrades should be handled with migrations, or wrapping.
Democracy is a compromise, not a goal. Not appropriate for changing policy(code).
@MatthijsDeVries The fact that publicly available code should be immutable is obvious.
There's simply no way for a governance process to upgrade code safely. It defeats the entire point of smart contacts.
I'm stunned you even consider this acceptable, let alone desirable.
@scupytrooples So close. But you fell for the con.
Libertarian left can't exist. Leftism is entirely based on totalitarian control.
You're thinking of anarchism.
Left wants to take control.
Anarchism wants to remove control.
@pcaversaccio Don't use an ownable design for anything public in the first place. Don't deploy redundant code to avoid introducing errors.
Immutable code needs an immutable supply chain.