Skip to content

Proposal: RPC v2 account and synchronization API - #2869

Open
Mirko-von-Leipzig wants to merge 3 commits into
nextfrom
mirko/rpc-v2-proposal
Open

Mirko-von-Leipzig wants to merge 3 commits into
nextfrom
mirko/rpc-v2-proposal

Conversation

@Mirko-von-Leipzig

@Mirko-von-Leipzig Mirko-von-Leipzig commented Nov 2, 2026 •

Copy link
Copy Markdown
Collaborator

Adds a proposed v2 service definition and usage proposal.

For discussion of API coverage before implementation. See the accompanying markdown file for more specifics.

Proposal summary

SyncAccount lets you sync an account's storage if it is small enough. Large accounts (defined by the server, some amount of map/vault entries) must use streaming SyncXxx methods. The idea is that 99% of accounts can just use SyncAccount.

Paginated methods are replaced by streaming equivalents.

GetAccount is broken up into more specific methods. Clients can request concurrently to maintain lower latency.

More explicit/obvious support for lazy loading / FPI for data store usage e.g. GetAccountWitness.

Changelog

changelog = "none"
reason    = "Proposal only; no runtime API changes."

Comment thread proto/proto/v2/rpc.proto
Comment on lines +55 to +56
// Immutable code addressed by its commitment.
rpc GetAccountCode(GetAccountCodeRequest) returns (GetAccountCodeResponse) {}

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will change based on how the code registry plays out.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant