docs(rpc): nearcore 2.13.0 RPC reference + technical descriptions#28
Merged
Conversation
Deploying builder-docs with
|
| Latest commit: |
6acdb94
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://0f089730.builder-docs.pages.dev |
| Branch Preview URL: | https://docs-nearcore-2-13-0-rpc.builder-docs.pages.dev |
Vendored from mike-docs docs/nearcore-2.13.0-rpc (#5) and 16069-rpc-description-recovery (#7): - view_state pagination (after_key_base64 / limit / last_key) + prefix_base64, technical register - view_access_key_list post-quantum (ML-DSA-65) wording - config field updates (client_config / genesis_config / EXPERIMENTAL_protocol_config) - recovered + technicalized 7 RPC descriptions (call_function, tx_status, EXPERIMENTAL_tx_status, broadcast_tx_async / broadcast_tx_commit, send_tx) - structured-graph nearcoreSource pinned to nearcore 2.13.0 Applied surgically: only the 11 changed RPC page models and nearcoreSource are updated; the richer REST schemas (neardata) and all other content on main are preserved untouched. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
mikedotexe
force-pushed
the
docs/nearcore-2.13.0-rpc
branch
from
July 14, 2026 21:50
b3d437c to
6acdb94
Compare
mikedotexe
changed the title
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
1 participant
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.
Brings the public RPC reference to nearcore 2.13.0 and lands a technical-register pass over the affected descriptions.
Supporting mike-docs PRs: fastnear/docs-pipeline#5 (2.13.0 sync + field-description machinery) and fastnear/docs-pipeline#7 (recover + technicalize 7 RPC descriptions, tracks nearcore #16069).
What changes on the docs
after_key_base64/limit/last_keypagination +prefix_base64, written as protocol reference ("Exclusive start cursor: returns only keys greater than this one…", "Maximum key/value entries per response (≥ 1)…")call_function,tx_status,EXPERIMENTAL_tx_status,broadcast_tx_async/broadcast_tx_commit,send_tx, tightened to protocol terms (SignedTransaction, Borsh/base64,wait_until, 10s timeout, deprecation)nearcoreSource→ nearcore 2.13.0Vendored surgically
Only the 11 changed RPC page models and
nearcoreSourceare updated. The richer REST schemas (neardataBlockDocument, etc.) and all other content onmainare preserved untouched — mike-docs main is still catching up on those (see reconcile PR fastnear/docs-pipeline#6).