Phase 6 is a probe with no code of its own, so it rides along: both fork tests pass unchanged, which means marmot-kmp 2.2.1 still scores a fork this device is half of the way quartz 1.15.2 did. The assertion whose message is "the two sides agree -- the library has been fixed" did not fire. What changed is that the fix docs/marmot-v2.md predicts is now a first-class thing on the library's side -- MlsGroup.stageCommit, with the staged commit in MlsGroupState from its STATE_VERSION 9 -- so it is a choice in MlsCandidateStateEngine between replaying a branch and taking the state that was kept. Both notes say so. Phase 5 is the skipped keys, and it is half closed. mls-kmp's state carries them: skippedApplicationSecrets and skippedHandshakeSecrets, exported by saveState and imported by restore, arriving at STATE_VERSION 5 so a version-4 blob reads them as an empty map. That is steps 1 to 3 of the fix docs/mls-skipped-keys.md proposed. Step 4 is not done: consumedGenerations, the replay guard, is still one SecretTree's field. The app does not benefit yet, and the first draft of this test claimed it did. MlsGroupManager.decrypt persists only when the message was a commit that advanced the epoch, so the secret reaches the live group and never the row. The draft delivered generation 1, rebuilt the engine, delivered generation 0 and asserted it decrypted -- and it did, for the wrong reason: a rebuilt engine restores a blob whose sender ratchet never moved, so generation 0 is simply the next one it expects. A green test proving nothing, caught by the assertion beside it that looked redundant. So the three tests say what is true: the secret is in the state the engine would save, a group rebuilt from those bytes reads the late message, and the stored state does not carry it. The last one is pinned in the style of the authored fork, with its KDoc saying what to invert when the receive path starts persisting -- deliberately not done here, because it is a write per inbound message that re-encodes the ratchet tree, the group context and every epoch secret. saveSenderRatchet is the library's answer to that cost on the send side. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Giza docs
Notes on the parts of this app whose behaviour is not recoverable by reading the code alone — where the reasoning lives in a protocol, a failure mode that is silent, or a decision that looked arbitrary and was not.
Most of them were written while the app was Bennu, before the fork, and they say so where it
matters: a decision taken in Bennu was taken in Bennu. Source paths in them point at
mobi/giza. Strings spelled bennu/… in their formulas were derivation tags the fork kept on
purpose (giza-rebrand.md); every one was a wallet's, and they appear only in
the retired notes now.
| document | covers |
|---|---|
| shared-key-ceremony.md | ChillDKG over NIP-17: the rounds, the approval gates, the chat transcript, participant ordering |
| shared-key-derivation.md | deriving further keys from the group's threshold key with FROST tweaks — why not BIP32, why no chain code, and the one rule that must not be broken |
| subgroups.md | a group making another group — the four ceremonies, what the parent's signature actually covers, and why the child's key is fresh rather than derived |
| ceremony-creation.md | one place to start a key ceremony — how joining a subgroup's ceremony opened a second one for the parent room, the screen that showed a ceremony and offered to start one in the same button, and the removal of the nip30303 documents, whose kinds collided with the ceremony's, leaving the member chronicle with nothing to carry and nothing to say |
| frost-batch-signing.md | signing several events in one ceremony — why one nonce can never cover two messages, and the phased schema, wire and UI work that follows from it |
| frost-session-resend.md | asking the members who never got a signing proposal to look again — why a proposer can repeat only what it wrote, why a member's availability signal needs no repeating, and the one half that has to come from the silent member's own device |
| marmot-membership.md | how members join an MLS group, and the epoch race that makes a missing member look like a successful invite |
| member-chronicle.md | handing a member added after the work was done the group's signed record — why the events are not on the wire at all, and why the room's id is enough to verify them |
| marmot-direct-messages.md | a one-to-one message inside a group as a stock NIP-59 gift wrap — what its MIP-03 carve-out costs, why the sender cannot read their own, and the one query that would broadcast it |
| mls-skipped-keys.md | why a group event that arrives a moment late is dropped for good, which flows trigger it, the quartz fix, and the partial mitigation in this app |
| long-running-sync.md | the chat subscriptions that stay open instead of pulling once per screen — why the request queue could not simply hold one, and how the group filter follows the room list |
| dead-code.md | code in the sync and relay stack that nothing calls, why each piece is still there, and which of it is a bug rather than a leftover |
| nsec-sign-in.md | signing in with an existing nostr key — why an nsec can never have a wallet behind it, the ten call sites that make it small, and the sign-in machine that was already built and unreachable |
| npub-sign-in.md | signing in with only a public key — what a key that cannot sign can still see here, why that is a preview rather than a browser, and the four decisions the word settles |
| multiple-profiles.md | several profiles on one device — why a profile is a credential and a seed is a wallet attached to one, why a switch is a restart rather than a swap, the two entrances the app lacks, and the inbox a switch would silently lose |
| jvm-target.md | what desktop support cost, phased — why the native chain was already done, why an empty source set in our phoenix fork was the real blocker, and why DAO tests need none of it |
| npub-profile-preview.md | showing the person before a direct message is started from a pasted npub — why the preview is a screen keyed by public key, what "found" means when a row can be a placeholder, and the phase that makes the button honest about a key package that never comes |
| material-design-conformance.md | what the M3 foundations actually require, measured against all 43 screens — the colour pairing that renders the app's own proposals invisible, and eight phases that put the decisions back in the theme |
| marmot-v2.md | bringing the group layer onto the Marmot current profile after the quartz 1.15.2 bump — the nine rules that reach this app, why the room's id and the routing id have to become two values, nine phases from reading both profiles to publishing before applying, and the one fork the library cannot yet settle |
| marmot-kmp.md | moving the group layer off quartz's engine and onto marmot-kmp, mls-kmp and crypto-kmp — why staying on quartz 1.15.2 is staying on an engine that left, the 228 import lines and the one rule that places all but two of them, the group state on a device that must still open afterwards, and eight phases that put the swap in one commit and the evidence around it |
| giza-wallet-removal.md | taking every wallet out of Giza, phased and built but for moving off the wallet library (7b). Covers why a Giza member declines a Bennu peer's wallet proposal instead of ignoring or signing it, why the wallet's kinds are retired rather than freed, why a recovery phrase stays as a key backup that has to derive the same npub and id byte for byte, and why the threshold crypto keeps the build tied to the wallet library until the last phase |
| giza-rebrand.md | forking Bennu as Giza under mobi.giza — what carries the name, what must not be renamed and why, why the desktop data directory changes first, and how the fork keeps merging from Bennu |
Start with the ceremony if you are new to this area; the Marmot notes all assume it.
Read the skipped-keys note before debugging any "the other device never got it"
report — it is silent, and it looks like every other kind of delivery failure. The
resend note is the recovery for it on a signing session, and says which delivery
failures a resend repairs and which heal on their own. The
sync note stands alone, and the dead-code inventory reads as a follow-up to it. The
batch-signing note is a phased plan that has been built: read it after the
derivation note, whose one rule is the same one it is built around. The member
chronicle note is a phased plan that has been built and now carries nothing --
the document kinds it was for are gone -- and reads as the membership note's
unanswered half: what a member who joins late can be given, and the one thing
they cannot. The
jvm-target note is unrelated to all of them: it is a build and packaging story.
The subgroups note is a phased plan that has been built; it assumes both
shared-key notes and reads as the ceremony's second half — what a group does
once it has a key, and what it can say about a group that does not yet.
The Material Design note is a phased plan that has not been built, and is the
only one about what the app looks like rather than what it does; read the
jvm-target note first if you want to know why its adaptive-layout phase exists.
The nsec sign-in note is a phased plan that has been built; it inherits the
key-storage decision from the jvm-target note and drives the navigation state
machine NavigationViewModel.processLocalAccount implements, so read it with the
code open, and read its table of where the build chose differently first.
The npub sign-in note is a phased plan that has been built, and reads as that
plan's out-of-scope note answered: it takes the Identity type and the sign-in
machine as given and asks what an identity with no secret is for, before it asks
how to build one; read its table of where the build chose differently first.
The multiple-profiles note is a phased plan that has been built, and reads as the
third of the sign-in notes: it asks what happens when the device holds two
identities, and its first phase changes one rule the other two share — a seed's
key becomes a credential like any other — so read it with StoredIdentity.merge,
SovereignWalletViewModel.switchToIdentity and the startup screen open, and read
its table of where the build chose differently first.
The npub profile preview note is a phased plan that has been built, and is the
smallest of the plans: it changes the entrance to the direct-message flow and
nothing past it, so read it with StartDirectMessageToNpubOrNip05Dialog and
ChatRoomMessagingViewModel.initiateNewChat open, its four decisions before its
four phases, and its table of where the build chose differently first.
The Marmot v2 note is a phased plan that has been built, and is the largest of
them: it assumes the membership and derivation notes, takes the quartz 1.15.2 bump
as its Phase 0, and is ordered so that the phases that reach other clients come
before the ones that make the app's forks settle the way theirs do; read its table
of nine rules and its two constraints before any phase, and its table of where the
build chose differently before any of the code -- its first row, that a room's
profile picks its pipeline, is the shape of everything that follows, and its last
is the one fork the library cannot yet settle.
The marmot-kmp note is a phased plan that has not been built, and reads as the
Marmot v2 note's Phase 0 come round again: quartz took the engine out, so the
version the v2 work was built on is the last one that has it. Read the v2 note
first — this plan happens entirely on the current-profile side of its first row —
and read this one's two constraints before any phase: the group state already on
devices is what decides whether the move can ship at all.
The ceremony-creation note is a phased plan that has been built. It reads as
the subgroups note's Phase 10 followed through to the screens: read it after
that phase, and its table of findings before any phase. Its second half
removes the nip30303 documents and leaves the member chronicle built but
carrying no kinds, so read it before building on the chronicle note.
The wallet-removal note is a phased plan that has been built but for its Phase 7b. It is how Giza came to keep no wallet: read its constraints and its decisions before any phase, and its table of where the build chose differently before the code. It reads as the rebrand note's D1 and D2 tested: one network shared with Bennu, whose members still bring wallets into rooms Giza is in.
Retired
retired/ holds the notes on Bennu's wallets -- the group's on-chain wallet, its guardians and the subgroup wallet policy, members' guarded wallets, the standalone Electrum client and the group Lightning wallet with its remediation plans. Giza removed all of them (giza-wallet-removal.md). They are kept because they are the only account of what a Bennu member in a shared group is doing, and of the kinds Giza now declines.