Mimir Solutions

Mimir Solutions Corporation

[Mimir Solutions @MimirSolutions]

@BowTiedPickle @BowTiedDevil No memory based exploits.

[Mimir Solutions @MimirSolutions]

@BowTiedDevil @BowTiedPickle It makes most of the backend infrastructure of traditional designs irrelevant.

We can all securely share the same DB.

[Mimir Solutions @MimirSolutions]

@blainemalone @OpenZeppelin @mudgen Care to tell them the wonders of your standard?

[Mimir Solutions @MimirSolutions]

@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.

[Mimir Solutions @MimirSolutions]

@blainemalone @PatrickAlphaC Diamond dev community
https://t.co/UCTbYiB2Wy

[Mimir Solutions @MimirSolutions]

@devtooligan @pcaversaccio @0xArbiter @optimizoor No, Solidity arrays are just mappings with consecutive integers as keys.

Have you ever programmed before?

[Mimir Solutions @MimirSolutions]

@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.

[Mimir Solutions @MimirSolutions]

@devtooligan Are you new? Do you understand how computers and math work?

[Mimir Solutions @MimirSolutions]

@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.

[Mimir Solutions @MimirSolutions]

@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).

[Mimir Solutions @MimirSolutions]

@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.

[Mimir Solutions @MimirSolutions]

@MatthijsDeVries This is a terrible idea.

[Mimir Solutions @MimirSolutions]

@banteg Is not defi if you can turn it off.

[Mimir Solutions @MimirSolutions]

@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.

[Mimir Solutions @MimirSolutions]

@foldfinance @pcaversaccio Wait till you see the whitepaper.

[Mimir Solutions @MimirSolutions]

@pcaversaccio Contact security really comes down to Verifiable Storage Control and a chain of custody for who's had that control.

[Mimir Solutions @MimirSolutions]

@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.

[Mimir Solutions @MimirSolutions]

@0xfbifemboy Process as punishment.