fcb ₿ on Nostr: I've been thinking about this as well. I wonder if a sort of multi-sig or ...
I've been thinking about this as well. I wonder if a sort of multi-sig or multi-signing solution can be added to the system. There's potentially a way to have two backup accounts that could both be used to 'approve' and account transfer. We'd need someway to track how this happens, maybe a special type of event from the compromised account that points to the new account. The clients would have to do the work of connecting the dots between the accounts, but this should be a huge lift on the client side.
Published at
2023-03-07 17:34:29Event JSON
{
"id": "fd25cf8ce3c3e9386503d1d59f933d9123ac68a46425bb4371c5fd58fd2c90b2",
"pubkey": "3f4341c90f9f0ee9628572b693234325bac0bc73dd629cfa45040fad84ae815f",
"created_at": 1678210469,
"kind": 1,
"tags": [
[
"e",
"6d7b6cf3529e52b1b200444367b8f79313a77ff6951e964aeb5cb7a9120733eb",
"",
"root"
],
[
"p",
"23d49394612585706c72908a5e3904f95177ea087b032ddbfcd2862304c7d983"
]
],
"content": "I've been thinking about this as well. I wonder if a sort of multi-sig or multi-signing solution can be added to the system. There's potentially a way to have two backup accounts that could both be used to 'approve' and account transfer. We'd need someway to track how this happens, maybe a special type of event from the compromised account that points to the new account. The clients would have to do the work of connecting the dots between the accounts, but this should be a huge lift on the client side.\n",
"sig": "d5d79b46c61a31a44c3b5594266760a5696d0136b7f4965260990607726cb23b9946fa48752a46f3cfd9e2c4ebd3fc8c4f3de520db07e0f9adfed55e22ca2594"
}
