Kgothatso NgakoandClaude Opus 5 1321962b3f test: the version the app ships, opened by the version it builds (marmot-kmp, Phase 9)
Phase 4 settled the blob and left the database alone, because there was nothing
to settle: the state is opaque to Room and its version is inside it. Phase 8 added
a table, and that turns "does an existing install still open?" from a question
about MLS into a question about Room. They fail differently. A blob the engine
cannot read costs one room; a migration Room cannot find costs the app, on every
device that has ever had it, on the first launch after the update.

That second one is also the easiest here to ship by accident, because a fresh
install never migrates anything. Measured rather than assumed: with
`AutoMigration(from = 36, to = 37)` commented out, 32 database tests ran and 4
failed -- all four of them the new ones.

ShippedProfileUpgradeJvmTest builds a v36 database on disk from the exported v36
schema, down to its indices, its room_master_table identity hash and its
user_version, puts a profile and two rooms in it with the Phase 4 blob in one, and
opens it with the app's own getRoomDatabase. Four claims: it reaches v37 with
Room's own identity hash stamped and every table's columns and indices equal to
37.json's; the legacy room's bytes come back unchanged and MarmotEngine.groupFor
restores a group with its 0xF2EE metadata and a 32-byte kind:445 key; opening the
profile rewrites nothing, which is asserted only after checking the restore held
the room; and the new table takes a row keyed to a ChatRoom that predates it.

Room opens lazily, so a test that builds a database and closes it migrates
nothing. The first version of this did that and failed on user_version still
reading 36.

The blob itself moves to OldEngineBlob in commonTest, read by both tests. The
only thing those bytes are worth is that they are old ones, and a blob living in
two files can be regenerated in one of them.

1171 tests across 157 classes, 0 failures; the four audits unchanged.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-11-19 18:57:12 +02:00
2026-03-24 04:47:19 +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%