Happy to see one more high quality wallet team join Polkadot ecosystem. And it is open sourced so you can verify it is not sending your seed phrase in plain text to some backend server.
In case you want to verify it now, repo is here: github.com/enkryptcom/enK…

If you were affected by the attack on certain Solana wallets today, please fill out the form below! If you weren't, please help share this tweet so those who were will see it. We need everyone's help in order to make sense of what happened.

solanafoundation.typeform.com/to/Rxm8STIT

Let's work together to build a safer Web3 ecosystem.

13/ This is one way to reduce impact or critical bugs in Substrate and I am sure there are many other tools we can implement to improve the situation. twitter.com/XiliangChen/st…

12/ But the most important thing is every protocol MUST have a process to handle ANY kind of bugs. However, there isn't any secret to this. Any good DevOps can explain how important a Disaster Recovery Plan can be. Yet I don't think most of the DeFi protocols have it.

11/ We could have additional monitor asserting some critical invariants always holds true. We could create interesting mechanism to allow whitehats to frontrun malicious transactions. We could add rate limiting to unexpected big amount transfers.

10/ We could have multiple implementation of critical smart contracts and ensure the results are matching. We could have reimplementation of the smart contracts using different languages running on a offchain server to ensure the onchain execution generates expected result.

9/ For mission critical softwares that are securing assets worth hundreds of millions of dollars, there isn't too much reason why it shouldn't have multiple redundancy and multiple layer of defense.

8/ Ethereum invested heavily on client diversity. Any censuses bug in a single client will not result consensus failure to the network. We know how to build resilient software but most of us are just not building it.

7/ Any critical components on a spaceship are fully redundant. Critical software services could be implemented multiple times by different teams individually. This is to ensure any bugs from a single implementation will not have actual impact to the system.

What if we have a programming language that can distinguish between non-existence and zero?

+2/ Generic Meta transaction pallet
Allow calls to be dispatched on behalf of another account, authorized by its signature. The call & signature can be delivered in XCM, relayer, etc. This will enable some interesting use cases such as atomic swap, XCM control foreign account

+1/ Two more ideas (added to the gist)
Fork the world
Allow developer to fork the relaychain & parachains and tweak the storages and run them locally so we can test cross chain code with live network data