Firstly, thank you for developing this amazing software. I'm going to be releasing an early alpha build of an application I'm working in a few weeks, and multichain is the biggest engine humming away inside it.
I need to implement a CAPTCHA-like system to prevent users from spamming the blockchain with garbage. I've been thinking about this problem a lot, and I suspect I will need to modify multichaind to accomplish this. I'll explain why my thinking has led to this conclusion, please let me know if there is another way I could tackle this problem.
Essentially, by main concern is that a user could receive asset issuing permissions on a blockchain (through my application), and then take their private key, connect to the blockchain with multichaind directly, and proceed to flood the blockchain with bad/useless data.
So far, the one solution I've come up with is integrating a CAPTCHA-like system directly into multichaind, perhaps requiring CAPTCHA entry only to users of a certain permissions group (e.g. an admin could continue to publish to the blockchain without entering CAPTCHA responses).
Does this seem like a reasonable solution, and can you think of any ways to incorporate this without modifying multichaind? Open to any solution that could help me prevent spamming/abuse of publishing rights to a blockchain.