You are viewing a single comment's thread from:
RE: Thinking out loud: A possible path towards the "crab bucket" concept?
I haven't fully thought this through yet, but what about this: Instead of a pledge-message and mechanism to downvote-when-triggered the user instead composes and signs a downvote transaction but doesn't post it directly to the chain, instead they encrypt it with the memo key of a "crab bucket" account and post the encryption output as a comment on a "crab bucket" post (I'm assuming they have a tool to take care of the technical aspects, not doing it manually). If the crab bucket account detects it has enough downvote transactions for a particular target post it then decrypts them and posts those transactions to the chain.
Interesting thought. On one hand, it would be good because there would be no possibility of reneging after committing to vote. OTOH, I'm not sure how it would scale. I'm sure it would be fine at current usage levels, but there may be limits. It's definitely worth keeping this in mind if anyone ever takes steps towards implementation.