[docs-agent] Add Solana Account Archive guide, OpenRPC entry, CU pricing row - #1492
Merged
Conversation
…ing row
Adds the initial docs for Solana Account Archive: an extension of `getAccountInfo` with three new mutually-exclusive parameters (`slot`, `lastUpdateBeforeSlot`, `firstUpdateAfterSlot`) for point-in-time and cursor-based historical reads. Coverage extends back to July 2025 with no pruning.
Changes:
* New guide + FAQ page at content/api-reference/solana/account-archive.mdx sourced from the internal Notion doc.
* New OpenRPC spec at src/openrpc/alchemy/solana-account-archive/solana-account-archive.yaml with three worked examples (point-in-time, walk-backward, walk-forward) and error -32020 documented for cursor-past-coverage.
* docs.yml: new 'Solana Account Archive' section under Solana with the guide page + flattened endpoints entry.
* compute-unit-costs.mdx: new 'Solana: Account Archive' block with TBD rows and a note that final per-method pricing is pending.
Assumptions flagged for reviewer confirmation:
* Endpoint host uses the standard `solana-mainnet.g.alchemy.com/v2/{apiKey}` (drop-in with normal Solana calls). Easy to switch to a distinct archive host if that's the actual routing.
* Chain scope: mainnet only for v1 (no devnet/testnet server entries). Add a devnet server if the archive is available there.
* No preview / private-beta callout on the guide. Add one if this ships behind an allowlist.
* CU pricing left as TBD per the original ask ("temporary for now if you dont have per method CU pricing").
Refs DOCS-168
Requested-by: @clinder777
🔗 Preview Mode
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: bf6f434e94
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
Codex flagged the inconsistency between the OpenRPC spec advertising x-compute-units: 10 and the pricing page showing TBD for the three archive params. Since Canaan's original ask was to leave pricing as TBD until topconfig.yml values land, remove the hardcoded CU value from the spec so both surfaces agree. Refs DOCS-168 Requested-by: @clinder777
… against prod Verified against the live endpoint: cursor walks terminate only with -32020 (a null value mid-walk is a deletion write, not end-of-history), slot 310M is below the coverage floor (~353.9M) so examples move to slot 400M, and all example responses are now real output for the top USDC token account. Also drops the excluded-accounts sentence (kept in FAQ) and the unfinalized-tier parenthetical, matching the internal Notion doc. Co-authored-by: Cursor <cursoragent@cursor.com>
…erence Drops the separate solana-account-archive OpenRPC spec and nav section: the archive is served on the standard endpoint, so the slot / lastUpdateBeforeSlot / firstUpdateAfterSlot params now live on the original getAccountInfo reference page, with the guide kept as a plain page. Also repositions the historical-account-state guide to lead with the Account Archive as the direct primitive, keeping Yellowstone capture and transaction replay for program-wide sets and pre-coverage history. Co-authored-by: Cursor <cursoragent@cursor.com>
…ount Archive The page taught workarounds for the absence of a historical getAccountInfo primitive, which the Account Archive now provides directly. Its slug redirects to the archive guide, and the still-unique guidance (program-wide capture via Yellowstone, pre-coverage balance reconstruction) moves into the archive guide's FAQ. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
SahilAujla
approved these changes
Aug 3, 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.
Summary
Adds the initial docs for Solana Account Archive, Alchemy's historical account state service. Answers
getAccountInfofor any Solana account at any historical slot from July 2025 onward, using the same request and response shapes as standard Solana RPC.The archive extends
getAccountInfowith three mutually-exclusive parameters, also mutually exclusive withminContextSlot:slotlastUpdateBeforeSlotfirstUpdateAfterSlotOmit all three for a normal latest-state read: the archive is a drop-in superset.
Changes
content/api-reference/solana/account-archive.mdx, sourced from the internal Notion doc. Covers the API surface, cursor iteration pattern, backfill-via-replay architecture, trust model, and FAQ entries.getAccountInforeference extended insrc/openrpc/chains/_components/solana/{methods,account}.yaml: the three archive parameters are documented on the original endpoint page (the archive is served on the standard endpoint, so no separate spec/endpoint page), with a worked historical Try It example at slot 400,000,000.historical-account-state.mdxremoved: the page taught workarounds for the absence of a historicalgetAccountInfoprimitive, which the archive now provides directly. Its slug 301-redirects to the archive guide, and the still-unique guidance (program-wide capture via Yellowstone, pre-coverage balance reconstruction) moved into the archive guide FAQ.docs.yml:Solana Account Archiveguide page added under the Solana section (plain page, no endpoint sub-section).compute-unit-costs.mdx: newSolana: Account Archiveblock with TBD rows and a note that final per-method pricing is pending.Semantics verified against prod
All examples are real responses from the live endpoint, and the documented behavior was tested against it:
-32020; anullvalue mid-walk is a deletion write (the account did not exist as ofcontext.slot), and the walk continues from that slot.3emsAVdmGKERbHjmGfQ6oZ1e35dkf5iYcS6U4CPKFVaa), with realjsonParsed/base64 payloads, realcontext.slotcursor values, and the realrentEpochsentinel.Assumptions to confirm
solana-mainnet.g.alchemy.com/v2/{apiKey}(matches the doc's "drop-in superset" framing and verified working).solana-devnetserver entry). Add if the archive is available on devnet/testnet.TBDper Canaan's original message ("temporary for now if you dont have per method CU pricing"). Will fill in oncetopconfig.ymlvalues land.Validation
pnpm run generate:rpc→ ✅pnpm run validate:rpc→ ✅Successfully validated json-rpc OpenRPC specspnpm run lint→ 0 errors (6 pre-existing baseline warnings unrelated to this diff)Linear
DOCS-168
Requested by
@clinder777 (via Slack thread)