ExFrog on Nostr: Replace covenants with multisig and realize that these 'attack surfaces' already ...
Replace covenants with multisig and realize that these 'attack surfaces' already exist. With covenants, the encumberance is coded into the recieve address, which you create and issue to the sender. The sender cannot suprise you with being in a covenant. Same with multisig, they cannot force you to withdraw into a multisig, but ofac compliant cbdc coin is possible (and easier) by only allowing withdraws into a multisig, whose second signer would only sign txn after checking with a gvt sponsored allow/block list... No covenant required
Published at
2024-04-07 17:02:24Event JSON
{
"id": "94ce81aeb2859be4627661aa9bdd2be55cbfd7370dcba2f4784b77af365ec2d5",
"pubkey": "0f43f6e2c622c2ad9f795eae4cde3edbf13d662a93e301ff4bb92a80456018a3",
"created_at": 1712509344,
"kind": 1,
"tags": [
[
"p",
"f0293508f3eb9e6fe99c2fd8ba69ff446216872a2d9f67979bfa4db8b3155806"
],
[
"e",
"aa79cb78cec48d7b9595134c5ce41e56b9a4c9265fdc23fe9f2e56aeb064b2db",
"",
"root"
]
],
"content": "Replace covenants with multisig and realize that these 'attack surfaces' already exist. With covenants, the encumberance is coded into the recieve address, which you create and issue to the sender. The sender cannot suprise you with being in a covenant. Same with multisig, they cannot force you to withdraw into a multisig, but ofac compliant cbdc coin is possible (and easier) by only allowing withdraws into a multisig, whose second signer would only sign txn after checking with a gvt sponsored allow/block list... No covenant required ",
"sig": "6abbea4aef7add8f7e4c37baffae5717121a19d1baf75eda0920addafac260ab1f2f62111d6fec404300b862f051f619d701808731ff71c8821df8ca3d0ca005"
}
