The member-wallet policy (30337) becomes the group's opt-in: no policy
means the group does not guard members' wallets (D8), so every new member
wallet's delay is one its group chose. A newer policy with ["closed"]
instead of a delay stops new wallets (D9); it never releases one already
guarded, whose addresses carry the group's leaf. Opening again is a newer
open policy.
The signer table, the picker's refusals (POLICY_UNKNOWN, NOT_OFFERED,
CLOSED), the request, the screen -- now MemberWalletPolicyScreen, with
Stop guarding new wallets -- and the emulator run follow. Phases 4, 5 and
6 now ship together, since 4 and 5 close every group until 6 opens it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The group's quorum signs a standing policy in its own room -- a new kind,
30337, ["guardian_delay", <blocks>] -- rather than a birth certificate
tag: the certificate is the parent's statement, frozen at birth, and a
root group has none. A member's request is built under the newest policy
and carries it whole, so late members (through the key notice) and
signers who missed it judge it alike; signers refuse a stale or missing
one. A wallet already guarded keeps its delay. Seven phases, not built.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings in member guarded wallets and funding a descendant's guarded wallet.
- Schema: bennu's v30 (MemberWallet, MemberWalletSpend) is kept as it is;
DkgSession.guardianDelay moves to v31, with a 30 -> 31 auto-migration.
- Conflicts: strings and README take both sides; the send form's guardian
delay line moves into the shared SpendForm; the guarded wallet card keeps
its Fund and Spend buttons and gains this group's own leaf's delay.
- bennu's uses of ANCESTOR_DELAY become each leaf's own delay:
GuardedWalletRow.arriving, the funding form's "spend these coins again"
line, the member wallet screens' reach text (MemberWalletManager.delaysOf)
and the member certificate's proposal summary.
- Four of bennu's fixtures built a "guarded" wallet with no guardian leaf;
they now carry the ancestor's, as a verified statement would.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Member guarded wallets are offered on mainnet; a member's own spend
there stays held to MAINNET_CAP.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
GroupWalletRollout.MEMBER_WALLETS_ON_MAINNET is on, lifted by decision
ahead of the signet run that was to lift it, as GUARDIANS_ON_MAINNET
was. A member's own spend on mainnet stays held to MAINNET_CAP, like
every group and guardian spend: memberCapFor no longer lifts with the
gate, since the run that would have justified lifting both has not
been made. The note says the gate is open, what it still leaves open,
and where the cap lifts.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A guarded wallet a group keeps for one member: the member's random key
on the key path, and the leaves a guarded subgroup of the group would
carry. docs/member-guarded-wallets.md.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings in a group funding a descendant's guarded wallet. Three conflicts:
- GroupSendScreen: funding replaced the address field and named the
funded wallet in the preview, inside the fields this branch moved
into SpendForm. SpendForm now takes a destination slot, which a
funding fills with its card, and the funded wallet's name; the
preview takes both that name and the member's ownWallet words.
- GroupWalletScreen: the guarded wallet row is funding's card with Fund
beside Spend, headed by this branch's #name / @name and carrying a
member's label.
- docs/README.md: both rows.
Funding reads guarded wallets through GuardianManager.guardedWalletsOf,
which this branch widened to members' wallets, so a group can now fund
a member's guarded wallet. Every place funding named a wallet with
`name ?: "a subgroup"` -- the title, the destination card, the preview,
the proposal summary, a signer's refusal -- uses displayName, so it
reads "Fund @alice's guarded wallet". A test funds a member's wallet
end to end through GroupSpend.fundingsOf.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The plan is marked built, with a table of the thirteen places the build
chose differently -- the key notice carrying the key rather than the
signed key state, the request travelling whole inside an inner event,
Put to the group living on the group's page, the wallet screen
following a member's spends while open, and the signet run still to
make before the mainnet gate lifts. The guardians and subgroups notes
point here, and the README says it has been built.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ChatRoomDetailScreen gets a Members' guarded wallets section of its own
under Subgroups: a row is a person, @name and the wallet's label, and
it opens their profile rather than a room. A request no signer has put
to the group yet says so, and a share-holder can put it to the group
from the row; a member who could ask has the way in beneath.
ProfilePreviewScreen lists the person's wallets the groups this profile
is in guard, one row per guarding group, with Spend where this device
holds a share -- the guardian spend the wallet screen already makes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A guarded wallet's subject is now a subgroup or a member.
GuardianManager.verify takes a member wallet certificate beside a
subgroup's statement, checks it on its own and walks the ancestor's
guardian root down a line of descent that ends in the wallet's id. The
group that signed a certificate lists it from its own signed events;
the groups above learn of it from a 30333 notice, and a member in both
rooms can carry it upward from the wallet screen as before.
The guardian spend is unchanged: the guarded tag carries W, the builder,
the check and the signing cache take any id. The wallet screen names a
subgroup's wallet #name and a member's @name -- the live profile name,
since the certificate fixes who the member is, not what they are called.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
MemberWalletManager.signSpend checks a spend the way a group member
checks a group's -- GroupSpend.check against the account the wallet
rederives to -- signs every input on the key path with the member's
key, asserts correctlySpends, and files it as a MemberWalletSpend.
While member wallets are shut on mainnet a member's own spend there is
held to the same cap as every group spend.
MemberSendScreen is the group's SpendForm with a button that signs and
sends; the line above it says there is no quorum after this. There is
no session for GroupTransactionWatcher to follow, so the wallet screen
follows the member's spends while it is open, sending again any
Electrum has not heard of, and lists them.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
guardian-delay.md is marked built, with a table of where the build chose
differently. group-wallet-guardians.md's "Why 12, and why for everybody"
becomes "Why a delay, and who sets it": each parent chooses its own leaf's
delay from 6 to 65,535 blocks, inherited ones keep theirs, and a long
delay is a backstop rather than an override. The policy note's picker
section and the README follow.
The three-emulator run is still to do by hand.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
proposeBirthCertificate grants the parent's own leaf the delay off the
child's ceremony, or the default for an older build's ceremony; every
inherited key keeps the delay its ancestor chose.
Every parent signer now takes the own leaf's delay from the proposal and
recomputes everything else -- keys, order, and each inherited key's delay,
which must be the group's own certificate's -- so a proposer cannot
shorten or lengthen an ancestor's wait. Every child signer refuses a
certificate whose own-leaf delay is not the one its ceremony announced at
the join gate. ProposedEvent says the delay in blocks and roughly in time.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
GroupSendScreen's fields and preview move, unchanged, into SpendForm,
which emits into the caller's column so the group's form lays out as it
did. The button stays the caller's: a group asks its quorum, a member
will sign alone. An ownWallet flag changes the words -- "your coins",
"this wallet" -- and nothing else, so the two forms cannot drift.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Under the guarded row, SelectSubgroupAdminsScreen offers the delay for
this group's own leaf: presets for an hour, two (the default), a day, a
week, a month, six months and the longest, and a custom field in blocks
whose supporting text says what it works out to, or why it cannot be
used. The view model keeps what was typed rather than clamping it,
refusal() refuses a delay outside 6..65,535 for a guarded subgroup, a
retry restores it, and confirm passes it to proposeRitual. The guarded
row and the join gate stop quoting 12.
Lands with Phase 6, which puts the chosen delay into the certificate.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The profile lists every guarded wallet of its own this device knows
about, named for the group that guards it: the ones whose key is here,
and the ones a group this device is in has certified for this npub,
which includes wallets made on another device and shown watch-only.
Each row says where the asking has got to -- asked, signing, not
signed, open -- or the balance.
MemberWalletScreen offers addresses only once a group has certified
the wallet. Before then the member can ask again or discard the key,
which is safe exactly then; after, it shows the balance, the address,
the coins and every coin a guardian took, read off the chain. Export
key, behind a confirmation, shows both descriptors with the private
key in them.
wipeData has no callers and deletes nothing yet, so there is no wipe to
guard; a note on it says what a caller must do once it does.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Each guarded wallet on an ancestor's wallet screen becomes an outlined card:
the name (now up to two lines) and what is within reach, then Fund and Spend
in a flow row under them rather than in the list item's trailing slot, each
naming its wallet to a screen reader. Fund is offered only where the room has
a wallet of its own and can sign and watch. The supporting line adds what is
arriving -- coins not yet past the leaf's lock -- so a funding does not look
lost for two hours. The send form's destination card names the wallet once,
under "To", instead of repeating the title.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Before a parent can choose a delay, the screens stop saying "12":
- the child's wallet screen, opened or not, lists each guardian nearest
first with its own delay -- "#Council: after 144 blocks, about 1 day" --
named by the room this device holds for it;
- an ancestor's Guarded wallets list says, per wallet, the delay that
wallet gives this group, and GuardedWalletRow.withinReach counts coins
past that delay rather than the default (GuardedWallet.delay);
- the send screen tells a guardian that only coins past its leaf's lock
can be spent;
- the subgroup rows and a subgroup's parent row say "Guarded wallet,
after <delay>", off the certificate.
The strings that quoted one number are reworded without it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
MemberWalletManager.request makes a random key, works out the group's
leaf and every inherited one, builds both descriptors, stores the key,
and only then puts the signed request into the group's room. It checks
the request the way every signer will before it goes, and a member who
holds a share of the group's key puts it to the group in the same step.
NewMemberWalletScreen is a consent screen first: who can take the
member's coins and after how long, who will see them, and that the
group is the recovery path -- then an optional label and one button.
Every refusal is named, and a member who does not know the group's key
can ask for it from there. Its entrances arrive with the profile's
guarded wallets (Phase 8) and the group's page (Phase 11).
GroupWalletRollout.MEMBER_WALLETS_ON_MAINNET is shut: the entrances are
offered on test networks only, since the member's own spend is the
first single-signer path the app has.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
proposeRitual takes a guardianDelay and puts it on the proposal as
["guardian_delay", "<blocks>"], beside ["wallet", "guarded"] and only
there; acceptProposal files it on DkgSession.guardianDelay. A delay that
does not read, falls outside 6..65,535, or comes with an unguarded policy
drops the proposal, and proposeRitual refuses the same before anything
goes out. A guarded proposal with no delay files none, and is certified at
the default later.
Schema 29 -> 30: the nullable DkgSession.guardianDelay, an auto-migration.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
text/BlockDuration.approximate: within 5% of exactly one hour, day, month
or year, that unit singular; otherwise the largest unit that comes to at
least 2, rounded -- 216 blocks is about 36 hours, 65,535 about 15 months.
delayText says it beside the block count, "144 blocks, about 1 day", and
the block count alone on regtest.
The catalogue's first plurals, so nothing reads "about 1 hours";
StringCatalogueJvmTest asserts they resolve. Nothing shows a delay yet.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
GroupSendRoute.fundChatRoomId opens the form in fund mode: the address field
gives way to a fixed destination card naming the wallet, the address
fundingAddress chose and its index, and that the group can spend the coins
again after the leaf's lock. The form follows the descendant's chain state and
the room's open fundings, so a paid or held address moves on while it is open.
A route naming both a source and a destination is not opened.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
For delays at each edge of the script number's encoding -- 6, 16, 17,
127, 128, 32767, 32768 and 65535 -- an ancestor quorum's script-path spend
passes correctlySpends at nSequence = delay and fails one block short.
GroupSpendBuilder offers a guardian a coin only once it is that deep and
puts that sequence on every input, and GroupSpend.check refuses the
default's lock on a leaf that chose another.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
GuardianDerivation gains MIN_DELAY (6), MAX_DELAY (65,535, BIP68's
block-based ceiling) and DELAY_RANGE; ANCESTOR_DELAY becomes DEFAULT_DELAY,
the 12 a parent is offered first. grant() takes the parent's own leaf's
delay and leaves every inherited key at the delay its ancestor chose.
leafScript and GuardianTag.parse refuse anything outside the range, so a
tag under the floor does not read. Every tag written before said 12.
Tests pin the leaf script byte for byte where the number push changes
length -- 6, 16, 17, 127, 128, 32767, 32768, 65535 -- and older(65535) in a
checksummed descriptor. Nothing chooses a delay yet.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
acceptProposal refuses a 30334 before it is shown unless it is exactly
the certificate the request it carries asks for, the person asking is a
member of the room, and its guardians are the ones this group grants --
SubgroupManager.grantFor with the wallet id in a child room's place.
MemberWalletManager.putToGroup is how a signer sponsors a request: one
session over the certificate the request determines, or the session
another sponsor already opened over the same event id. The signers read
the proposal as whose wallet and what the group can take from it, and
the transcript gets a line for the request and for the certificate
rather than raw JSON.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
GroupSpend.fundingsOf reads each payment's derivation against the guarded
wallets the room holds: a claim that derives is a funding, one that does not
refuses the spend, and one under an account this device does not hold is left
as the bare address. Every proposal and acceptance path and checkedSpend read
it, ProposedSpend says "Fund X's guarded wallet", open fundings hold their
addresses, and a bump keeps the claim.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
MemberWallet holds the random key of a guarded wallet one member holds
and a group guards, with the request that asked for it; MemberWalletSpend
the transactions the member signed alone. Whether a wallet is certified
is read off the group's signed events each time, so there is no column
for it. Neither table has a foreign key: deleting a group's room on this
device must never delete a key that coins may sit behind.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A parent sets only its own leaf's delay; an inherited ancestor keeps the
delay it chose, all the way down a guarded subtree.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
MemberWalletCertificateEvent (30334) is the group's signature over a
member's request, which it embeds whole so an ancestor never in the room
can check that the member asked. template(request) is the only way one
is built and verify() checks a certificate is exactly that template, so
a sponsor chooses nothing and two sponsors propose one event id.
Its own kind rather than a 30329: every reader of birth certificates
assumes a room, and a test fails the day subgroupsOf reads both.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
GroupSpendBuilder.send and sendAll take a Destination: a typed address, or a
Funding of a descendant's guarded wallet at the address fundingAddress chose.
The funding output carries its tap_bip32_derivation under the descendant's
account, the field change already uses, so it is never taken for change and a
signer holding that wallet can derive it again.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
MemberWalletRequestEvent (30335) is the first thing that leaves the
member's device: the wallet key, its id, every guardian leaf and both
descriptors, signed by the member's nostr key and -- over a tagged
possession message -- by the wallet key itself. verified() checks all
of it that can be checked without the group's key, down to the
descriptors byte for byte.
An inner event is an unsigned rumor, so the room carries the signed
request whole as an inner event's content, as a 30333 notice carries a
statement; carried() takes it out only from the member who signed it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
GroupWalletState.fundingAddress picks the lowest unused, unreserved receive
index from current + ADDRESSES_AHEAD up to the end of the watched window, and
GroupSpend.claimedFundingIndices reads what open fundings already hold.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A member welcomed after a group's founding holds no key state, so cannot
work out the leaves a guarded wallet of theirs would carry. They ask with
a 30336 GroupKeyNoticeEvent; any member holding the verified key state
answers with the threshold key, its path and the group's certificate.
The answer is believed only for what checks itself -- the key rederives
the room, the certificate certifies it and names that key -- and is read
where it is used, never filed as key state. It carries the key rather
than the signed key state because the key state's row keeps what it said
and not the event.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A parent picks its own leaf's delay when it makes a guarded subgroup, from
6 blocks to 65,535 (BIP68's block-based ceiling, about 15 months); an
inherited ancestor keeps the delay it chose. The delay rides the ceremony
proposal, is signed into the certificate's guardian tag and checked by
both quorums, and every screen that quotes "12" says each leaf's own
delay as blocks with an approximate duration. Eight phases, not built.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
MemberWalletDerivation holds the private side of a guarded wallet whose
key path is one member's random key: the wallet id W, the account step
added to the scalar, CKDpriv to each address, and a key-path signature
under the address's script-path tweak. The public side is the group
wallet's derivation unchanged; GroupWalletDerivation.accountStep is split
out so both add the same tweak.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The member's device makes a random key, works out every ancestor leaf
and both descriptors, and only then asks the group. The group's quorum
signs a member wallet certificate of its own kind (30334) rather than a
birth certificate, since every reader of 30329 assumes a room. Ancestors
list the wallet as @name, and the group's page opens the member's profile.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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>
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>
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>
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>
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>
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>
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>
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>