ConfederationReachableJvmTest runs a local confederation DKG and two
signatures -- one plain, one under a taproot tweak checked against the
P2TR output key -- through the desktop JNI library Giza loads. A compile
proves only that the classes are on the classpath; a libsecp256k1 built
from an older secp256k1-zkp fails here with an UnsatisfiedLinkError.
Not a ceremony: dkgLocal and signLocal run every role in one process,
and nothing in the app calls them.
The plan records Phases 1-4, the Android launch over an existing build,
and why secp256k1-kmp's instrumented tests do not build (FrostRefreshTest's
spaced method names, from before this update).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Comments that state a current version now state the new one: the material3
notes in the catalogue, Theme.kt's expressive note, m3-audit.sh's role list
(ColorScheme declares the same getters at 1.12.0-alpha03), the Kotlin/Native
workaround's note, and two lines of quartz-mls-marmot-update.md. Notes that
record what was true when they were written are left. The plan's status
names what is left: pushing the four submodule branches, Phase 8, and
Compose 1.13.0 once final.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
lightning-kmp-app moves to d87af50, which carries Kotlin 2.4.21 down to
secp256k1-kmp, and engine-interop/new follows the app as its comment asks.
The declared Kotlin now matches the stdlib quartz already resolved, and the
resolved graphs are unchanged. secp256k1-kmp and bitcoin-kmp tests,
lightning-kmp-app's library compile and engine-interop all pass. The
Kotlin/Native workaround stays until a mac links without it.
The submodule commits are on claude/dependency-update branches, not pushed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
lightning-kmp-app moves to 63a48b2, which carries AGP 9.5.1 down to
secp256k1-kmp. AGP 9.5 registers a Compose Preview runfiles task on every
Compose variant and refuses to create it unless that variant's unit tests
exist and include Android resources, so unit tests include resources and run
for release as well as debug. Merged manifests are identical to 9.4.0's.
The submodule commits are on claude/dependency-update branches, not pushed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
check passes with Phase 0's audit numbers unchanged and one more test. The plan now says it
is built, the rebrand's brand-assets phase points to it, and the index entry says what is
still waiting on a mac, a phone and Windows.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Desktop had no icon at all, so jpackage and the window showed Java's. The installers now
name a generated .icns (Apple's Big Sur plate), .ico and .png, and the window takes the
in-app logo. The .deb carries the icon and its .desktop entry points at it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The pixel-art rock and its two unhelpfully named files give way to three generated PNGs,
one per appearance: opaque RGB with no alpha for light, as App Store Connect requires; the
mark on transparency for dark, which iOS backs itself; grayscale for tinted, which iOS
tints by luminance. Not yet built in Xcode.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
compose-multiplatform.xml, the mark in the middle of every QR code, is generated from the
master: the same shape as before -- a background square, then the mark -- with the old
#FF3A1A and black swapped for black and sand. AppLogoDrawableJvmTest samples it where the
master is unambiguous, and fails against the drawable it replaces.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Compose 1.13.0 is still rc01, so this takes 1.12.2 and the material3 built
against 1.12. The pinned material3 1.10.0-alpha05 had been built against
Compose 1.9.3. coil and qrose are here because they need Compose 1.12.
Adaptive stays at 1.2.0, which the new navigation suite still asks for.
On Android, Google's material3 moves to 1.5.0-alpha22 underneath.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docs/scripts/app-icons.py renders the iOS appearances, the desktop .icns/.ico/.png and the
in-app logo's vector XML from docs/brand/giza-sphinx.svg, with Python and ImageMagick
alone. It writes the .icns itself, since iconutil is macOS-only, and strips PNG
timestamps so a rerun leaves the tree clean.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The designer's Transparent Cutouts SVG is committed unchanged as docs/brand/giza-sphinx.svg.
Its path is the one Android's launcher layers already carry. Measuring it showed its
sub-paths are disjoint, so the fill rule does not make the cutouts; the plan said it did,
and now says why it does not.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
coil 3.6.x and qrose 1.2.0+ need Compose 1.12, so both move with Compose in
Phase 3 instead. ktor 3.6 pulls ktor-openapi-schema (kaml, snakeyaml-engine,
urlencoder) and kotlinx-datetime's 0.8.0-0.6.x-compat build, a superset of
0.8.0. IdentitySwitchJvmTest's timeout fails 1 in 4 uncached runs both before
and after this change.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Eight libraries, the sqldelight plugin alias and six version keys that no
build script references, and the commented-out lines that named them or
Room 2's aliases. The jvm, debug and release runtime graphs are identical
to Phase 0's.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
marmot-kmp.md's D2 and its out-of-scope item point here; the docs index reads
this note after it; CLAUDE.md says the daemon is Java 21, a first build needs
the network, and a version moves in the catalogue and the lock together. The
plan's status: built but for mls-kmp 1.4.0's release, the mac half of
Phase 6, and Phase 8's manual checks. check green, jvmTest 1392/1392.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
magpieLockAudit runs docs/scripts/magpie-lock-audit.sh from check, beside the
M3, brand, wallet and marmot audits. Every catalogue library in a group Magpie
serves must be declared strictly (D3) and have a lock line for its root,
-jvm and -android modules -- read as text, so a bump made on one platform is
caught on any. Verified both ways: silent on a clean tree; a dropped lock line
or a plain, unlocked bump names the module and fails the build.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
quartz 2.20.0's lines went: under the strict pin, marmot's request for it is
never looked up, and every classpath resolves under a frozen lock without
them. Checked here: a frozen lock refuses a version it does not hold, with
Magpie's own instruction, and an offline build from a fresh daemon resolves
from the mirror. The iOS lines need a mac, and the freeze waits for them.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
giza deleted FoundingAdmins.check (remove-founding-admins-card): it
cannot tell a founder left out by a buggy creator from one the group
demoted, and every founder is an admin when the room is made. RoomAdmins
drops its missing-founders guard, and A4 says why.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2.20.1 changes two files of quartz's in-process relay server, which neither
the app nor marmot-kmp's main source imports, so it is inert here. The strict
pin wins over marmot 2.3.0's request for 2.20.0, the graph moves by quartz
alone, and check is green: jvmTest 1392/1392, MarmotClientInteropJvmTest 3/3.
mls-kmp 1.4.0 (5b) waits: it is tagged but released nowhere yet.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
C1 measured again on mls-kmp 1.3.1: the old-blob, shipped-profile, store,
sender-ratchet, skipped-generation and fork tests are green untouched, and the
authored fork is still open. The re-save test only said "newer than 4", which
a library that moved to 11 would pass, though a bump is what an older build
cannot read back; the seventh case pins 10 exactly, checked red at 11.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docs/tools/engine-interop runs marmot-kmp 2.3.0 over mls-kmp 1.3.1 against
quartz 1.15.2's engine -- the one a Bennu peer on that version runs -- in two
JVMs over a pipe, since one build cannot hold two versions of the quartz group.
Each side creates a room in turn; the other joins by Welcome, applies two more
commits and reads a message each way at every epoch. 20 checks, all green, so
mls 1.3.1's new epoch-0 shape costs nothing against the old engine.
The note records Phase 3, including the first draft of the epoch-0 test, which
asserted a restore-time repair mls-kmp drafted and then removed before 1.3.1.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
None of the four is on Maven Central at these versions: they are released on
Nostr + Blossom, and the Magpie settings plugin (0.2.3) serves the quartz,
marmot, mls, crypto, negentropy and schnorr256k1 groups exclusively. The
versions are marmot 2.3.0's own pins (D2), declared `strictly` so a transitive
request cannot move them (D3). gradle/magpie.lock pins the release key and the
manifest of every module resolved -- jvm, android and root so far; the iOS
lines need a mac (Phase 6).
No Kotlin file changed. The resolved graph moved by exactly the four libraries,
negentropy v1.2.3 and the new schnorr256k1-kotlin; secp256k1-kmp still resolves
to the composite. check green, jvmTest 1389/1389 with no test edited, release
minifies through R8.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The running card names the members whose share it takes away because
the group removed them as admin, and their rows read Share being
rotated away instead of Holds a share. Removing an admin says nobody
is asked again.
The plan is marked built, with where the build chose differently, and
the notes it changes point to it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Magpie, which the next phase brings in, refuses a daemon below 21. The criteria
file makes Gradle pick 21 itself (foojay downloads one where none is installed),
so a 17 launcher still gets a 21 daemon: checked with JAVA_HOME at 17, jvmTest
1389/1389. No dependency moves in this commit.
The file was gitignored since 8de05742, most likely to keep an IDE-generated copy
out of the tree; it is now the build's statement of its daemon JVM, so it is
tracked.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every target resolves from the release relay but mls-kmp 1.4.0, which is in
neither Magpie nor Central, so Phase 5b waits and mls stays at the 1.3.1 marmot
2.3.0 was built against. Baselines: 1389 jvm tests in 182 classes, check green.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
None of the four is on Maven Central any more: from quartz 2.19.0, mls 1.3.1,
marmot 2.3.0 and crypto 2.1.1 they are released on Nostr + Blossom through the
Magpie settings plugin. The code the app calls has barely moved; the way the
build reaches it has. Nine phases, marmot's own pins first and the newest second.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The rotation an admin change owes asks nobody, because the group's
signature on the change already decided who is withheld; admin changes
and rotations never overlap. Phase 0's twelve decisions, as recommended.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Since a keyed room can demote an admin and an admin can step down, a founder
missing from the policy is often the group's decision, and the card's repair
offers to undo it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings in a keyed room's step-down by request (bb35d73c) and keyed rooms
born needing the group's signature, with the switch gone (1ccd8c7f).
Resolved: AdminGovernance keeps giza's canAskToStepDown and
stepDownProposer beside the policy-backed memberActions; the
repositories keep memberActionOptions and lose requireSignatures; the
loader no longer asks GovernanceSupport whose devices a room waits on.
Reconciled: the policy offers your own row Step down as admin in a keyed
room on canAskToStepDown's terms -- governed, rotation on, above the
floor, another admin to ask -- so the menu matches the request giza
added. SignaturesNotRequired carries no data and says the group was made
before signed changes and keeps its admins, since nothing switches the
rule on any more.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
An admin's own row had no menu in a keyed room: stepping down was not
offered, because a demotion's proposer starts the rotation that takes
the demoted admin's share away, and a rotation's proposer has to keep a
share.
Step down as admin now sends a request into the room
(PromotionEvents.STEP_DOWN, 30377) and commits nothing. The remaining
admin in the lowest leaf (AdminGovernance.stepDownProposer) -- one
device, named the same everywhere, so two never propose at one epoch --
takes it up in GovernanceFollowThrough and runs the same demote its own
Remove as admin would. A request is used once, and dropped by every
device once its requester is no longer an admin. Offered only above the
floor and while another admin is there to ask.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The note's status, a table of the build's departures from the plan --
the route carries the action by name, an unavailable item's state rather
than a second click label, the only admin as one reason -- the README
entry, and a pointer from member-admin-promotion's Phase 11. The unused
"See why" string goes with the click label it was for.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The rule that a keyed room's changes need the group's signature was
switched on after founding, once every member's device had said it could
follow signed commits. That protected Bennu members and older Giza
builds from being left behind by the first signed change. Giza is in
development and keeps compatibility with neither, so the switch
protected nobody, and it kept an invited member from ever being made an
admin.
MarmotGroupCreation.createFor now writes GovernanceMarker's line, with
the floor the ceremony's quorum sets, into the room's epoch-0
description. Founding still needs no signature: the founding invite is
the creator's commit while it is the only member, which no other device
processes.
Removed: GovernanceSupport and its event (30372), the announcements on
joining, at start and in answer, the automatic switch and
requireSignatures, and the screen's waiting and ready states.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Requiring the group's signature for changes was a button an admin had
to find on the room's screen. Nothing about it was a decision: the two
conditions it waits on -- every member's device can follow, enough of
them are admins -- were already checked in code. The button is gone.
One device switches it on: the admin in the room's lowest leaf, which
in a room as made is its creator (GovernanceSupport.switcherOf). Not
every admin's, because two commits at one epoch are not settled for
their authors (docs/marmot-v2.md, Phase 8); every device reads the same
leaf, so they agree on one without talking. GovernanceFollowThrough
runs the switch whenever a member says it follows signed commits, and
on start.
Not at creation: a Bennu or older-Giza founder would be cut off without
anyone knowing, and a founding invite finished later is a bare commit a
governed room refuses. The room switches seconds after its founders
join instead. The screen names whose device it is waiting on.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
An invited member of a robust group could never be made an admin. Making
one needs the room to require the group's signature, which waits until
every member's device has said it follows signed commits. A device said
so when the room's screen was opened, or back when it heard another say
it -- but the founders said it before the invite, at an epoch the new
member cannot read, so it heard nothing, nobody said it again, and the
room waited on a screen the member had no reason to open.
A device now says it on joining (the Welcome path) and once each start
(GovernanceSupport.announceAll), for members who joined before this.
The waiting notice names who the room waits on and what for, instead of
"X need to update Giza".
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
remove-convenient-groups' new test makes its phones with Phone(profile);
since the legacy KeyPackage slot was retired every phone publishes the one
package the app does, so it is Phone().
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Two files this branch deleted were changed on giza:
- SelectChatRoomTypeViewModel: giza added a reconcileAdmins call to the
convenient path, which this branch removed. The robust path
(MarmotGroupCreation) and direct messages (MarmotOutboundDao) already
reconcile, so the deletion stands.
- ChatRoomType: giza added minimumAdmins(threshold) for the admin floor.
It moves to Quorum.minimumAdmins beside the other quorum rules (D6);
AdminGovernance and AdminChangesJvmTest call it there.
docs/member-admin-promotion.md now notes where the names it cites went.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>