Ecosystem metrics

New Repos
25
New
Commits
471
up 37.3%
Releases
3
up 200.0%
Contributors
49
up 36.1%
Merges
9
down 10.0%

Repository Explorer

7558 commits in all time Aug 24, 2026 22:38 – Nov 22, 2026 22:38 UTC
scholtz wallet
Merge 21654f248a6d26c893ac6570070297846cfeee87 into bca7c6be32befff7b143c3505833b050118ec47a
Git Commit 25ef0342 Branch pull/228/merge Document 27/4,639 ++ 80 --
scholtz-aures wallet
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>
Git Commit 21654f24 Branch feature/asset-management Document 13/66 ++ 14 --
scholtz wallet
Merge b7f2f09007de5069b01127b253ce6f4eae74542a into bca7c6be32befff7b143c3505833b050118ec47a
Git Commit 861f027d Branch pull/228/merge Document 27/4,587 ++ 80 --
scholtz-aures wallet
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>
Git Commit b7f2f090 Branch feature/asset-management Document 3/113 ++ 25 --
scholtz-aures wallet
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>
Git Commit 9ac5a29e Branch feature/asset-management Document 4/75 ++ 8 --
scholtz wallet
Merge 5581a9ba710aa47a36b88c686586001bcf291551 into bca7c6be32befff7b143c3505833b050118ec47a
Git Commit e13c03b2 Branch pull/228/merge Document 27/4,432 ++ 80 --
scholtz-aures wallet
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>
Git Commit 5581a9ba Branch feature/asset-management Document 15/140 ++ 3 --
scholtz wallet
Merge 8a90fa26e2e0436d3ef835c30bf0dfbb26c30b30 into bca7c6be32befff7b143c3505833b050118ec47a
Git Commit 0db1a799 Branch pull/228/merge Document 27/4,295 ++ 80 --
scholtz-aures wallet
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>
Git Commit 8a90fa26 Branch feature/asset-management Document 13/160 ++ 18 --
scholtz wallet
Merge 7bd6afe963985db9df1269e2892398594fd7b83f into bca7c6be32befff7b143c3505833b050118ec47a
Git Commit 53759436 Branch pull/228/merge Document 27/4,153 ++ 80 --
scholtz-aures wallet
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>
Git Commit 7bd6afe9 Branch feature/asset-management Document 1/15 ++ 3 --
scholtz wallet
Merge d9806e8b2b55a40e351c577c36ea1c2cbe11b7e8 into bca7c6be32befff7b143c3505833b050118ec47a
Git Commit 11d41a65 Branch pull/228/merge Document 27/4,141 ++ 80 --
scholtz-aures wallet
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>
Git Commit d9806e8b Branch feature/asset-management Document 5/16 ++ 24 --
scholtz-aures wallet
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>
Git Commit 678834aa Branch feature/asset-management Document 2/68 ++ 13 --
scholtz wallet
Merge d95106220073d0706fe10d16a67868777c9a958f into bca7c6be32befff7b143c3505833b050118ec47a
Git Commit e0fd2f1b Branch pull/228/merge Document 27/4,094 ++ 80 --
scholtz-aures wallet
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>
Git Commit d9510622 Branch feature/asset-management Document 3/65 ++ 10 --
scholtz wallet
Merge c97f26985b1321fe45823d0668b57027452659c9 into bca7c6be32befff7b143c3505833b050118ec47a
Git Commit c9b208fc Branch pull/228/merge Document 27/4,039 ++ 80 --
scholtz-aures wallet
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>
Git Commit c97f2698 Branch feature/asset-management Document 16/251 ++ 103 --
scholtz wallet
Merge 564585b40aa12e4657e181e0b086a1ce4aa4ffe2 into bca7c6be32befff7b143c3505833b050118ec47a
Git Commit a1a1122c Branch pull/228/merge Document 27/3,893 ++ 82 --
scholtz-aures wallet
fix: address code review round 2 (double toast, stale roles, loading states, safety check, hub)
- signAndSend returns right after a cancelled/failed signature instead of
  trying to send nothing, which produced a second, false error toast.
- Change addresses: refuse and reload when a role changed on the chain since
  the form was filled, so an untouched field is never sent back with an old
  address.
- No "not opted in" / "could not be loaded" while a holding is still being
  fetched; the destroy view resets and guards its async creator lookup.
- assertAssetManagementTxnSafe also checks the freeze target and state, the
  clawback holder, receiver and amount, and the chosen addresses.
- Asset manager: roles only count for accounts the wallet can sign for; the
  create button is labelled "Create asset (ASA / NFT)".

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Git Commit 564585b4 Branch feature/asset-management Document 16/331 ++ 122 --
scholtz wallet
Merge 503668aafce4d163953973be27b50abe55874fc2 into bca7c6be32befff7b143c3505833b050118ec47a
Git Commit 81107b12 Branch pull/228/merge Document 27/3,683 ++ 81 --
scholtz-aures wallet
fix: address code review round 1 (holding refresh and load errors, stale result, hub text, typing, LF, send errors)
- Re-read the freeze / clawback holdings after a successful send, so the new
  frozen state and balances show (and Max uses the current balance).
- A holding the node cannot load is shown as "could not be loaded" instead of
  "not opted in"; the checks before signing use a strict lookup that reports
  the real error.
- Clear the "Transaction sent" result when switching to another action.
- Unnamed wallet accounts no longer show their address twice.
- Asset manager text says it lists created assets (roles held elsewhere are
  opened by ID).
- Route parsers take string | undefined instead of unknown; Actions.vue back to LF.
- algod/signAndSend reports a send failure without a node message too.
- E2E: the mocked ledger applies freeze/clawback; regressions for the refresh,
  the stale result and the failing holding lookup.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Git Commit 503668aa Branch feature/asset-management Document 17/819 ++ 362 --
scholtz-aures wallet
feat: asset management - freeze, clawback, address changes and destroy for ASAs
Replaces the empty /asset/{freeze,revoke,modify,destroy}/:assetId stubs with one
management page (plus /asset/manage/:assetId) and turns /asset into an asset
manager hub that lists the assets created by the wallet's accounts.

- Each action is signed by the asset's role address (freeze / clawback /
  manager), resolved with signingRouteFor: key and HD accounts sign in place,
  multisig / Ledger / Falcon hand the transaction to /signAll and return via
  "Return to asset management"; a role outside the wallet gets a clear message.
- The asset is re-read from algod and holdings re-checked right before
  signing; every built transaction passes assertAssetManagementTxnSafe
  (sender, type, asset, no rekey/close-out, fee cap).
- Clearing a role needs confirmation, restoring a cleared role and clearing
  every address (= destroy) are refused; destroy requires the whole supply
  back with the creator and a confirmation.
- Pure logic in src/scripts/assets/management.ts with unit tests; E2E covers
  direct freeze/clawback/modify/destroy, the multisig Sign-all round trip and
  the no-signer / disabled-role cases. Locales in all 10 languages.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Git Commit 0986fe9a Branch feature/asset-management Document 27/3,395 ++ 250 --
ipaleka frontend
DAO voting: vote panel on the session page, one card per linked seat; voteBridge.ts signs the vote call
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Git Commit ab0b808b Branch main Document 30/1,573 ++ 56 --