feat(wallet): ship behind the rollout gates (Phase 10)
GroupWalletRollout holds the three gates, each with what lifts it. The flag is on, its condition met. Send-an-amount is off, so the form sends everything confirmed to one address and says so. A spend proposed from this device on mainnet may send at most 100,000 sats; test networks have no cap. The gates are on the composer and nothing else: a device behind them still accepts, shows and signs what another member proposes, through every check GroupSpend makes. The plan is marked built, with its table of where the build chose differently. Full JVM suite: 1474 tests, none failing; the Android target compiles; every M3 budget is met. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
0db1fe8fc8
commit
f83fe35a45
10 files changed
+108
-18
No files matched your search
@@ -848,4 +848,6 @@
|
||||
<string name="bump_the_fee">Bump the fee</string>
|
||||
<string name="sent_again">Sent again</string>
|
||||
<string name="couldn_t_bump_the_fee">Couldn't bump the fee: there isn't enough left over to pay it.</string>
|
||||
<string name="for_now_a_spend_sends_everything">For now, a spend sends everything the group has confirmed to one address, less the fee.</string>
|
||||
<string name="while_the_wallet_is_new_at_most_s_sats">While the wallet is new, a spend on mainnet can send at most %1$s sats.</string>
|
||||
</resources>
|
||||
Reference in new issue
Block a user