Repository navigation
0.55.8 — Solana payments sign on the gateway's quoted blockhash - #212
Merged
Merged
Conversation
…ckrun/llm 3.26.5)
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.
Raises
@blockrun/llmto^3.26.5and releases 0.55.8.@blockrun/llm 3.26.5 signs Solana
exactpayments on the 402's quotedextra.recentBlockhashwhen it is a valid 32-byte base58 hash, instead of a blockhash the SDK fetched itself. That is afinalizedhash every facilitator verifier has seen, and the Solana gateway applies its sandbox-create payment-window check only to payments signed on the hash it quoted. With no valid quote the payment is built exactly as before. MCP signs through the SDK'sSolanaLLMClient, so no MCP code changes.Lockfile: only
@blockrun/llm3.25.0 → 3.26.5 and the package version.npm test: 1479 passed, 0 failed; build and typecheck clean.🤖 Generated with Claude Code