Kgothatso NgakoandClaude Opus 5 fc80a089aa build: the Marmot engine comes from marmot-kmp (marmot-kmp, Phase 1)
quartz 1.15.2 -> 2.7.3, and the engine it used to carry from marmot 2.2.1 over mls 1.3.0
over crypto 2.1.0. docs/scripts/marmot-kmp-imports.sh --apply moved 187 lines by the rule;
42 `quartz.marmot` imports stay, which are the event classes quartz kept.

The 854 non-Marmot quartz imports came through the major bump without an edit. All 45
compile errors were in the engine seam, and 44 were one thing: five accessors that were
members of `MlsGroup` in quartz's engine are extension functions in marmot-kmp
(`currentGroupState`, `currentMarmotData`, `currentNostrGroupId`, `currentAdminIdentities`,
`isLocalAdmin`), so 14 files import one now. The 45th, `buildCurrentProfileFrom`, likewise.
No constructor the app drives changed shape, and `GroupEventResult` still has exactly nine
variants -- `MarmotEngine`'s exhaustive `when` compiling is the proof there is no tenth to
drop on the floor.

One change here is not a rename. `MlsGroupPolicy` is new in mls-kmp: quartz's engine
hardcoded Marmot's rules, mls-kmp made them an argument, and every factory defaults it to
`Permissive` -- so the eleven places this app builds a group itself were building a
non-Marmot group. The loud half is that `commitExporter` is then null, `preCommitExporterSecret`
comes back empty and `GroupEventEncryption.encrypt` refuses it ("Group key must be 32
bytes"), which is the one test that failed. The silent half matters more: `Permissive`
greases the leaf's capabilities, which MDK has never been tested against; it knows neither
`0xF2EE` nor the app-data dictionary, so RFC 9420 13.4 refuses a GroupContextExtensions
proposal in a group we are a member of; and it authorizes every commit, proposal and
SelfRemove without a check. So `MarmotGroupPolicy` goes in at all eleven. The
current-profile paths needed none -- `CurrentProfileGroupFactory` and every
`MlsGroupManager` entry point pass it themselves.

1149 tests, 0 failures; compileDebugKotlinAndroid clean; the three audits unchanged.
Import blocks were re-sorted in the touched files only: 253 further files in composeApp
have blocks that were already out of order, and C2 is the reason to leave them be.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-11-18 23:56:27 +02:00
2026-03-24 04:47:19 +02:00
2026-03-23 01:41:39 +02:00
2026-03-23 01:41:39 +02:00

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. commonMain holds most of the code, and androidMain, iosMain and jvmMain hold 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.

Languages
Kotlin 100%