I believe this is correct. What I’m unsure of is whether you can create your new parent/bunker key, and give it “ownership” of an existing keypair.
What I would love to do someday is create an “offline” master nsec, and somehow — like in Bitcoin — use it airgapped to sign a message or otherwise give my nsecbunker admin control over any of my existing primary Nostr keypairs.
So the two contrasts with how I currently understand nsecbunker to function are, 1) offline key generation and storage and 2) delegation/control over existing keys and not simply generating new “child” keys in-app.
This account ( bostonwine (npub14qz…2q26)) is my daily driver. It’s my nym and my social graph, whereas my other keys are primarily used for client testing and Other Stuff. I generated this key inside Damus back in 2022: it has never touched another client and I’d love to keep it that way.
Thus my daydream: an offline-generated-and-stored “parent” nsec with the ability to “adopt” child accounts that already exist.
Heh, yo PABLOF7z (npub1l2v…ajft) what are the chances of this “adoption” thing working in nsecbunker at some point?
bostonwine / boston wine
npub14q…e2q26
2024-09-26 06:30:37
in reply to nevent1q…wjxt
Author Public Key
npub14qz92uedt0a8jte8jqg63jr3s5cc99cej36jh883z6tprlu354uqqe2q26Published at
2024-09-26 06:30:37Event JSON
{
"id": "ffc12eca1a034f169b1289eceb610162be53d94ea2a0db9f4bcc4573398fdf55",
"pubkey": "a80455732d5bfa792f279011a8c871853182971994752b9cf1169611ff91a578",
"created_at": 1727332237,
"kind": 1,
"tags": [
[
"e",
"16cea49ba0b3c6e154684805ed743d3fa63ef3129ae08fce73a687529547160b",
"",
"root"
],
[
"p",
"1928ee3558f54e3164d81d26c35e123c254bae128354d7617d7fd862d70d9a2b"
],
[
"p",
"a80455732d5bfa792f279011a8c871853182971994752b9cf1169611ff91a578"
],
[
"p",
"fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52"
]
],
"content": "I believe this is correct. What I’m unsure of is whether you can create your new parent/bunker key, and give it “ownership” of an existing keypair.\n\nWhat I would love to do someday is create an “offline” master nsec, and somehow — like in Bitcoin — use it airgapped to sign a message or otherwise give my nsecbunker admin control over any of my existing primary Nostr keypairs. \n\nSo the two contrasts with how I currently understand nsecbunker to function are, 1) offline key generation and storage and 2) delegation/control over existing keys and not simply generating new “child” keys in-app.\n\nThis account ( nostr:npub14qz92uedt0a8jte8jqg63jr3s5cc99cej36jh883z6tprlu354uqqe2q26) is my daily driver. It’s my nym and my social graph, whereas my other keys are primarily used for client testing and Other Stuff. I generated this key inside Damus back in 2022: it has never touched another client and I’d love to keep it that way.\n\nThus my daydream: an offline-generated-and-stored “parent” nsec with the ability to “adopt” child accounts that already exist.\n\nHeh, yo nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft what are the chances of this “adoption” thing working in nsecbunker at some point?",
"sig": "89e4a941dc84ae7f9fcc12c407c582db107e4f969d8805e0f467d62cb9dcf1915af94e0bd839da413d37b51899fd2e7d9809b9dfd83c3e3727343308892dd61f"
}