Ecosystem metrics
- Commits
- 476
- up 39.6%
- Releases
- 3
- up 200.0%
- Contributors
- 49
- up 40.0%
- Merges
- 9
- down 10.0%
Activity Overview
Commits and releases over time
- Commits
- Releases
- Authors
Repository Explorer
No repositories match that filter.
7563 commits in all time
Aug 24, 2026 23:37 – Nov 22, 2026 23:37 UTC
fix: address code review round 15 (short validity window, pinned "Check again", storage hardening)
- A management transaction signed in place is valid for about 50 rounds, so an unconfirmed send expires within minutes and the lock ends by itself; a group handed to Sign-all keeps the node's window. A node that does not know the transaction (404) no longer unlocks early: another node of a gateway may still hold it, only the validity window ends the lock. - "Check again" is pinned to the asset, action and storage key it started on, so finishing late cannot clear another page's lock. - A stored lock that is not an object is ignored; the clawback receiver is only prefilled on the clawback page; the changelog says created assets. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
38326b1f
feature/asset-management
3/57 ++ 22 --
fix: address code review round 14 (Sign-all review details, unknown transactions)
- The Sign-all page shows what a freeze, address change, destroy or clawback does (TxReviewDetails, as on /sign), and those rows start expanded, so a co-signer or Ledger user does not approve them without seeing the target. - A transaction the node does not know at all (never received, e.g. offline, or dropped) is reported and does not lock the page for the whole validity window; the "expired" message now covers it. - E2E: Sign-all shows the freeze, and an unknown transaction does not lock. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
4c970def
feature/asset-management
14/80 ++ 16 --
fix: address code review round 13 (freeze on /sign, restored-lock result, receiver prefill)
- A freeze shown to a co-signer on /sign no longer reports a malformed "pay to" address (afrz joins the types without a receiver); the freeze target is shown by the transaction review. E2E asserts it on the multisig round trip. - "Check again" shows the confirmed result also when the lock was restored after the page was left. - The clawback receiver is only prefilled when an asset is shown first. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
cda21a0f
feature/asset-management
3/13 ++ 3 --
fix: address code review round 12 (rejection reported once, gateway errors with a message, expiry message)
- A transaction the pool rejected after the user left the page is reported once, with the pool's reason, and no longer also as a green "sent" toast. - A gateway error (5xx) counts as "maybe sent" even when it carries a JSON message; 4xx answers such as 429 mean the node did not take it. - "Check again" says so when the transaction expired without confirming and it is safe to retry. - E2E: expiry unlocks the page with that message. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
21654f24
feature/asset-management
13/66 ++ 14 --
fix: address code review round 11 (lock for a page that was left, gateway errors, pool rejection)
- A send that is not confirmed after the user left the asset or action still records its lock for the asset and action that were sent. - A 408, 429 or 5xx answer to the broadcast counts as "maybe sent" like a missing answer (a gateway can answer after the node queued the transaction); no error toast is shown for it, the page says "sent, not confirmed". - A transaction the pool rejected after submission is detected through the node's pool error: the reason is shown and the page is not locked, and "Check again" unlocks as soon as the pool error is set. - A malformed stored lock is dropped instead of half applied. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
b7f2f090
feature/asset-management
3/113 ++ 25 --
fix: address code review round 10 (persistent send lock, definite HTTP failures, form and hub state)
- The lock after an unconfirmed send is kept per network, asset and action in sessionStorage, so leaving the page, opening another asset or remounting no longer lets the same action be sent twice; it is cleared when the transaction confirmed or its validity window is over. - Only a broadcast with no HTTP answer at all (timeout, dropped connection) counts as "maybe sent"; an HTTP answer without a message (gateway page, 401/403) is a definite rejection and does not lock the page. - The address form (and its confirmation) is only reset when the chain's addresses changed, not by every refresh. - The hub's "destroyed" filter follows the route and reloads the list. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
9ac5a29e
feature/asset-management
4/75 ++ 8 --
fix: address code review round 9 (real unlock condition, uncertain sends, genesis/lease/group checks)
- "Check again" only unlocks once the transaction confirmed or its validity window is over (last round > lastValid); a pending transaction, or a node that cannot be asked, keeps the actions locked. - A broadcast that gets no answer from the node (timeout, dropped connection) is treated as "sent, uncertain": signAndSend (opt-in reportSendErrors) returns the transaction id, so the page waits for it and locks instead of unlocking. - busy is tied to the latest send/check, so an older call that finishes late cannot unlock a page that moved on. - A failing signer lookup shows "no signer" instead of a blank page. - The final safety check also verifies the network's genesis hash and id and that the transaction has no group id or lease. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
5581a9ba
feature/asset-management
15/140 ++ 3 --
fix: address code review round 8 (lock after an unconfirmed send, disabled action links, wallet-account guard)
- After a send that is not confirmed the actions stay locked until the user
checks again ("Check again"), so the same clawback/freeze cannot be sent a
second time while the first may still confirm.
- A disabled action is a plain disabled button, not a focusable link.
- execute() only signs for a role address that is a wallet account.
- A failing signer lookup no longer breaks the asset manager list.
- E2E: unconfirmed send locks the form and Check again unlocks it.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
8a90fa26
feature/asset-management
13/160 ++ 18 --
fix: address code review round 7 (form flicker, unconfirmed double send)
- A refresh of the account data no longer hides the action form while the signing route is resolved again; it is only cleared for another role address. - An unconfirmed send waits up to 10 more rounds before the form is offered again, so the same action is not sent twice while the first may still confirm. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
7bd6afe9
feature/asset-management
1/15 ++ 3 --
fix: address code review round 6 (overlapping hub loads, stale route, toast level, dead code)
- The asset manager hub drops the result of a superseded load, so a wallet that opens while a load runs cannot be overwritten by an older, partial list, and the spinner follows the latest load. - The signing route is cleared before it is resolved for another role address, so the previous action's route is never shown for the new one. - A result that arrives after the user left the page is a plain toast, never an error for a transaction that may still confirm. - Removed the unused rolesHeldBy helper; created-asset paging allows 200 pages. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
d9806e8b
feature/asset-management
5/16 ++ 24 --
fix: address code review round 5 (result tied to its page, unconfirmed is a warning, signer-based hub roles)
- A transaction that finishes after the user opened another asset or action no longer writes its result or refresh into that page (toast only); a fresh page is never left busy by an older call. - An unconfirmed send is shown as a warning, not a green success. - The signing route is resolved again when accounts change (wallet opened, rekey) and after the post-send refresh. - The asset manager decides which roles the wallet holds with the same signing-route decision as the manage page, and reloads when the account list changes. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
678834aa
feature/asset-management
2/68 ++ 13 --
fix: address code review round 4 (confirmation per cleared set, unconfirmed sends, destroy redirect)
- The "cleared addresses can never be set again" confirmation is reset when the set of cleared roles changes, so one tick cannot also cover clearing the manager later. - A failed refresh after a sent transaction keeps the page and its result and reports the error as a toast; a successful load clears an old load error. - A transaction that is not confirmed is only reported as sent: no re-read of the state and no redirect after a destroy. - After a destroy the hub is told the asset id and leaves it out, since the indexer lags the node. - The hub's role column no longer counts WalletConnect accounts. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
d9510622
feature/asset-management
3/65 ++ 10 --
fix: address code review round 3 (stale asset, form state, one result signal, translated safety errors, hub)
- Drop an asset answer for an asset the user already left and reset the per-asset form and holdings when the route's asset changes. - Keep what was typed in the address form when switching action tabs; it only follows the chain when the asset is (re)loaded. - One result signal after a send: the inline message says confirmed or sent (a toast only when the page is left after a destroy); no spinner flash on the post-send refresh. - signAndSend toasts a message-less broadcast failure only when asked (reportSendErrors), so bulk payment tools stay as quiet as before. - The final safety check throws typed problems that the page shows translated (asset_manage.unsafe_*) instead of English sentences. - Asset manager: accounts are asked 4 at a time and the warning names the accounts that could not be listed. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
c97f2698
feature/asset-management
16/251 ++ 103 --