Connor McCormick ☀️
@nor
Got more WhatsApp spam so I'm here to say this again: A great pattern to prevent spam is to require a stake to send a message which can optionally be slashed by the recipients (where the tokens are destroyed). Required stake size can vary based on account reputation and other signals
2 replies
0 recast
7 reactions
Connor McCormick ☀️
@nor
1 reply
0 recast
1 reaction
Connor McCormick ☀️
@nor
Good discussion with @weeoo about this here https://warpcast.com/nor/0x21b527db
2 replies
0 recast
0 reaction
Connor McCormick ☀️
@nor
1 reply
1 recast
0 reaction
Dan Finlay 🦊
@danfinlay
You could do a version of this with gator.metamask.io where it doesn't cost a tx fee to "stake" (extend allowance). Allowance would have to be active to be visible, and the reader gets to determine when the "race" to withdraw begins, and so achieve good safety if they have a bundler they trust.
2 replies
0 recast
2 reactions
Connor McCormick ☀️
@nor
oh cool! Doing it via an allowance is a really elegant I think UX would be best with a max allowance where each message stake can slash from that allowance (stake must be less than allowance, but sum of stakes can be greater than total allowance it just harms their send score) any easy ways to avoid race issues?
1 reply
0 recast
1 reaction
Dan Finlay 🦊
@danfinlay
I think having a trusted bundler (flashbots/smart transactions style) can largely solve the race issue. Otherwise would need to lock funds.
0 reply
0 recast
1 reaction