Are the backup databases fully synced?
Regardless of the coins, those holding the copies, after cross-checking its integrity, can create independent reclaim codes and communicate them to shareholders. This can be done regardless of the BTC flow, and hopefully ASAP.
As I had proposed in another thread, the claim codes should encode the asset id and number of shares, so that a list doesn't need to be given to issuers. This way, it will be up to the shareholders to disclose their ownership to the issuer.
After the shareholder submits the code to the issuer, issuer sends a verification code to one of the database maintainers, which passes the verification code to the shareholder. Shareholder submits this verification code to the issuer, thereby successfully proving ownership anonymously.
Any better ideas? This may sound like too much fuss, especially if different encoding schemes are used by database maintainers or the database isn't synced, but I think it would definitively fix this portion of the wreckage.
Also, if the issuer wants to list on a different exchange, which will cooperate with the process, the maintainer might give the shareholders a redeeming URL at the new exchange to automate the process.
Get one person to AML for lots of different accounts for a cut.
I don't get what you're saying. I'm assuming the only people we can trust is the db maintainers, for no other reason than the fact that we already have to trust them. Are you talking about the shareholder side?
On the other hand, "they" probably already have the database and it's almost worse than it being public. Just sending it to all issuers might have become a valid option. I'd like to hear what theymos thinks about this.
Another option is to launch the same exchange under tor by one of the maintainers, but there would be massive problems with this.
EDIT: Oh, okay, I get what you are proposing now.
