If we did go down the forking route, this is definitely an option. Creating custom types with ownership isn’t that hard, no that I’ve understood how its done.
What isn’t clear to me is how creating tokens could be done.
Once idea was to have a smart contract thar burned ANT (or eMAID, tbh) and created a one way exchange for native. This could then dictate the supply without any further action. What was burned becomes what circulates.
However, that links the fork to MAID, which may be undesirable on a fork. May be best for all involved to keep them separate.
Maybe it makes a certain amount of sense to create the external token on a blockchain, then burn it for native though. That could help to control the unburned suppy, without having to invent something novel to do it natively. A one way burn into a storage token would be like buying a gift card, which feels reasonable from a legal standpoint, but maybe maidsafe were advised otherwise? Clarity would be nice.
Then you have the problem of how to pay node runners. I haven’t inspected the code around that, but it may be possible to transfer a native token directly to a node runner. I’m guessing the mainnet does something similar to that now already, but via a blockchain.
So, having data types that can have ownership changed, without a long history, is semi-proven as possible (i.e. not battle tested, but POC works). That is useful for all sorts of data permission reasons. Using such a type for tokens seems possible too, but managing supply and node payments isn’t clear to me.
Whatever does happen, backwards compatibility with mainnet would be hugely beneficial, as would remaining friendly with the maidsafe team. Tbh, if they weren’t happy with the fork, I’m not sure I’d want to be involved with it either.