Kgothatso NgakoandClaude Opus 5 b2539773ce test: the state on every device still opens (marmot-kmp, Phase 4)
C1 is the constraint the whole move hangs on: ChatRoom.mlsGroupState is a
MlsGroupState.encodeTls() blob written by quartz 1.15.2 on every device that has ever been
in a group, and a blob the new engine cannot read costs a user every room they are in --
there is no in-place migration from a legacy group.

The argument was checkable before a test was written. quartz 1.15.2's own sources, in the
sources jar beside the artifact in the gradle cache, declare STATE_VERSION = 4; mls-kmp
1.3.0 declares 10 and accepts 1..10, appending only. So every blob in the wild is version
4 and the window covers it six times over.

The measurement is docs/tools/old-state-blob, whose only dependency is
com.vitorpamplona.quartz:quartz:1.15.2 -- it prints a real 1033-byte blob for a legacy
MIP-01 group at epoch 0, which is the shape every room in the wild started as. It is
checked in because once it is gone nothing in the hex says whether the fixture came from
the old engine or the new one, and a fixture written by the new engine would pass while
testing nothing.

MlsGroupStateCompatibilityTest pins it six ways: the fixture is still version 4 (asserted
alone, so a fixture that drifted to 10 cannot make the rest pass vacuously); mls-kmp
decodes it; the group rebuilds from it with 0xF2EE, its nostr_group_id and its name
intact, still reading as legacy; the kind:445 outer key off a restored old group is 32
bytes, which is Phase 1's policy finding pinned against real pre-migration bytes; a
re-save lands on version 10 and still decodes, same group id and epoch; and
RetainedEpochSecrets still round-trips the five fields RoomMlsGroupStateStore stores it as.

No schema change: the blob is opaque to Room and the version is inside it, so 36 stands.

Not done, and not automatable here: one manual upgrade of a profile with real rooms in it.
A fixture is one member at epoch 0; the rooms that matter have epochs, members and a
retained window behind them. That is the last thing between this and a release.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-11-19 00:08:17 +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%