Putting this on my timeline for further review. I like the idea of mpub/nsec but I’d prefer to call it cpub/csec (child npub, child nsec). That’s just a a minor comment- I will study this more deeply. Thanks nostr:npub1gkgyk28lurjuhyfjlxsga9mw6lc0c47c8pmcr65usre9d3qjcx6q9cyk5m
nostr:note1ka653adu7krdfqec7nektvgu0rs47emzrzwhv8dy6dzet98830gqrj3c3p
Multi was the M but Child makes sense for a C too. 🤙
Here’s a longer dump of the ideas bundled…
They’re completely from a UX perspective so forgive any lack of technical understanding of key gen and key derivation limitations at drafting. Would love to see this concept make it to a client. I did a writeup of UX as perceived in a client. Will see if I can find that and link it too.
nevent1qqsf9anzwnh8hrcma6hmf95eltp3mqxez556eszwrak5aucq2jl56lgpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgy8ga7q
Thanks! I plan to dig into this pretty hard in the coming months. There is another scheme which I am familiar with - KERI (key event receipt infrastructure)
Love it. Ping me when brainstorming the functionally against real world use cases if it would be helpful. That’s my forte.
Sure thing. I like to spend a lot of time really nailing down the requirements. I understand the mechanisms, but I am not sure if I actually understand the requirements yet.
The UX flow for the client…
nevent1qqsrapx599qrxcjewkvst0jfq3ydlxs5s4gg9c6c4x3r45792nnhwyqppemhxue69uh5qmn0wvhxcmmv742muq
