I’ve had a bit of a fear for a number of years that after burning maidsafe tokens to the launched network, the network, for some unforeseen reason, or an attack, catastrophically crashes and all data, including token data is lost.
That fear is most likely completely unwarranted for reasons A,B,C, etc that I’m not clear on. But, precautionary principle in mind and assuming the cost of doing something about this isn’t too high, then maybe there is a way we can protect the community from such an event in the form of a token backup.
For example, I send maidsafe tokens to the burn address and I also give an ethereum address … not only does the app at the burn address create the safe network tokens on the network, but it also sends the same amount of maidsafe v2 tokens (to given ETH address) via an Ethereum contract purposely built for this task as a backup.
These new ethereum-based tokens serve only as a backup - they can’t be sent to the burn address for more safe network tokens (it would only accept omni-tokens anyway).
If something unthinkable happened to the network at some point in the future and all data was lost, including safe network token data, then a new network could be launched (bug/security-vulnerability fixed) and these backup tokens would then become the new source token for burning to become safe network v2 tokens.
known cons: Extra work for devs