Replies: 4 comments
|
One possible mitigation is requiring PoW with each submitted operation, like nostr proposes with NIP-13. |
0 replies
|
One consideration is that the MDIP network should be permissionless, meaning any node should be able to join or leave at any time without involving a 3rd party. |
0 replies
|
I like NIP-13. BitMessage also used PoW as a relatively effective spam control. |
0 replies
|
Another possibility is a micropayment bond attached to the message. If the recipient accepts the message, the micropayment (e.g. 100 sats) is returned to sender, otherwise the recipient keeps it. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Without any sort of DID spam mitigation, the network is vulnerable to bad actors (malicious or accidental) that create millions of throw-away DIDs that every node has to store and resolve, causing waste of resources at best and network failure at worst. What can we do to prevent this scenario?
All reactions