Skip to content

v1.5.3

Latest

Choose a tag to compare

@tasosbit tasosbit released this 20 Nov 18:12
588e534

A nodemgr and UI bugfix release for algod 5.1. No contract changes — the protocol is untouched. Node runners on algod 5.1 or later should upgrade nodemgr: without this fix, epoch payouts that distribute rewards are rejected.

Fixes

  • Epoch payouts failed with group fee too small on algod 5.1. nodemgr and the dashboard simulate each call first, then send it with the fee the simulation says it needs. That fee was estimated as appBudgetAdded / 700, which only held because simulate used to count 700 of added budget for every inner transaction. go-algorand #6708 (algod 5.1.0) stopped counting payment-only inner groups, so the estimate came up one min fee short for every inner payment or asset transfer — exactly what epochBalanceUpdate does when it pays out rewards.

    Fees now come from group-usage, algod's own figure for what the whole group must pay, covering inner transactions at any depth and size-priced transactions. The required total is ceil(groupUsage × minFee / 1e6), which is the same rule algod applies when it checks the group. This applies to epochBalanceUpdate, addStake and removeStake in nodemgr, and to staking, unstaking, epoch updates and token claims in the dashboard. group-usage is reported by algod 5.0 and later.

  • Token claims put the whole group's extra fee on every pool's claim instead of once, overpaying by one share per pool. Fees pool across the group, so it now goes on the first claim only.

  • nodemgr dropped an error while building the removeStake group; it is now returned.

  • Pera PQ accounts: transactions mutated by the wallet were submitted and executed, but confirmation waited on the pre-mutation transaction id and failed. Fixed by algokit-utils 9.2.2 (#413). This has been live on the dashboard since v1.5.2, which was not tagged as it was a UI-only fix for PQ accounts.

Behaviour change

Fees are now exact for the simulated state. The old formulas overpaid by 1,000–3,000 µALGO on most calls, which doubled as headroom. If chain state changes between simulate and send so that a call needs one more inner transaction — for example another staker filling the chosen pool — the group is rejected and has to be retried.

Maintenance

  • go-algorand-sdk 2.7.0 → 2.14.0, which requires Go 1.25; nodemgr's go.mod, Dockerfile-nodemgr and the release build move from Go 1.23 to 1.25.
  • algosdk 3.6.0 → 3.8.0 in ui, contracts and contracts/bootstrap.
  • CI pins the Playwright runner to ubuntu-24.04 and runs prettier from the local install.

Testing

New table tests cover the fee calculation in nodemgr and the dashboard. Against MainNet algod 5.1.1, simulating epochBalanceUpdate on live pools, the old estimate fell one min fee short on a pool whose payout sends 47 inner transactions, and the new fee succeeds.

Full Changelog: v1.5.1...v1.5.3