From bcfa74ed9c2353bbadada2418c29173cf82874ae Mon Sep 17 00:00:00 2001 From: Alain Brenzikofer Date: Fri, 11 Sep 2026 07:09:56 +0000 Subject: [PATCH] docs: what the stealth meta address is for Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01Rvc3HbiWBTqbAvRT45G5oX --- docs/rfcs/2026-09-10-name-ownership-keys.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/rfcs/2026-09-10-name-ownership-keys.md b/docs/rfcs/2026-09-10-name-ownership-keys.md index 812f21a967..7f9df0daae 100644 --- a/docs/rfcs/2026-09-10-name-ownership-keys.md +++ b/docs/rfcs/2026-09-10-name-ownership-keys.md @@ -48,6 +48,13 @@ the point of the layout. Stealth addresses will attach at purpose `5564'`, at the profile level. Only purpose `44'` is used here. +The plan is one meta address per profile: a spend key and a viewing key, whose +public halves are published with the chat profile, opt-in. A sender derives a +fresh destination from it without a handshake, so one meta address serves any +number of names received that way, and those keys are not at a derivation path. +That is why it belongs at the profile level, while the names a profile buys sit +at the address level. + ## Commands Internal API. The names commands will call these; users will not.