I‘m curious about this too.
- the inheritance key: Nunchuk says it’s a 2-of-4 setup. But if the conditions for claiming the inheritance are met, isn’t it effectively a 1-of-4?
Because they also mention that „all funds“ can only be moved if 2 of your own keys are used (the platform key should only be able to co-sign to the configured amount).
So, I suspect that the inheritance key has also the sole signing rights if time-restricted conditions are met?
What am I missing here?
Can the inheritance setup be restored in e.g. Sparrow as well?
- platform key: where exactly does the primary key reside? It must be a software key. But is this key also synchronized to the cloud and available on the desktop app or does it reside only in the mobile app? And how do I know, it does not internally have the majority of/sole signing rights. Given that the co-signing amount is configurable and is denominated in $ and not sats, this is still a little confusing to me and I haven’t figured out how that could be implemented without custom logic on their servers (I.e. in a trustless way) and restored on e.g. Sparrow.
mrldotsh / Mr. L
npub1nj…v2875
2023-12-17 07:43:44
in reply to nevent1q…hc6u
Author Public Key
npub1njsejpxx4x04slle73wl56u6kf4yef57m05xl5ukjt9f4s63lrqq2v2875Published at
2023-12-17 07:43:44Event JSON
{
"id": "6dd882ac80023c9a1a5a749098b6fe6577bf33504e4ae50014b610803d2490f7",
"pubkey": "9ca19904c6a99f587ff9f45dfa6b9ab26a4ca69edbe86fd39692ca9ac351f8c0",
"created_at": 1702799024,
"kind": 1,
"tags": [
[
"e",
"17cba217f1c03deccdac52a426eb2b021b360ea49dd5bef3cf441e09fa843d79"
],
[
"e",
"f12732c18da5d29d63a18509f1b3435c0bc438f74408efb731b422ba40643997"
],
[
"p",
"1989034e56b8f606c724f45a12ce84a11841621aaf7182a1f6564380b9c4276b"
],
[
"p",
"1bf0db0a42346c39c6a0d70f2edd0c9e7104715995c841d5a48e9bfa834228f9"
]
],
"content": "I‘m curious about this too.\n\n- the inheritance key: Nunchuk says it’s a 2-of-4 setup. But if the conditions for claiming the inheritance are met, isn’t it effectively a 1-of-4? \nBecause they also mention that „all funds“ can only be moved if 2 of your own keys are used (the platform key should only be able to co-sign to the configured amount).\nSo, I suspect that the inheritance key has also the sole signing rights if time-restricted conditions are met?\nWhat am I missing here?\nCan the inheritance setup be restored in e.g. Sparrow as well?\n\n- platform key: where exactly does the primary key reside? It must be a software key. But is this key also synchronized to the cloud and available on the desktop app or does it reside only in the mobile app? And how do I know, it does not internally have the majority of/sole signing rights. Given that the co-signing amount is configurable and is denominated in $ and not sats, this is still a little confusing to me and I haven’t figured out how that could be implemented without custom logic on their servers (I.e. in a trustless way) and restored on e.g. Sparrow.",
"sig": "232881a7814fa9d67134797bab65e6ddaa14d33b43e61950a012ffbac8115b59811e4db7fe7c6c35039da52b10824db795bef2d76569e1555eed648a1686311a"
}