MarmotGroupCreation.finishFoundingInvite invites the founders a room's founding invite never reached, in one commit, every key package first as at creation. It acts only on a room still at epoch 0: the founding invite is the commit that ends epoch 0, and leaving is a commit too, so a founder without a leaf there is one nobody ever invited -- never one who left. CeremonyFollowThrough takes it as step 4 once the room exists, on the coordinator's device; the repository exposes it by room for the detail screen, with the set it would invite. Also fixes what Phase 0 found. MarmotGroupCreation invited the founders through a room read before its routing id was recorded, so on the current profile the engine adopted a second copy of the group under the room id, and the copy at the real address still held only its creator: every later invite took the founding path, with no commit and nobody already in the room told. It now reads the room again first. RobustGroupAdminsJvmTest: a room left without its invite is finished and every founder joins as an admin, on both profiles; a room past its founding invites nobody; a later member on the current profile now gets a real commit. CeremonyFollowThroughJvmTest: step 4's outcomes. jvmTest 1249/1249, compileDebugKotlinAndroid, audits. Co-Authored-By: Claude Opus 5.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.