Repository navigation
feat(minter): read deposit address balances in batches with the typed getMultipleAccounts - #282
Merged
Merged
Conversation
Replace the outdated section 3.1.1, which described per-transaction crediting with getSignaturesForAddress and quotas replenished by the removed process_deposit endpoint, with a design that builds on the balance sweep of deposit_sol: a free registration endpoint, a scan timer reading watched deposit addresses in batches with getMultipleAccounts, a schedule adapted from the ckETH minter, a fixed fee in SOL deducted from the minted amount, and a watchlist persisted only as a bounded snapshot at pre_upgrade. Every change to the interface, the arguments and the event log is additive, since the minter is deployed on mainnet. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
State that a re-armed account is reported as watching again, that the main account receives the sweepable amount minus the fee share, correct the worst-case cost arithmetic and state its success assumption, and distinguish a failed upgrade from a reinstallation. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…ring Move the sequence diagram of the automatic flow ahead of its explanation, remove the semicolon that broke the mermaid parser on GitHub, and define the deposit id where it is first used in the section. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…he constraint State that scan ticks are guarded like the other timers so that they never overlap, and base the automatic deposit fee constraint on the single-signature fee share that a pending mint actually bears. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Drop the separate status query: calling the registration endpoint again returns the stored registration or the id of the deposit in flight, as deposit_eth does in the ckETH minter. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
… signature lookup Spell out that scan ticks never overlap, that the fee derivation is a single-attempt estimate with re-arm costs absorbed by the minter, and that only manual deposits are retried by the caller. Remove getSignaturesForAddress from the RPC inventory and cost tables, since the minter no longer uses it. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
A re-armed entry restarts its schedule from the first gap, bounded by the remaining window, and a re-arm only ever follows a detection. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Record the watchlist snapshot on every upgrade so that an older one cannot be replayed after the watchlist emptied, and let the transaction submission section account for deposits queued by the balance scan. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The window ends with the last scan, and the next registration call starts a new window rather than reporting a registration without a next scan. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…it ids Follow the ckETH minter: a registration freezes neither the minimum deposit amount nor the automatic deposit fee, both are quoted and the values in force at detection apply, the fee being recorded with the queued deposit. deposit_sol compares the latest deposit id of the account before and after its balance read, and a registration is allowed while a deposit_sol call is in progress. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…edule Measure gaps from the previous scan as before, but end the window at a fixed 24 hours after registration, as the ckETH minter does, so that the accumulated tick and call delays have slack and clients and the re-arm share one unambiguous boundary. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…ence Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…owner rationale The fee recorded at detection matters for deposits an upgrade finds not yet credited; a credited deposit has its mint amount in CreditedSweep. The minter's principal is excluded as a deposit owner because its default account is the ledger's minting account, not because of an address collision. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…xample with the automatic flow Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…er a concurrent scan Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…n delay and the fee worst case Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…or to new registrations Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…vents the automatic flow adds Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
gregorydemay
force-pushed
the
DEFI-2780-07-get-multiple-accounts
branch
from
October 14, 2026 09:04
22f1571 to
194a84c
Compare
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
Raw provider-specific response context prevents reliable 3-of-4 consensus through jsonRequest.
1 open finding
What changed in this PR
Adds batched Solana deposit-balance reads through getMultipleAccounts.
Changes:
- Adds generic JSON-RPC batching with dynamic cycles and response sizing.
- Parses balances and handles malformed/inconsistent responses.
- Expands RPC test fixtures and coverage.
| File | Description |
|---|---|
minter/src/rpc/mod.rs |
Implements batched balance retrieval. |
minter/src/rpc/tests.rs |
Tests requests, sizing, and errors. |
minter/src/constants.rs |
Defines batch limits and cost estimates. |
minter/src/test_fixtures/mod.rs |
Generates RPC response fixtures. |
minter/src/test_fixtures/runtime.rs |
Records cycles and stubs responses. |
minter/Cargo.toml |
Promotes serde_json to a runtime dependency. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
gregorydemay
force-pushed
the
DEFI-2780-07-get-multiple-accounts
branch
from
October 14, 2026 09:18
194a84c to
88ec974
Compare
… mints The deposits hand the credited sweep back to the state, which reads the fees it collects; the fee accessor of a queued deposit is named after the fee alone; the mints of a sweep fail with their own error type; and the count of automatic deposits, which a fee does not establish, is dropped. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The plan-level fee test and the decode test of the old queued deposit encoding go, the state test asserts the amount received, the rejected Candid deposit carries an arbitrary fee, and the replay of the recorded log takes no extra events. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…leAccounts Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
gregorydemay
force-pushed
the
DEFI-2780-07-get-multiple-accounts
branch
from
October 15, 2026 12:30
f3d9e68 to
f28f6f1
Compare
The typed `getMultipleAccounts` of dfinity/sol-rpc-canister#394 is not released yet, so the client and types crates are patched to that commit until it is. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…tMultipleAccounts Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…the pinned commit Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
… of building it Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
gregorydemay
commented
Oct 15, 2026
…nts response The parameters, the cycles and the response size estimate the SOL RPC client sends are its own to test, and the one account per requested address is the SOL RPC canister's contract, so the count check goes with its tests. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
✅ No security or compliance issues detected. Reviewed everything up to 1f35c9d. Security OverviewDetected Code Changes
|
eichhorl
reviewed
Oct 22, 2026
…t per address The balances are paired with the addresses by position, and the SOL RPC canister does not guarantee one account per requested address in the pinned version, so a short response would leave the addresses past its end unread. A response with the wrong number of accounts is now an error. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Pins the parameters, the response size estimate and the cycles the minter chooses for 1 and 100 addresses, which the tests of the response alone leave unchecked. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…e to the SOL RPC canister As for every other call, the SOL RPC canister prices the call with its own default estimate, which allows 192 bytes per account without data in its upcoming release, close to what the minter estimated, so the minter no longer mirrors the canister's internal sizes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Replace the pins to the dfinity/sol-rpc-canister#394 commit with the released sol_rpc_client 7.0.0 and sol_rpc_types 4.0.0, and run the integration tests against the SOL RPC canister v1.4.0 release wasm. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
mbjorkqvist
approved these changes
Nov 4, 2026
eichhorl
approved these changes
Nov 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


Reads up to 100 deposit address balances at once for the scans of the automatic deposit flow of #272 with the typed
getMultipleAccountsof the SOL RPC canister, with cycles sized by the number of addresses. The function is only used by the scan timer, which lands next.The typed method ships with the SOL RPC canister v1.4.0 (dfinity/sol-rpc-canister#394), whose
sol_rpc_client7.0.0 andsol_rpc_types4.0.0 crates this PR depends on, and which the production SOL RPC canister already runs.🤖 Generated with Claude Code