dandri/simplex-chat
1
0
Fork 0
mirror of https://github.com/simplex-chat/simplex-chat.git synced 2026-09-27 17:58:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: give the reason for the counter before what it costs

Browse Source 
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Rvc3HbiWBTqbAvRT45G5oX
This commit is contained in:
Alain Brenzikofer
2026-09-11 07:35:39 +00:00
co-authored by Claude Opus 5
parent af1349160e
commit 05508c0edd
1 changed files with 8 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/rfcs/2026-09-10-wallet-keys.md
+8 -5
View File
@@ -42,11 +42,14 @@ find the rest. A key per name leaves no such link. It also keeps an export
narrow, as a name's secret is a leaf, with no chain code, so handing it over
hands over that name only.
**Why the account is a counter and not a hash of the profile.** A hashed index
would survive a restore in any profile order, and would leave no gap to disclose
a hidden profile. It would also change when a profile is renamed, and it would
move profile accounts off the list MetaMask and Ledger Live enumerate, which is
the point of the layout.
**Why the account is a counter and not a hash of the profile.** A counter keeps
every profile on the account list MetaMask and Ledger Live enumerate, which is
the compatibility this layout is for. A hash of the display name would not, and
it would change whenever a profile is renamed.
It costs two things a hash would give: the same account after a restore whatever
order the profiles were recreated in, and indexes with no gap to disclose a
hidden profile.
Stealth addresses will attach at purpose `5564'`, at the profile level. Only
purpose `44'` is used here.