Commit Graph
926 Commits
Author SHA1 Message Date
Kgothatso Ngako 8cb6f04efb Merge branch 'claude/parent-group-wallet-control-5a1540' into bennu 2026-10-24 06:13:36 +02:00
Kgothatso Ngako 60cb3fa7ae Merge remote-tracking branch 'origin/bennu' into claude/parent-group-wallet-control-5a1540
# Conflicts:
#	composeApp/src/commonMain/kotlin/com/machankura/bennu/compose/database/repository/DatabaseChatRepository.kt
#	composeApp/src/commonMain/kotlin/com/machankura/bennu/compose/repository/ChatRepository.kt
#	composeApp/src/commonMain/kotlin/com/machankura/bennu/compose/ui/view/model/ChatRoomDetailViewModel.kt
#	composeApp/src/commonMain/kotlin/com/machankura/bennu/compose/ui/view/state/ChatRoomDetailUIState.kt
#	composeApp/src/commonTest/kotlin/com/machankura/bennu/compose/text/ProposedEventTest.kt
2026-10-24 06:13:32 +02:00
Kgothatso NgakoandClaude Opus 5.5 e9fae262c8 docs: the subgroup wallet policy is built, and the notes it touched say so (Phase 9)
subgroup-wallet-policy.md is marked built, with a table of where the
build chose differently. group-wallet-guardians.md's "why it is still the
child's choice" becomes "whose choice it is": the parent decides, the
chain still does not enforce it, and an older certificate still leaves it
to the child. subgroups.md gains the wallet tag and the policy as the
second value the coordinator picks for other people.

The three-emulator run is still to do by hand.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 22:11:00 +02:00
Kgothatso NgakoandClaude Opus 5.5 6bd47210f9 feat(subgroup): the detail screens show what a parent decided about a wallet (Phase 8)
SubgroupManager.Subgroup.walletPolicy reads it off the certificate, and
each row of a parent's subgroup list says guarded or unguarded wallet
under its supporting line. A subgroup's own parent row says the same,
off ChatRoomDetailUIState.walletPolicy. Founding history, shown as such;
an undecided certificate says nothing.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 22:10:14 +02:00
Kgothatso NgakoandClaude Opus 5.5 1069059174 feat(wallet): every member refuses and ignores a wallet its parent ruled out (Phase 7)
Signing: FrostSigningManager refuses a wallet statement proposal whose
guardedness the room's own certificate does not allow, before it is
shown, reading the policy off this device's key state.

Reading: GroupWallet.newestAmong takes the policy and drops a statement
it does not allow before rule 1 -- under a guarded policy a plain
statement is no wallet even alone, so an older client's plain wallet has
no addresses derived, no coins watched and no spends signed. walletFor
passes GroupWalletManager.walletPolicyFor. An undecided room reads
exactly as before. GuardianManager.verify refuses a forwarded statement
whose certificate's policy contradicts its keys or decided unguarded.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 22:08:48 +02:00
Kgothatso NgakoandClaude Opus 5.5 47df6f51f7 feat(wallet): a subgroup's wallet screen offers only what its parent decided (Phase 6)
GroupWalletViewModel reads the room's own wallet policy through
ChatRepository.walletPolicyOf: a parent that decided guarded leaves the
guarded wallet alone, one that decided unguarded the plain one alone, and
an undecided subgroup or a root group keep what they had. openWallet will
not build a plain statement under a guarded policy, and OpenWalletAction
shows one button with a line saying the decision was the parent's.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 22:04:43 +02:00
Kgothatso NgakoandClaude Opus 5.5 52ca030c8b feat(subgroup): the child's quorum holds its certificate to the policy it joined under (Phase 5)
SubgroupManager.refuseKeyState: a child signer refuses a key state whose
birth certificate decides a wallet policy other than the one its own
ceremony announced at the join gate -- undecided included. A ceremony
from an older build announced none and holds the certificate to nothing.
proposeSubgroupKeyState refuses the same thing before asking.

GroupKeyStateManager.parentageOf drops a state whose certificate's policy
does not read or contradicts its guardian keys, so a corrupt policy never
reads as undecided.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 22:02:49 +02:00
Kgothatso NgakoandClaude Opus 5.5 44a15e9bc2 feat(subgroup): the certificate carries the wallet policy, and every parent signer checks it (Phase 4)
proposeBirthCertificate reads the policy off the child's ceremony: guarded
carries the grant and `guarded`, unguarded carries no keys and
`unguarded`, and an older ceremony with none is certified as it always
was -- or as guarded under a guarded parent. An unguarded ceremony under
a guarded parent is refused with the remedy, start again.

refuseGrant becomes refuseCertificate. Every parent signer refuses a
certificate whose policy does not read or contradicts its keys, and a
guarded group's signers refuse anything but a guarded one, undecided
included -- D4, read off the signer's own key state. ProposedEvent says the
decision in both directions.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 22:00:59 +02:00
Kgothatso NgakoandClaude Opus 5.5 6599b5b116 feat(subgroup): the picker chooses the subgroup's wallet policy, and the join gate says it (Phase 3)
SelectSubgroupAdminsScreen gains a wallet section under the quorum
stepper: guarded (the default) or unguarded, carried to proposeRitual.
Under a guarded parent the unguarded row is shown disabled with its
reason, setWalletPolicy will not move off guarded, a retry is pulled back
to guarded, and refusal() refuses it -- D4. A parent whose guardian keys
do not read cannot make a guarded subgroup, which is now refused before a
ceremony rather than after.

SubgroupManager.walletPolicyOf is the one reader of a group's own policy,
reached through ChatRepository with guardiansOf. DkgJoinApprovalScreen
tells an admin what the subgroup's wallet will be before they join.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 21:58:10 +02:00
Kgothatso NgakoandClaude Opus 5.5 58751692c6 feat(dkg): a subgroup's ceremony carries the wallet policy its coordinator chose (Phase 2)
proposeRitual takes a walletPolicy and puts it on the proposal as a
["wallet", ...] tag, beside the parent and subject; acceptProposal files it
on DkgSession.walletPolicy. A proposal whose policy does not read, or that
carries one with no parent, is dropped, and proposeRitual refuses a policy
on a ceremony with no parent before anything else.

Schema 28 -> 29: the nullable DkgSession.walletPolicy, an auto-migration
like the other nullable additions.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 21:53:41 +02:00
Kgothatso NgakoandClaude Opus 5.5 f19001cd61 feat(subgroup): a birth certificate can carry its child's wallet policy (Phase 1)
SubgroupWalletPolicy and WalletPolicyTag, ["wallet", "guarded"|"unguarded"],
and SubgroupBirthCertificateEvent.parseWalletPolicy. A certificate with no
tag reads Undecided; one whose tag does not read, or contradicts the
guardian keys beside it, reads null rather than undecided. certifies is
unchanged. Nothing writes the tag yet.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 21:50:57 +02:00
Kgothatso Ngako f57ac781ca Merge branch 'claude/hierarchy-wallet-guarding-bug-75ab6e' into bennu 2026-10-23 21:49:00 +02:00
Kgothatso NgakoandClaude Opus 5.5 fed7e67c3d docs: plan the parent deciding a subgroup's wallet policy at birth
The coordinator picks guarded or unguarded on the subgroup picker, the
parent's quorum signs the choice into the birth certificate, and the
child's admins agree to it by joining and again when they sign the key
state. Every honest client then offers, signs, derives and watches only
the wallet the certificate allows. An unguarded certificate carries no
guardian keys, and a guarded group can only make guarded subgroups.

Not built: Phase 0's decisions and nine phases.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 21:48:32 +02:00
Kgothatso NgakoandClaude Opus 5.5 67fe01dd5b fix(groups): a grandchild's wallet reaches every guardian in one share
Sharing a guarded statement wrote one notice per guardian room, each hashed
from the same sharer, second, kind, tags and content -- so every notice had
the same id, and the last room's upsert took the row. A grandchild told its
parent and grandparent at once reached only the grandparent.

Each notice now names its room in an `h` tag, which gives it an id of its own.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 20:51:38 +02:00
Kgothatso NgakoandClaude Opus 5.5 b8c01946fd test(groups): the wallet row is named for its room
The onchain-wallet naming change gives the row its room's name, so the row
test written for the removal of the nostr profile, relays and posts looks
for "Translation room onchain wallet" rather than "Group onchain wallet".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 18:31:36 +02:00
Kgothatso Ngako da0841fd5e Merge branch 'claude/remove-nostr-relays-posts-fc5580' into bennu 2026-10-23 18:28:30 +02:00
Kgothatso Ngako 79f2ec3d4d Merge branch 'bennu' into claude/remove-nostr-relays-posts-fc5580
# Conflicts:
#	composeApp/src/commonMain/kotlin/com/machankura/bennu/compose/database/model/ChatMessage.kt
#	composeApp/src/commonMain/kotlin/com/machankura/bennu/compose/database/repository/DatabaseChatRepository.kt
#	composeApp/src/commonMain/kotlin/com/machankura/bennu/compose/nostr/wallet/GroupWallet.kt
#	composeApp/src/commonMain/kotlin/com/machankura/bennu/compose/repository/ChatRepository.kt
2026-10-23 18:28:25 +02:00
Kgothatso Ngako ea48c96933 Merge branch 'claude/group-onchain-wallet-naming-144edc' into bennu 2026-10-23 18:27:11 +02:00
Kgothatso NgakoandClaude Opus 5.5 7093adc0ee feat(wallet): a group's onchain wallet is named for its group
The wallet screen's title and the row on the group's detail screen read
"<group name> onchain wallet" instead of "Group onchain wallet". A room
with no subject, and the wallet screen before its room has loaded, keep
the generic name.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 18:26:44 +02:00
Kgothatso NgakoandClaude Opus 5.5 b400280486 Merge branch 'claude/dm-envelope-30330' into bennu
A direct message's envelope is opened, not taken for a signing decline:
both are kind 30330, and recognising protocol kinds first had dropped every
direct message in a current-profile room.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 18:19:20 +02:00
Kgothatso NgakoandClaude Opus 5.5 0449293963 fix(marmot): a direct message's envelope is opened, not taken for a signing decline
FrostSigningEvents.DECLINE and MarmotDirectMessage.ENVELOPE_KIND are both
30330. Recognising protocol kinds first (ceremony-creation Phase 6) returned
before the direct-message branch, so every direct message in a
current-profile room was dropped unopened. A 30330 that holds a gift wrap is
an envelope; only one that does not is a decline.

ProtocolKindDispatchJvmTest now opens an envelope through
fromGroupEventResult, which no test did before.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 18:13:02 +02:00
Kgothatso Ngako 79470dab1a Merge branch 'claude/taproot-group-hierarchy-spending-7a37ac' into bennu 2026-10-23 18:07:20 +02:00
Kgothatso NgakoandClaude Opus 5.5 7746f3d17f feat(wallet): offer guarded wallets on mainnet
GroupWalletRollout.GUARDIANS_ON_MAINNET is on, lifted by decision ahead of
the signet run its condition named. The mixed-version risk stays open and
is said so in the gate and the guardians note; guardian spends on mainnet
are held to MAINNET_CAP like every other spend.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 18:06:19 +02:00
Kgothatso Ngako 172709c131 Merge branch 'claude/bob-parent-group-button-bug-6c1d7e' into bennu 2026-10-23 18:00:04 +02:00
Kgothatso NgakoandClaude Opus 5.5 af4304aaae fix(dkg): a parent's second subgroup is not shown its first one's signing sessions
A subgroup's ceremony runs in its parent's room, so that room holds a
certificate and a key-state signing session for every subgroup made under
it. The ceremony screen took the newest of each kind regardless of which
subgroup it was for, so a parent's second subgroup opened on the first
one's finished certificate, with "Ask the parent group to certify"
already disabled.

Each session is now matched on what its event names: the certificate on
the subgroup's threshold key, the key state on the ceremony. The newest
match still wins, so a failed request can be asked for again.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 17:59:34 +02:00
Kgothatso NgakoandClaude Opus 5.5 b21f4c4d2c refactor(groups): remove the group's nostr profile, relays and posts
The group's detail screen loses its "Nostr profile", "Relays" and "Posts"
rows, and the six screens behind them go with them: the profile, its
editor, the relay lists, their editor, the posts and the composer. So do
the readers they stood on (GroupNostrProfile, GroupRelayList, GroupPost),
their ChatRepository methods, and 97 strings.

Two things go that were not named, because nothing else reaches them.
BroadcastGroupSignedEventScreen was only opened from those three screens,
so the app no longer sends a group-signed event to a relay, and
EventPublishTransport goes with it. "Propose event" accepted only a
profile, a post or a relay list, so it would refuse every paste;
ProposeGroupEventScreen and GroupEventProposal are removed, and with them
the detail screen's canEditNostrProfile gate. What is left of that block
is the wallet row, shown in Marmot rooms only.

The transcript keeps what it already holds. The three message types stay
as private legacy names in GROUP_IDENTITY_TYPES, as the curated-lists
types did, so rows already written stay system lines. A profile or relay
list arriving in a room now applies to nothing, so a signing session an
older build opened for one ends without a raw-JSON bubble. A kind:1 falls
through to "unsupported", which is what it was before posts existed.
ProposedEvent no longer describes the three kinds.

GroupSignedWorkRowsJvmTest now covers the wallet row and the absence of
the removed rows. The chronicle tests still use a profile, a relay list
and a post as their kinds; they compare GroupSignedEvent rows, which are
unchanged, so only ChronicleTestKinds' account of why is corrected.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 17:56:58 +02:00
Kgothatso Ngako dba3df697b Merge branch 'claude/taproot-group-hierarchy-spending-7a37ac' into bennu 2026-10-23 17:48:29 +02:00
Kgothatso Ngako 61c6f0b68e Merge remote-tracking branch 'origin/bennu' into claude/taproot-group-hierarchy-spending-7a37ac
# Conflicts:
#	composeApp/schemas/com.machankura.bennu.compose.database.BennuDatabase/27.json
#	composeApp/src/commonMain/kotlin/com/machankura/bennu/compose/database/BennuDatabase.kt
#	composeApp/src/commonMain/kotlin/com/machankura/bennu/compose/database/model/ChatMessage.kt
2026-10-23 17:41:56 +02:00
Kgothatso NgakoandClaude Opus 5.5 d878c9b992 Merge branch 'claude/ceremony-creation' into bennu
One place to start a key ceremony, and the removal of the nip30303
documents. See docs/ceremony-creation.md.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 17:33:03 +02:00
Kgothatso NgakoandClaude Opus 5.5 4023e9c08b fix(dkg): the creation screen's title before it knows the room's name (Phase 9)
Found on the emulators: refusing a Marmot room left the app bar reading
"Shared key for " and nothing. It reads "Shared key" until the room is
loaded. The plan now records what was checked on the three emulators that
found the bug, and what was not.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 17:12:37 +02:00
Kgothatso NgakoandClaude Opus 5.5 378bb8c800 docs: the ceremony-creation plan is built, and the notes it touched say so (Phase 9)
shared-key-ceremony.md says where a ceremony starts and how one ends early;
subgroups.md points its Phase 10 here; member-chronicle.md says the chronicle
is built and carries nothing; the batch-signing, skipped-keys and Material
notes mark their document examples as removed; the plan records the ten
places the build chose differently.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 17:05:03 +02:00
Kgothatso NgakoandClaude Opus 5.5 2d57f9b4c9 refactor(db): drop the nip30303 document tables (Phase 8)
Schema 26 -> 27. MIGRATION_26_27 deletes the chat lines the removed document
arms wrote and the unsupported bubbles a subgroup's ceremony left in its
parent's chat -- found by the kind of the inner event behind them, so an
unknown payload's bubble stays -- then drops the twelve document tables,
children before parents, and MarmotInnerEvent.payloadEventId. Manual,
because it deletes rows. GroupSignedEvent keeps whatever the group signed,
and the chronicle keeps its column and its lines.

The nip30303 events and tags, the Mantra entities and DAOs, the repository
interface and the Markdown helper go with the tables, and so do the tests
that only exercised them. The key-state test signs posts where it signed
dialects. The migration test builds v26 from the exported schema and checks
the result against v27's.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 17:04:00 +02:00
Kgothatso NgakoandClaude Opus 5.5 76f1df4e58 refactor: stop handling nip30303 documents, and keep the member chronicle quiet (Phase 7, part 2)
The inbound path no longer opens document submissions or applies document
kinds, and ProposedEvent no longer describes them. Nothing could send one:
the screens that did were removed in part 1.

The member chronicle carried nothing but document kinds. It is kept, and
what it may carry is now a ChronicleKinds value -- empty in the app, so a
device asks for no chronicle, sends none, and applies nothing from a page an
older build sends. The row-rebuild fallback and translation supersession go
with the documents. The chronicle's tests exercise the machinery with a kind
set of their own; the round trip through document rows is deleted with the
rows, as are the document-only apply test and the tests of translation
supersession.

Tests that used a dialect as an arbitrary signed payload now use a post.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 16:59:03 +02:00
Kgothatso NgakoandClaude Opus 5.5 68a86b4d77 refactor: remove the unreachable nip30303 document screens (Phase 7, part 1)
Nothing navigated to the artifact, chapter, dialect or translation screens:
ArtifactDetailRoute, AddArtifactRoute and AddDialectRoute were never built,
and the other six were only reached from inside those screens. Removed with
their view models, UI states, routes, nav host entries, the repository behind
them, TranslationScaffold, DetailRow, and the 65 strings only they used. The
group details screen loses the document repository it stored and never read.

The string catalogue test now checks its escapes on a string that stays.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 16:42:15 +02:00
Kgothatso NgakoandClaude Opus 5.5 02afa1eaec fix(marmot): ceremony and signing messages are recognised before anything sharing their kind (Phase 6)
A subgroup's ceremony runs in its parent's Marmot room, where its kinds
30310-30312 are also nip30303 document kinds. Round 1 (30312) was read as a
document submission first, failed to parse, and reached every other admin's
chat as an unsupported bubble of raw hex; the proposal and host keys reached
the translation arms before the ceremony's own. fromGroupEventResult now
stores a protocol message and returns before any document handling, and
applyInnerEvent checks the protocol arms first.

The comments that called the overlap safe are corrected, and the
"No app logic to handle" line every application message logged at info is
now a debug line that does not read like a failure.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 16:40:12 +02:00
Kgothatso NgakoandClaude Opus 5.5 726adfc02c feat(dkg): a participant can abandon a key ceremony, and only a participant (Phase 5)
There was no way to end a ceremony: ChillDKG has no "no" short of it, and
the approval screens pointed at an abandon action on the ritual screen that
did not exist. ChillDkgRitualManager.abandon now ends a running ceremony this
device is in, filing and broadcasting the same FAILURE a fault sends, and the
ceremony screen offers it behind a confirmation.

record() now ignores a FAILURE from anyone outside the ceremony. In a
parent's room every member can read a subgroup's proposal, so any of them
could otherwise end it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 16:35:56 +02:00
Kgothatso NgakoandClaude Opus 5.5 66887767b8 feat(dkg): the ceremony screen shows a ceremony and never starts one (Phase 4)
DkgRitualRoute and the three approval routes now require the ceremony's id,
and the screen loses its start button, its quorum stepper and its fallback to
the room's newest ceremony. A transcript line naming no ceremony opens
nothing. The title is the ceremony's name rather than the room's, so a
subgroup's ceremony is not called after its parent.

Try again on a failed ceremony goes back to the screen that starts that kind:
the creation screen for a group's own key, or the subgroup picker filled in
from the ceremony that failed. Retrying a failed subgroup used to open a
whole-room ceremony in the parent's room.

A test counts the screens that open a ceremony, so a fourth is a decision.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 16:34:02 +02:00
Kgothatso NgakoandClaude Opus 5.5 cc01f4aab9 feat(dkg): one screen that starts a group's own key ceremony (Phase 3)
CreateSharedKeyScreen takes the quorum and a single button, and nothing
else. It refuses a Marmot room and a group of one with a reason, hands over
to a ceremony the group already has rather than offering a second, and
replaces itself with the ceremony once it is opened so back never returns to
an offer. The group details' Shared key button and the card shown when a
robust group was created without its ceremony both lead here.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 16:27:15 +02:00
Kgothatso NgakoandClaude Opus 5.5 69095ba4a8 fix(dkg): the ceremony screen keeps hold of its ceremony (Phase 2)
Three ways the shared-key screen could lose the ceremony it was showing, and
so offer to start one:

- initiate() ran again whenever the screen came back into view, resetting
  the state to no ceremony and stacking another set of watchers. It now runs
  once per view model.
- five coroutines each read the state, changed one field and wrote it back,
  one of them across a suspending query, so an old copy could overwrite a
  newer one. The state is now built by one flow and written in one place.
- an approval closed its screen as the button was pressed, cancelling the
  view model's scope and with it a publish still in flight. The screen now
  closes once the approval has gone out.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 16:22:46 +02:00
Kgothatso NgakoandClaude Opus 5.5 e259634513 fix(dkg): a Marmot room hosts its subgroups' ceremonies and never one of its own (Phase 1)
proposeRitual now refuses a ceremony with no parent in a Marmot room, and
acceptProposal drops one arriving there. A Marmot room's id is derived from
the key it already has, so a key of its own is one it could never use -- and
the shared-key screen offering to start one in a parent's room is how a
second, whole-room ceremony opened beside a subgroup's.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 16:19:28 +02:00
Kgothatso NgakoandClaude Opus 5.5 30e425f201 docs: plan one place to start a key ceremony, and the removal of the nip30303 documents
Joining a subgroup's ceremony could open a second, whole-room ceremony in the
parent's Marmot room: the shared-key screen showed a ceremony, asked for
approvals and offered to start one from the same button slot. The plan
separates starting from showing, guards proposeRitual, and removes the
unreachable nip30303 document code whose kinds collide with the ceremony's,
keeping the member chronicle as an empty, quiet shell.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 16:17:55 +02:00
Kgothatso NgakoandClaude Opus 5.5 29328b4c5f fix(wallet): settle a spend whose coins another room's transaction took
A guarded wallet's coins have a spender outside the room: a guardian can
take a coin the child's open spend wants, and the child can move one a
guardian's wants. Neither winner is a row in the loser's room, so the loser
sat signed and rebroadcast forever. The watcher now asks the chain, for a
signed spend Electrum has not heard of, which transaction took each coin;
once that one confirms, recordReplaced marks the spend replaced and settles
every other spend of the coin, as recordConfirmed does for the room's own.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 16:12:48 +02:00
Kgothatso NgakoandClaude Opus 5.5 f9e2d45ec4 docs(wallet): guardian leaves built, and where the build differed (Phase 9)
The guardians note records what was built against the plan, what is left to
do by hand before the mainnet gate lifts, and the conflicting-spend gap. The
subgroups and wallet notes each change the one sentence the plan said they
would.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 15:40:43 +02:00
Kgothatso NgakoandClaude Opus 5.5 2b44ebcbbc feat(wallet): a subgroup's transcript names the guardian that spent from it (Phase 8)
Whenever a guarded wallet's coins change, the wallet screen reads every used
address's history off Electrum, recognises a guardian's leaf in the witness
that spent a coin, and writes one transcript line per transaction saying
which group above took how much -- the child's only notice, since nobody in
its room signed it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 15:40:43 +02:00
Kgothatso NgakoandClaude Opus 5.5 00df58c1f3 feat(wallet): an ancestor's quorum spends a descendant's coins through its leaf (Phase 7)
GroupSpend checks a spend as a guardian would sign it: every input under
the descendant's account, locked by the leaf's 12 blocks, signed over the
script-path sighash as the key the ancestor's walk reaches, and witnessed
with the leaf and its control block. The builder waits out the lock and
weighs the leaf; the signing manager proposes, accepts, signs and completes
it, and every signer reads the descendant's wallet from its own copy of the
statement. A guarded wallet row on the ancestor's wallet screen opens the
send form for it. Schema v27 adds GroupTransaction.guardedChatRoomId.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 15:37:21 +02:00
Kgothatso NgakoandClaude Opus 5.5 634f51f915 fix(wallet): read a PSBT's key fingerprint as unsigned
bitcoin-kmp reads a taproot derivation's fingerprint back from a serialised
PSBT as a signed int, so for any account whose fingerprint has its top bit
set -- half of them -- every member but the proposer refused every spend as
not the wallet's own. Compare the fingerprint as an unsigned 32-bit value.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 15:34:30 +02:00
Kgothatso NgakoandClaude Opus 5.5 e7a1ad260f feat(wallet): a guarded wallet is told to the groups above, and they watch it (Phase 6)
A member in both rooms carries a descendant's signed guarded statement into
an ancestor's MLS room as a 30333 notice, and can pass one on a generation
further. Every ancestor device believes it only when its own guardian root
reaches the key the statement names for it. The wallet screen lists the
guarded wallets below the group with what is within its reach, and the
statements this device can still carry up.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 15:26:19 +02:00
Kgothatso NgakoandClaude Opus 5.5 cbe5330cac feat(wallet): a subgroup opens a guarded wallet, and spends from it as before (Phase 5)
A room whose certificate grants guardian keys is offered a guarded wallet,
with a plain one beside it, on test networks; mainnet waits behind
GroupWalletRollout.GUARDIANS_ON_MAINNET. A spend's account is the one the
statement opened, so its own spends sign the guarded addresses' key path,
and wallets are watched per descriptor rather than per xpub.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 15:17:24 +02:00
Kgothatso NgakoandClaude Opus 5.5 606b4bb12f feat(wallet): a guarded wallet statement, and the account it opens (Phase 4)
An account knows its guardians and puts a leaf per guardian in every
address, internal key unchanged. The statement names them and carries the
certificate that granted them, and verifies only when the certificate
certifies this room and grants exactly those keys. A guarded statement
outranks a plain one for its account, and its first guardians stand.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 15:15:37 +02:00
Kgothatso NgakoandClaude Opus 5.5 e32419f0d8 feat(subgroup): a birth certificate carries the parent's guardian keys (Phase 3)
The parent grants the child its own guardian key and every key its own
certificate carries, one step further each, as guardian tags. Every parent
signer recomputes the grant and drops a certificate proposal carrying any
other keys before it is shown; one carrying none still signs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 15:10:30 +02:00