Why Nostr? What is Njump?
2023-12-17 07:47:21

mrldotsh on Nostr: Anyone figured out how Nunchuk is implementing their „Honey Badger“ plan (I.e the ...

Anyone figured out how Nunchuk is implementing their „Honey Badger“ plan (I.e the one with Inheritance Plan)?

Their docs only get me so far but doesn’t seem to answer all questions.
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.
Author Public Key
npub1njsejpxx4x04slle73wl56u6kf4yef57m05xl5ukjt9f4s63lrqq2v2875