Commit Graph
1106 Commits
Author SHA1 Message Date
Kgothatso Ngako 64fc85cc98 frost: harden recovery and refresh verification 2026-11-20 01:48:05 +02:00
Kgothatso Ngako c272492b59 frost: repair current shares after reinstall 2026-11-20 01:21:00 +02:00
Kgothatso Ngako 4ef86fd78c frost: add refresh UI and stored-message resend 2026-11-20 00:37:00 +02:00
Kgothatso Ngako 2684b9459a frost: activate refreshed shares with a signed epoch 2026-11-20 00:15:55 +02:00
Kgothatso Ngako ba42d2034d frost: run re-enrollment through candidate activation 2026-11-19 23:54:49 +02:00
Kgothatso Ngako 8a24a0607c frost: add re-enrollment storage and wire kinds 2026-11-19 23:31:51 +02:00
Kgothatso Ngako aaa68a3dbd frost: fence signing sessions by share epoch 2026-11-19 23:24:01 +02:00
Kgothatso Ngako 947685a914 frost: integrate the share refresh primitive 2026-11-19 23:06:35 +02:00
Kgothatso Ngako 7df2dca551 docs: specify FROST share re-enrollment 2026-11-19 22:51:56 +02:00
Kgothatso Ngako 1eda3416c1 chore: use the enrollment-capable lightning baseline 2026-11-19 22:49:45 +02:00
Kgothatso NgakoandClaude Opus 5.5 d4dd87f2a2 docs: the submodule refresh is pushed, and what is left
Material Design conformance / budgets (push) Canceled after 0s
Material Design conformance / tests (push) Canceled after 0s
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-19 22:00:32 +02:00
Kgothatso NgakoandClaude Opus 5.5 70a38d0636 docs: the submodule refresh is built, and what is left to push and check
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-19 21:55:10 +02:00
Kgothatso NgakoandClaude Opus 5.5 051b339a8c build: lightning-kmp-app with reduced FROST enrollment down the chain
67a0376..e4779ff. Every level now pins the tip of the branch it tracks:

  lightning-kmp-app  e4779ff  (master 949bfcb + this bump)
  lightning-kmp      df778bc4 (threshold 065dcf89 + this bump)
  bitcoin-kmp        1982eba  (threshold 9e3c4f8 + bump + FrostReducedEnrollment)
  secp256k1-kmp      ce05021  (threshold tip, reduced enrollment bindings)
  secp256k1-zkp      a04dc1ed (main tip)

Also arriving, from lightning-kmp-app master, three lightning-kmp bumps Giza
calls none of: a node may decline / answers again requests for its offers,
and a swap-in's user key held by a signer. The wallet audit is unaffected.

Giza does not call enrollment yet; see docs/submodule-refresh.md, Phase 6.

compileDebugKotlinAndroid, jvmTest (1171 tests) and check pass on Linux.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-19 21:54:58 +02:00
Kgothatso NgakoandClaude Opus 5.5 33492cfff0 docs: carrying reduced FROST enrollment up the submodule chain (plan)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-19 21:37:05 +02:00
Kgothatso NgakoandClaude Opus 5 3aef54b549 Merge branch 'claude/marmot-kmp-migration-ab8940' into giza
Material Design conformance / budgets (push) Canceled after 0s
Material Design conformance / tests (push) Canceled after 0s
The Marmot group layer moves off quartz's engine, which quartz 2.3.0 took out,
and onto marmot-kmp over mls-kmp over crypto-kmp. Nine phases: the rule table as
a reversible script, the swap itself in one commit with the policy finding inside
it, the names quartz 2.x gave the kinds, a stand-in on the library's own client,
C1 measured against a real state blob from the engine the app shipped, the
skipped-keys gap closed, the authored fork probed and still open, a build guard so
the engine cannot come back from quartz, the sender ratchet as its own row with
the receive-side write beside it, and a v36 database opened at v37 to show an
existing install survives the schema change that followed. docs/marmot-kmp.md.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-11-19 18:59:23 +02:00
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
Kgothatso NgakoandClaude Opus 5 e07bb68014 feat: the sender ratchet as its own row, and the receive side beside it (marmot-kmp, Phase 8)
The piece Phase 7 deferred, in both directions, because they are one question:
a group's state is a few kilobytes of ratchet tree, group context and epoch
secrets, and the app was rewriting all of it to record things that moved a
counter.

Sending an application message advances exactly one thing -- this leaf's entry
in the secret tree (RFC 9420 §9) -- so the library carries the position as its
own record, `MlsGroupStateStore.saveSenderRatchet`, in the spirit of OpenMLS
keeping `message_secrets` apart from `group_state`. Giza defaulted that to
false, which sent the manager back to a full save per message. It is now a
`MarmotSenderRatchet` row, one per room, schema 36 -> 37 with an AutoMigration.
The bytes are stored as the library wrote them -- the `MarmotPublishObligation`
precedent, not the retained-epoch one -- because a record whose whole job is to
never go backwards is safest when nothing here re-encodes it; the epoch, leaf
and generation sit beside it, read off those same bytes, so they cannot drift.

The hazard this introduces is an ordering, and it is in the app's code, not the
library's. `MlsGroupManager.restoreAll` applies the record itself. A room joined
after the engine restored is loaded from its row by `MarmotEngine.groupFor`
instead, and that has to apply the record BEFORE `adoptGroup`, because adopting
persists and persisting rewrites the row from the group being adopted. The other
way round, the next restart re-emits generations already published, under AEAD
keys and nonces already used.

Finding the test that could tell the two orders apart took two goes. The first
asserted the row after a lazy load and passed with the order inverted: a state
saved before this leaf ever sent has no ratchet entry, `exportOwnSenderRatchet`
returns null, and the adopt writes nothing. The order cannot matter until the
stored state holds a position of its own behind the record's, and a received
message is what puts one there. With one receive in the middle the inverted
order fails with expected:<2> but was:<1>.

The receive side is a full save, from `MarmotEngine.processGroupEvent`, which
`NostrDao` now reads inbound events through so a second caller cannot forget it.
And a correction to Phase 5, which said an unwritten row still lost the late
message. It does not: mls-kmp writes the skipped keys beside the positions they
belong to, so an unwritten row is an older COHERENT state, and a position that
has not passed the late generation derives it forward. quartz's engine saved the
positions and dropped the keys -- that pair is what lost messages. The cost of
an unwritten row is the re-deriving, against SecretTree's thousand-step cap. The
reason the write lands now is the send side: until this change every send wrote
the whole state, so the row could not fall far behind inside an epoch.

1167 tests across 156 classes, 0 failures; Android and JVM compile clean; the
four audits unchanged. docs/mls-skipped-keys.md loses its mitigation claim and
gains the correction; docs/marmot-kmp.md gains Phase 8.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-11-19 09:55:31 +02:00
Kgothatso NgakoandClaude Opus 5 7fb56b8f8f docs: the move is built, and what it does not claim (marmot-kmp)
Phases 0 to 7, one commit each but for 5 and 6, which share one because the fork probe
produced no code. 1161 tests, 0 failures; compileDebugKotlinAndroid and compileKotlinJvm
clean; four audits green, the new one among them.

Three things it does not claim, said at the top rather than left to be discovered at the
end of a phase. No manual upgrade of a profile with real rooms has been done, and that is
the last check before a release -- a fixture is one member at epoch 0. The sender ratchet
record and the receive-side write are deferred together, because they are one decision
about how often this app persists a group and they want a schema change. And the authored
fork is still not settled; Phase 6 probed it and the gap is the library's, unchanged.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-11-19 00:17:24 +02:00
Kgothatso NgakoandClaude Opus 5 f0f1c179df build: the engine cannot come back from quartz (marmot-kmp, Phase 7)
marmotAudit runs docs/scripts/marmot-kmp-imports.sh --check from `check`, beside the M3,
brand and wallet audits. Verified both ways: silent on a clean tree, and on a tree with
one import put back it names the file and the line and fails with a pointer to the note.
That is C2 made enforceable -- a cherry-pick from a Bennu still on quartz 1.15.2 brings
the old spelling back, and "re-run the rule" is advice until a build failure makes it a
step.

The other three items of this phase are named in the note rather than done, each for a
reason:

- The app's own copies: nothing to delete. CommitOrdering is still live in NostrDao's
  reindex sweep and MarmotInboundManager's epoch tracker, and marmot-kmp has no
  CommitOrdering at all -- the convergence engine replaced the idea, not the class. Under
  D4 the legacy pipeline keeps its behaviour, so the comparator retires with the profile.
- The sender ratchet record wants a new table, so schema 36 -> 37 and an AutoMigration,
  and the interface says the write MUST be durable before it returns or a lost position
  reuses an AEAD key and nonce pair. A per-message write path with a correctness hazard
  does not belong in the tail of a migration whose discipline was D5. It is the obvious
  next task, and it is the same shape as the receive-side write Phase 5 pinned: one piece
  of work that decides how often this app persists a group, in both directions.
- Durable ingest dedup is taken by MarmotManager, not by MarmotInboundProcessor, so it
  needs the client D1 deferred. Phase 3 is where that stopped being hypothetical.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-11-19 00:16:21 +02:00
Kgothatso NgakoandClaude Opus 5 3b2b5e3614 test: the skipped keys, half closed and half pinned (marmot-kmp, Phases 5 and 6)
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>
2026-11-19 00:15:28 +02:00
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
Kgothatso NgakoandClaude Opus 5 763edcde9f test: the app's orchestration against the library's own client (marmot-kmp, Phase 3)
`MarmotStandIn` moved to marmot-kmp's managers in Phase 1 with nothing but its imports
changing, and it stays as it is: the convergence and lifecycle tests need a processor they
can reach into -- `recordLocalCommit` with a state snapshot of their own, `buildAppEvent`
with a payload they wrote -- which a `MarmotManager` would take away.

So the second stand-in is additive. `MarmotClientStandIn` is a `MarmotManager` over an
`InMemoryMlsGroupStateStore` and a publisher that says yes, with no message store and no
KeyPackage store because both are nullable and a client that persists nothing is all a
test wants from one. It is what Amethyst, its desktop app and the `amy` CLI drive.

The two are not redundant, and the difference is the difference between the two questions
this migration has to answer. In CurrentProfileInteropJvmTest the test's own code decides
how the Welcome is sealed and what an application payload looks like, and asks whether two
engines agree. Here the library decides -- `addMemberInvites` picks the commit's shape,
`MarmotWelcomeSender` wraps the Welcome -- and the question is whether the app's own
orchestration, `MarmotEngine` and the DAOs and the outbound queue, reaches the same group
as the orchestration the library ships. It does, on the first run: the app joins a group
the client made and invited it to, under the routing id the client minted; it files and
attributes a `buildTextMessage` from it; and the client decrypts what the app's outbound
path sends and decodes it as a canonical payload.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-11-19 00:05:11 +02:00
Kgothatso NgakoandClaude Opus 5 9bc05c112d refactor: the names quartz 2.x gave the kinds (marmot-kmp, Phase 2)
Most of this phase was answered by Phase 1 rather than built. `GroupEventResult` still has
exactly nine variants -- `MarmotEngine.inRoom` is an exhaustive `when` used as an
expression, so the compiler says so rather than a reading of the source. The convergence
and lifecycle surface takes and returns what `settleLater` and `awaitSettled` already
expected, `allowsOutboundWork` included. `stageAddMember` -> `StagedCommit` ->
`gate.prepare` -> `installState` needed no edit. And no test's assertions moved: seven
fixtures now build their group with `MarmotGroupPolicy` as the app does, which is a
construction-site change, not a weakened expectation.

What was left is the six classes quartz 2.x renamed to match what the NIPs call the kinds,
and kept deprecated typealiases for: SealedRumorEvent -> SealEvent, ChatMessageRelayListEvent
-> DmRelayListEvent, RelayFeedsListEvent -> FavoriteRelayListEvent, LnZapEvent ->
ZapReceiptEvent, LongTextNoteEvent -> LongFormContentEvent, ChannelListEvent ->
PublicChatListEvent. 104 references in 25 files; same packages, so each is an identifier
rename. None reaches a string the app persists -- no Room column, no string resource, no
kind number -- and after it the build has no quartz deprecation warnings left.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-11-18 23:59:35 +02:00
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
Kgothatso NgakoandClaude Opus 5 1775ae7d4c build: the rule that says where a Marmot class comes from (marmot-kmp, Phase 0)
docs/scripts/marmot-kmp-imports.sh, with --apply, --revert and --check. The destinations
in it are not derived from the packages' names but from listing what quartz 2.15.1 still
has under `marmot/` against what marmot-kmp 2.2.1 and mls-kmp 1.3.0 declare, which is how
the split inside `mip00KeyPackages`, `mip02Welcome`, `mip03GroupMessages` and
`mip05PushNotifications` came out: the events and tags stay, the five stores and managers
beside them move. marmot-kmp imports the quartz half itself.

Applied and reverted on a clean tree it moves 187 lines and puts all 187 back -- 79 onto
marmot-kmp, 80 onto mls-kmp, 27 onto crypto-kmp, one KDoc line -- and leaves the 42
`quartz.marmot` event imports standing, which is the count the plan's table predicts.

Reversible because the fork still cherry-picks from upstream, upstream is on quartz 1.15.2
with the engine inside it, and every line this touches is one a cherry-pick will conflict
in. The resolution is to re-run the rule, not to read the diff.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-11-18 23:43:46 +02:00
Kgothatso NgakoandClaude Opus 5 f2059eb1b5 docs: the Marmot engine left quartz, and a plan to follow it (marmot-kmp, the plan)
quartz 2.3.0 dropped the Marmot engine. Everything this app imports from
`com.vitorpamplona.quartz.marmot` but the event classes -- the MLS engine, the three
processors, convergence, the publish gate, the app components, the KeyPackage managers --
is in marmot-kmp over mls-kmp over crypto-kmp now, and quartz 1.15.2 is the last version
that still has it inside. So the app is not behind on a version; it is on a branch of the
engine that ended.

The note is the move: where each of the 228 import lines goes and the one rule that places
all but two of them, the two constraints (the group state already on devices, and that the
fork still cherry-picks from a Bennu that is on 1.15.2), the six decisions -- keep
`MarmotEngine`, pin quartz to the 2.7.3 marmot 2.2.1 was built against, declare crypto-kmp
rather than inherit it -- and eight phases that put the swap in one commit with the
evidence around it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-11-18 23:43:46 +02:00
Kgothatso NgakoandClaude Opus 5.5 8b06679584 docs: follow Bennu by cherry-picking, and record what is left (wallet removal, Phase 9)
Material Design conformance / budgets (push) Canceled after 0s
Material Design conformance / tests (push) Canceled after 0s
The rebrand's Phase 9 now takes fixes from Bennu one commit at a time
(W1): a merge would bring every wallet change back as a conflict, and
Giza's schema has its own version 36. The wallet-removal plan records
itself as built but for Phase 7b and Phase 9's device checks, which need
an iOS build, devices and a Bennu build.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 16:15:37 +02:00
Kgothatso NgakoandClaude Opus 5.5 b27ed2a05f docs: retire the wallet notes, and guard against a wallet coming back (wallet removal, Phase 8)
The 23 wallet notes move to docs/retired/ with a banner; every link between
notes is rewritten for the move and checked. The index lists them as one
Retired paragraph, and seven kept notes carry a line on what changed. The
README and CLAUDE.md describe a Giza with no wallet.

brand-audit.sh loses its "bennu/ exception: every such tag was a wallet's,
so one now is a wallet coming back. wallet-audit.sh --check, in check and
in CI, fails on a retired kind in the app's code, a lightning-kmp import,
a file named for a wallet's pieces, or sats in a string.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 16:15:13 +02:00
Kgothatso NgakoandClaude Opus 5.5 005cbc2f23 refactor: composeApp stops importing lightning-kmp (wallet removal, Phase 7a)
W3: a Lightning invoice in a note is a card that opens a lightning: link
in the device's own wallet app, undecoded -- decoding was lightning-kmp's,
and paying from the card was never wired. The dead pay and zap hooks go.

Lightning.randomBytes becomes quartz's RandomInstance; the tests'
LocalKeyManager becomes PhraseKeys; NodeParamsManager.chain becomes
PROFILE_CHAIN, the mainnet constant every profile's preference files are
named under.

What is left of the library is storage (keystore, credentials, seed file,
preferences). Moving it into the app and off the composite build is
Phase 7b, which needs an iOS build and a device to check, and is left for
its own branch.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 16:08:52 +02:00
Kgothatso NgakoandClaude Opus 5.5 84be1c5beb refactor: no node behind a recovery phrase (wallet removal, Phase 6)
PhraseKeys derives a phrase's nostr key (NIP-06, m/44'/1237'/0'/0/0) and
its profile id (hash160 of m/50'/0', the old node key) with bitcoin-kmp's
DeterministicWallet. ForkCompatibilityTest's Phase 0 pins pass unchanged
through it, so the same phrase is the same person with the same
preference files.

No profile starts a node: Identity.business, startupNode and its state
machine, the platform start/schedule/stop actuals, LightningApplication,
BusinessManager.initialize, the NFC hooks and POST_NOTIFICATIONS go. A
switch is clearing the identity and nothing else. Copy that promised funds
or a wallet is reworded, and the switcher's badge says Recovery phrase.

Forgetting a phrase profile is still refused (now PhraseAttached): the
phrase would derive the key again, and offering it is new UI.

iosMain was edited without an iOS build.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 16:03:47 +02:00
Kgothatso NgakoandClaude Opus 5.5 9c2cbf0295 feat: schema 35 -> 36, the wallets' tables and rows dropped (wallet removal, Phase 5)
MIGRATION_35_36, by hand: the wallets' chat lines; GroupTransaction; every
signing session over a transaction or a sweep, with its items and its
members' messages; the other fifteen wallet tables, children first; and
FrostSigningItem.inputIndex, DkgSession.guardianDelay and
ChatMessage.lightningFactKey. DkgSession.walletPolicy stays: the join
screen reads a Bennu ceremony's tag from it. The 36 schema is committed.

The wallet line-type constants and the transcript's arms for them go with
the rows they named.

jvmTest: 1,150 run, 0 failed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 15:54:21 +02:00
Kgothatso NgakoandClaude Opus 5.5 c6b231fa84 refactor: remove the group's on-chain wallet, guardians and the subgroup wallet policy (wallet removal, Phase 4)
wallet/ (Electrum included), nostr/wallet/, the policy and guardian tags,
GroupWalletDerivation, GroupWalletManager, GuardianDerivation,
GuardianManager, ProposedSpend, three screens with their view models,
states and routes, and FROST's spend half.

FROST is back to signing events. Every transaction proposal from a Bennu
peer is filed declined without being read, and the decline goes out
through advance(). Certificates and ceremonies carry no wallet tag; a
guarded subgroup's ceremony is filed and not joined, and its join screen
says why (W5). A key state carrying a wallet's certificate is declined.
The last bennu/ derivation tag leaves the code, and the last wallet pins
with it.

jvmTest: 1,148 run, 0 failed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 15:48:11 +02:00
Kgothatso NgakoandClaude Opus 5.5 db38640e57 refactor: remove member guarded wallets (wallet removal, Phase 3)
The member-wallet events, MemberWalletManager, MemberWalletDerivation, the
repository and DAO, five screens with their view models, states and routes,
and the 74 strings only they read. GuardianManager stops reading member
certificates. The entities stay until Phase 5's migration.

Guardians and the subgroup wallet policy move to Phase 4: they are built
into the group's on-chain wallet and cannot leave before it and compile.

jvmTest: 1,311 run, 0 failed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 15:32:04 +02:00
Kgothatso NgakoandClaude Opus 5.5 1bd0761339 refactor: remove the group Lightning wallet and Iceberg (wallet removal, Phase 2)
The Lightning events, managers, Iceberg ceremony, wallet/lightning, the
repository, five screens with their view models, states and routes, the
four DAOs, and the regtest network with its build wiring. The entities
stay until Phase 5's migration.

FROST's sweep path goes here rather than in Phase 4, since it was built on
GroupSweep: a sweep that arrives is filed declined without being read.
Lightning kinds fall to the retired-kinds arm; existing Lightning lines
stay as settled lines that open nothing. The 147 strings Phases 1 and 2
left unread go, and a Phase 1 test name that said Bennu is renamed.

jvmTest: 1,440 run, 0 failed, 0 skipped.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 15:25:15 +02:00
Kgothatso NgakoandClaude Opus 5.5 8e0f1bd38a feat: Giza neither offers nor signs a wallet (wallet removal, Phase 1)
A Bennu member can put a wallet to a group Giza is in. Giza can no longer
check one, so it declines on arrival, out loud: the proposal is filed as a
declined session and advance() publishes the DECLINE, which the group
counts. Refusing used to be silent, which looks like a phone in a pocket.

- RetiredKinds: 30331-30337 and 30350-30366 stay Bennu's, never reused.
- WalletRefusal: what is a wallet's to sign, read by tag name so it
  outlives the wallet's parsers. approve() declines one instead.
- A retired kind is one line or none in the transcript, never a raw bubble.
- No Lightning dispatch, no guarded-wallet forwarding, no key answers.
- The detail and profile screens and the subgroup picker lose their
  wallets; a guarded room says why it offers no subgroup (W5), and
  certificates carry no wallet tags.
- The wallet tests this behaviour breaks are deleted with it.

jvmTest: 1,495 run, 0 failed, 2 skipped.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 15:14:53 +02:00
Kgothatso NgakoandClaude Opus 5.5 94b45c0bc8 test: pin a recovery phrase's npub, profile id and host key (wallet removal, Phase 0)
Through LocalKeyManager, the code Phase 6 replaces, on NIP-06's own test
vector. A different npub would be a different person, and a different id
would lose the profile's preference files.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 14:59:22 +02:00
Kgothatso NgakoandClaude Opus 5.5 60e878e74f docs: a phased plan to remove the wallets from Giza
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 14:52:31 +02:00
Kgothatso NgakoandClaude Opus 5.5 caf1fb1855 test: name the pinned tags in comments, not test names (fork, Phase 8)
Material Design conformance / budgets (push) Canceled after 0s
Material Design conformance / tests (push) Canceled after 0s
ForkCompatibilityTest's method names began with `bennu`, which is neither a comment nor a
"bennu/ tag, so the brand audit -- and with it ./gradlew check -- failed from 851ff0c8 on.
The audit ran in Phase 6 and was not run again over Phase 8. Each test now carries the tag
it pins in a comment above it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 12:48:57 +02:00
Kgothatso NgakoandClaude Opus 5.5 bad6012940 docs: the repository is giza.mobi/giza-kmp (fork, Phase 1)
The README's clone URL and the plan guessed machankura/giza-kmp. The repository was made
under giza.mobi, with Bennu's full history and giza as its default branch at 4e106fb5.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 12:44:31 +02:00
Kgothatso NgakoandClaude Opus 5.5 851ff0c8c2 test: Giza derives what Bennu derives, every tag pinned (fork, Phase 8)
ForkCompatibilityTest pins each mantra/ and bennu/ derivation tag through the
function that hashes it: the ChillDKG host key, the Marmot shared-key tweak,
the group Lightning basepoints, the Iceberg pool label and the session,
contribution, commitment, seed and transcript hashes, the member wallet id and
possession message, and the group wallet address and guardian root. A sweep
that renames one of them now fails a test rather than moving a group's coins
and splitting Giza from Bennu.

The vectors come from this tree. A diff against 4e106fb5 shows that the files
holding the tags differ only in packages, imports, comments and the database's
type name, so the vectors are Bennu's too.

docs/giza-rebrand.md gains a table of where the build stands and what turned
out differently, the twelve bennu/ tags first.

jvmTest: 1651 run (1643 + 8), 0 failed, 2 skipped. m3Audit and brandAudit pass.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 11:00:44 +02:00
Kgothatso NgakoandClaude Opus 5.5 c0f1b3d5e3 build: Giza's version numbers and an upload key from outside the repo (fork, Phase 7)
versionCode 1 and versionName 0.1.0: a new applicationId has no store history
to stay above. The desktop packageVersion stays 1.0.0, since jpackage refuses
a DMG whose major version is 0.

Release builds are signed with an upload key named by gradle properties
(giza.upload.*) or the environment (GIZA_UPLOAD_*), and are unsigned without
them, as before. Key files are gitignored. It must never be Bennu's key.

The store records, provisioning and listings are outside this tree.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 11:00:44 +02:00
Kgothatso NgakoandClaude Opus 5.5 5b92b83869 chore: tooling, docs and a guard for the name (fork, Phase 6)
- rootProject.name is Giza. Res is pinned, so no import moves.
- Regtest: GIZA_REGTEST, GIZA_SPLICE_DELAYS and the gizaRegtest task input;
  node aliases giza-lsp and giza-payer.
- README describes Giza and says what it shares with Bennu: one network, one
  derivation, and a recovery phrase that must not run in both apps at once.
  The clone URL is the planned giza-kmp repository, which does not exist yet.
- docs/README.md is titled Giza docs and says how to read the documents
  written while the app was Bennu.
- CLAUDE.md gains the rule: name the app Giza, never name Bennu outside a
  comment, and never rename a mantra/ or bennu/ derivation tag.
- docs/scripts/brand-audit.sh --check, run by check (brandAudit) and by the CI
  budgets job, fails on Bennu anywhere in composeApp, iosApp, testing or the
  gradle scripts except in a comment or a "bennu/ tag. It catches the strings
  a merge from Bennu brings in, which giza-rename.sh cannot word.
- The plan gains the twelve bennu/ tags, missed when it was written.

jvmTest: 1643 run, 0 failed, 2 skipped. compileDebugKotlinAndroid, m3Audit and
brandAudit pass.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 10:53:17 +02:00
Kgothatso NgakoandClaude Opus 5.5 4f3f0da3ca feat: Giza in everything a person reads and on the wire (fork, Phase 4)
- Strings: app_name and the giza key say Giza, as do the eight values that
  named Bennu. Two keys that contained the name are renamed. Two messages that
  meant "has no Marmot key package yet" now say so, since a Bennu user counts.
- Restore: when a recovery phrase is recognised, the sign-in screen says to stop
  using it anywhere else. A seed running in Bennu and Giza at once is two copies
  of one Lightning wallet, which can lose funds.
- Desktop: the window title and the unlock heading come from the catalogue.
  The installers are named Giza (giza on Linux), with a fixed Windows upgrade
  UUID of their own so a Giza MSI never upgrades a Bennu one.
- iOS: PRODUCT_NAME and the product reference are Giza.app.
- Wire: the client tags are Giza and giza. Nothing compares them.
- The twelve bennu/ derivation tags stay as they are. They are hash inputs like
  mantra/, and a Bennu peer and a Giza peer derive the same keys through them.
  Each now has a note saying so. The rebrand-history comments count four.

jvmTest: 1643 run, 0 failed, 2 skipped. compileDebugKotlinAndroid passes.
m3-audit: all budgets met. It differs from the baseline only by the new restore
line (one more stringResource and one more bodyMedium).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 10:46:57 +02:00
Kgothatso NgakoandClaude Opus 5.5 34e802ce6f refactor: packages, classes and Res under mobi.giza (fork, Phase 3b)
docs/scripts/giza-rename.sh, run over the moves of Phase 3a:

- com.machankura.bennu.{compose,android,desktop} -> mobi.giza.{...}, in
  package lines, imports, fully qualified references, the manifest, mainClass,
  the Android namespace (one value with applicationId again), the m3Audit
  source path, the six docs/scripts tools, and the source links in docs/;
- Res moves from bennu.composeapp.generated.resources to
  mobi.giza.compose.resources, now pinned with packageOfResClass so a later
  rename of the root project leaves the imports alone;
- BennuDatabase, BennuTheme and the other eleven Bennu identifiers are Giza*.

The script's search is now the same pattern as its sed expressions, so on a
renamed tree it finds nothing and changes nothing.

Checked against the Phase 0 baseline: jvmTest 1643 run (1642 + AppDirJvmTest),
0 failed, 2 skipped; compileDebugKotlinAndroid passes; m3-audit prints the
baseline report line for line. iOS is not compiled on this Linux host.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 10:40:27 +02:00
Kgothatso NgakoandClaude Opus 5.5 30d5feaf87 refactor: move the sources to mobi/giza, paths only (fork, Phase 3a)
docs/scripts/giza-rename.sh --moves-only: com/machankura/bennu becomes
mobi/giza in all six source sets, the nine files named Bennu* are named Giza*,
and the Room schema directory moves to mobi.giza.compose.database.GizaDatabase.
Every source file is a 100% rename, so log --follow and blame go straight
through.

This commit does not compile on purpose: the next one rewrites the contents.
The script, which does both, comes with it so a merge from Bennu can re-run it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 10:35:04 +02:00
Kgothatso NgakoandClaude Opus 5.5 78d913aaf2 feat: Giza installs beside Bennu and never opens its data (fork, Phase 2)
The store identities move first, before any rename, because they are what keep
two installed apps apart:

- the desktop data directory is giza, not curated, which is Bennu's. A Giza
  build in curated would open Bennu's database, key store and wallet;
- the Android applicationId is mobi.giza.android (mobi.giza.android.debug on
  debug). The namespace follows with the sources in Phase 3;
- the iOS bundle id is exactly mobi.giza.ios, without the $(TEAM_ID) suffix
  the template appended to Bennu's;
- the regtest compose project is giza-regtest, so it does not replace Bennu's
  containers. The ports are shared, which the README now says.

AppDirJvmTest checks the directory name on all three OS branches.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 10:34:53 +02:00
Kgothatso NgakoandClaude Opus 5.5 afd43434cc chore: Giza is a fork of Bennu; CI runs on giza (fork, Phase 1)
The workflow triggered on pushes to mantra, a branch two rebrands old, so on
Bennu it only ever ran for pull requests.

The remote steps of Phase 1 -- the new repository, its remotes and default
branch -- are outside this tree and left to the owner.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 10:28:50 +02:00
Kgothatso NgakoandClaude Opus 5.5 2a7fc7a08a docs: a plan to fork Bennu as Giza under mobi.giza
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 10:28:11 +02:00
Kgothatso NgakoandClaude Opus 5.5 4e106fb56d docs: a README that describes Bennu
Replaces the Kotlin Multiplatform template with what the app does, how
to build it with its nested submodules and their local.properties, how
to check a change, and where the design notes live.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-12 15:06:08 +02:00
Kgothatso NgakoandClaude Opus 5.5 8dd09aa083 chore: license the project under GPL-3.0-or-later
Adds the GPLv3 text as LICENSE and a License section with the notice to
the README. Version 3 because the Apache-2.0 dependencies, lightning-kmp
among them, are compatible with it and not with version 2.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-10 20:33:16 +02:00