lontivero on Nostr: #WalletWasabi is implemented on top of an #ecash system. The coordinator mints ...
#WalletWasabi is implemented on top of an #ecash system. The coordinator mints credentials (tokens), which are then redeemed in the form of Coinjoin transaction outputs. This means that the tokens have a very short lifespan; however nothing forces us to do that and they can be used for many many things if we create long-live ones.
Right now, I'm thinking we could use them to prevent DoS attacks against the coordinator by charging per request. That would be much better than the current mechanism, which bans coins depending on their size and how many times they were used to disrupt rounds, etc.
Published at
2024-05-29 14:02:04Event JSON
{
"id": "b431f9f5d8ad15dfcce1467017959ed4e9c11e0130f0b21301c6989837bf5eca",
"pubkey": "9e30e940238cd9ebebc6328176dd4d109812129442f2a6c38727fc66fa7ea90a",
"created_at": 1716991324,
"kind": 1,
"tags": [
[
"t",
"WalletWasabi"
],
[
"t",
"ecash"
]
],
"content": "#WalletWasabi is implemented on top of an #ecash system. The coordinator mints credentials (tokens), which are then redeemed in the form of Coinjoin transaction outputs. This means that the tokens have a very short lifespan; however nothing forces us to do that and they can be used for many many things if we create long-live ones. \n\nRight now, I'm thinking we could use them to prevent DoS attacks against the coordinator by charging per request. That would be much better than the current mechanism, which bans coins depending on their size and how many times they were used to disrupt rounds, etc.",
"sig": "285c46a316eb2c0b4058aafbf9edaee86e2a060d2dc43a12aa0db5e0e9937c6c23f5125349681916577586c934b06423e9b3296c36e9052f2b7e0875b30598e1"
}