Skip to content

Instantly share code, notes, and snippets.

@Shaptic

Shaptic/protocol-20-updates.md Secret

Last active November 30, 2023 21:49
Show Gist options
  • Save Shaptic/d8cac9464f7dce6489511f4f16370957 to your computer and use it in GitHub Desktop.
Save Shaptic/d8cac9464f7dce6489511f4f16370957 to your computer and use it in GitHub Desktop.
Download ZIP
Additional breaking changes to the Protocol 20 Soroban RPC API
Raw
protocol-20-updates.md

Protocol 20 Changes

There are additional breaking changes to the Soroban RPC schema.

Soroban RPC

  1. The schema for getLedgerEntries has a rename:
  • expirationLedgerSeq is now named liveUntilLedgerSeq
  1. The data type for all references to ledger sequence numbers (and some others) have been unified to always be an unsigned, 32-bit integer values (uint32) rather than strings. This includes:
  • getNetwork's protocolVersion
  • getLatestLedger's latestLedger
  • simulateTransaction's latestLedger
  • sendTransaction's latestLedger
  • getTransaction's latestLedger, oldestLedger, and ledger
  • getLedgerEntries's latestLedger, lastModifiedLedgerSeq, and liveUntilLedgerSeq
  • getEvents's latestLedger and each event's ledger
  1. The request format for getEvents has also changed:
  • startLedger must now be a uint32 rather than a string
@2opremio
Copy link

have been unified to always be an unsigned, 32-bit integer (uint32)

I would also mention that they are not stringified anymore

@Shaptic
Copy link
Author

Shaptic commented Nov 30, 2023

thanks, @2opremio! fixed up

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