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
Giza is a group chat app where the group can speak as one. Groups talk over nostr using the Marmot protocol's MLS encryption. A group can also run a key ceremony that gives it a threshold key, which no single member holds. The group uses that key to sign as one: what it decides, who it makes a subgroup of, what it says about itself, each signed by a quorum of its members. Giza keeps no wallet (docs/giza-wallet-removal.md).
It is a Kotlin Multiplatform app with a Compose Multiplatform UI, built for Android, iOS and desktop (JVM).
Giza and Bennu
Giza is a fork of Bennu, and the two still
speak the same protocol. A group can have members on both apps, and a Bennu recovery phrase
restored in Giza opens the same profile. The two install side by side as separate apps
(mobi.giza.android and mobi.giza.ios), each with its own data.
Bennu keeps wallets and Giza does not. A Bennu phrase restored in Giza brings back the profile and nothing else, and a Bennu member who puts a wallet to a group Giza is in sees Giza's members decline to sign for it. docs/giza-rebrand.md explains what the fork changed, what it left alone and why.
What it does
- Group chat. End-to-end encrypted groups on Marmot, with direct messages between members, inside a group or one to one.
- A key for the group. A ChillDKG ceremony, run in the chat, gives the group a threshold key. Members then approve and sign the group's events with FROST, several at a time if needed.
- Subgroups. A group can create subgroups, each with a key of its own, certified by its parent's quorum.
- Profiles. Create a profile from a recovery phrase, sign in with an existing nsec or a phrase, preview one from an npub, or keep several profiles on one device.
The reasoning behind each of these, including the protocol details and the failure modes, is in docs/.
Building
You need JDK 21 and the Android SDK. iOS builds also need Xcode on macOS.
Clone with submodules. The app builds against lightning-kmp-app as a composite build, and that
repository nests its own builds down to secp256k1-kmp:
git clone --recursive https://code.sigidli.com/giza.mobi/giza-kmp.git
In an existing clone, or in a git worktree, which does not get submodules automatically:
git submodule update --init --recursive
Each of the five nested Gradle builds needs a local.properties that points at the Android SDK.
The file is gitignored, so create it in each one:
for d in . lightning-kmp-app \
lightning-kmp-app/experimental/lightning-kmp \
lightning-kmp-app/experimental/lightning-kmp/experimental/bitcoin-kmp \
lightning-kmp-app/experimental/lightning-kmp/experimental/bitcoin-kmp/experimental/secp256k1-kmp; do
echo "sdk.dir=$HOME/Android/Sdk" > "$d/local.properties"
done
Then build each target (on Windows, use gradlew.bat):
- Android:
./gradlew :composeApp:assembleDebug - Desktop:
./gradlew :composeApp:run - iOS: open iosApp in Xcode and run it from there.
docs/jvm-target.md explains what the desktop target needed and how it is packaged.
Checking your work
./gradlew :composeApp:compileDebugKotlinAndroid :composeApp:jvmTest
./gradlew check
check also runs the Material Design 3 audit, docs/scripts/m3-audit.sh. It fails a build that
adds hardcoded spacing or colours, title-case strings, or touch targets under 48dp. CLAUDE.md
lists the UI conventions the audit enforces.
Layout
- composeApp is the shared app.
commonMainholds most of the code, andandroidMain,iosMainandjvmMainhold each platform's own parts. - iosApp is the iOS entry point.
- lightning-kmp-app is a submodule. Giza takes only its key and preference storage from it, and the threshold crypto (FROST, ChillDKG) from the bitcoin-kmp fork it carries.
- docs holds the design notes.
License
Copyright (C) 2026 Machankura
This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.