[dependabot]

Bumps @blockrun/llm from 3.24.4 to 3.25.0.

Release notes

Sourced from @​blockrun/llm's releases.

3.25.0 — batch.onLocked

Added — batch.onLocked: wait or fail instead of paying exact (issue #96)

• Batch pays in one process per wallet: the process that opened the channel holds its store's lock until it exits, and other processes on the wallet paid exact (1.5–2.5x the metered price), seen only as a channel_store_locked fallback. The README now says so. New batch.onLocked: "exact" | "wait" | "throw" (default "exact", unchanged) and batch.lockWaitMs (default 60000): "wait" waits for the lock and then pays with batch, "throw" raises the new BatchChannelLockedError ("unpaid", nothing signed), as does "wait" once its wait runs out. Exported: BatchChannelLockedError, DEFAULT_BATCH_LOCK_WAIT_MS.

3.24.10 — 600 s Solana timeout, finalized deposit blockhash

Fixed — SolanaLLMClient waits as long as LLMClient (issue #93)

• SolanaLLMClient aborted every request after a fixed 60 s, while LLMClient waits 600 s and honours BLOCKRUN_CHAT_TIMEOUT. A reasoning model's long turn (moonshot/kimi-k3.1-pro at 60.3 s) was aborted after its batch payment was sent, ending in BatchPaymentUnresolvedError. Both clients now share one default: BLOCKRUN_CHAT_TIMEOUT (seconds) when set, else 600 s; the timeout option still overrides it.

Fixed — batch deposits sign with a finalized blockhash

• When a batch 402 names no recentBlockhash, @x402/svm built a deposit (open or top-up) with a blockhash read at @​solana/kit's default confirmed commitment. PayAI's verifier runs behind the tip and can reject it as BlockhashNotFound: the deposit is refused and the call pays exact. The SDK now adds a blockhash read at finalized from your RPC (cached 10 s per RPC URL) to its copy of the 402 when the payment will likely carry a deposit. A blockhash the 402 names is kept; authorizations read nothing; a failed read leaves the scheme's own read in place.

v3.24.9

Fixed — a reclaimed channel with deposit to spare is re-read when refused

• The chain was read only before a top-up, so a reclaimed channel whose record still had deposit to spare got an authorization signed into it on every call. The gateway refuses those at verify with a plain 402, and every call paid exact. Now an authorization refused with a plain 402 (no receipt, not an admission refusal) re-reads its channel at once: open and the wallet's → kept; closing, closed or not the wallet's → re-read through resync; gone at finalized and confirmed → the same anchored wait as a top-up (exact for about two minutes, then the record is dropped and the next call opens afresh). The saved anchor is read before the payment is built (the scheme rewrites the record without it), so a process that makes one call per run still finishes

... (truncated)

Changelog

Sourced from @​blockrun/llm's changelog.

[3.25.0] - 2026-10-27

Added — batch.onLocked: wait or fail instead of paying exact (issue #96)

• Batch pays in one process per wallet: the process that opened the channel holds its store's lock until it exits, and other processes on the wallet paid exact (1.5–2.5x the metered price), seen only as a channel_store_locked fallback. The README now says so. New batch.onLocked: "exact" | "wait" | "throw" (default "exact", unchanged) and batch.lockWaitMs (default 60000): "wait" waits for the lock and then pays with batch, "throw" raises the new BatchChannelLockedError ("unpaid", nothing signed), as does "wait" once its wait runs out. Exported: BatchChannelLockedError, DEFAULT_BATCH_LOCK_WAIT_MS.

[3.24.10] - 2026-10-27

Fixed — SolanaLLMClient waits as long as LLMClient (issue #93)

• SolanaLLMClient aborted every request after a fixed 60 s, while LLMClient waits 600 s and honours BLOCKRUN_CHAT_TIMEOUT. A reasoning model's long turn (moonshot/kimi-k3.1-pro at 60.3 s) was aborted after its batch payment was sent, ending in BatchPaymentUnresolvedError. Both clients now share one default: BLOCKRUN_CHAT_TIMEOUT (seconds) when set, else 600 s; the timeout option still overrides it.

Fixed — batch deposits sign with a finalized blockhash

• When a batch 402 names no recentBlockhash, @x402/svm built a deposit (open or top-up) with a blockhash read at @​solana/kit's default confirmed commitment. PayAI's verifier runs behind the tip and can reject it as BlockhashNotFound: the deposit is refused and the call pays exact. The SDK now adds a blockhash read at finalized from your RPC (cached 10 s per RPC URL) to its copy of the 402 when the payment will likely carry a deposit. A blockhash the 402 names is kept; authorizations read nothing; a failed read leaves the scheme's own read in place.

[3.24.9] - 2026-10-27

Fixed — a reclaimed channel with deposit to spare is re-read when refused

• The chain was read only before a top-up, so a reclaimed channel whose record still had deposit to spare got an authorization signed into it on every call. The gateway refuses those at verify with a plain 402, and every call paid exact. Now an authorization refused with a plain 402 (no receipt, not an admission refusal) re-reads its channel at once: open and the wallet's → kept; closing, closed or not the wallet's → re-read through resync; gone at finalized and confirmed → the same anchored wait as a top-up (exact for about two minutes, then the record is dropped and the next call opens afresh). The saved anchor is read before the payment is built (the scheme rewrites the record without it), so a process that makes one call per run still finishes

... (truncated)

Commits

• 8fb3a09 release: 3.25.0
• 2c8af6f feat(batch): batch.onLocked waits for or fails on another process's channel l...
• 644b02c release: 3.24.10
• f0b4579 fix(batch): sign deposits with a finalized blockhash when the 402 names none ...
• 51bba02 fix(solana): default SolanaLLMClient to LLMClient's 600 s timeout (#94)
• f8bc955 release: 3.24.9
• 9ec2a2d fix(spend): let settlement evidence beat a skip header; book BlockrunClient c...
• 15d86ce fix(batch): re-read a channel whose authorization is refused with a plain 402...
• fed16d7 Merge pull request #89 from BlockRunAI/fix/settlement-skipped-books-zero
• 9e5e932 Merge remote-tracking branch 'origin/main' into fix/settlement-skipped-books-...
• Additional commits viewable in compare view

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: BlockRunAI/ClawRouter
• Branch: main
• File: .coderabbit.yaml
• Commit: c95dab6
• Layers: Repository YAML
• Review profile: CHILL
• Plan: Advanced
• Run ID: 649d94f2-ae75-4011-86ef-db5d089f2081

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

CodeRabbit Verify

• Run CodeRabbit Verify to test the changes in this pull request.

[VickyXAI]

Reviewed; CI green.