Protocol 21 SDK Support

[psheth9]

Protocol 21 SDK Support

Once voted in, the release of Protocol 21 will introduce following new CAPs:

• CAP-51: Smart Contract Host Functionality
• CAP-53: Separate host functions to extend the TTL for contract instance and contract code
• CAP-54: Soroban refined VM instantiation cost model
• CAP-55 : Soroban streamlined linking
• CAP-56: Soroban intra-transaction module caching

XDR changes:

XDR update issue details - stellar/stellar-xdr@1a04392

Reference Implementations:
js-sdk - stellar/js-stellar-base#738

Soroban API Changes:

Breaking Changes:

• simulateTransaction: soroban-rpc: adding optional params breaks clients using params array format stellar/soroban-rpc#13

Non Breaking changes:

• Add StateDiff to simulateTransaction Response: Add ledger entry diff to simulateTransaction response stellar/soroban-rpc#120

New optional field in SimulateTransactionResponse which indicates how the state (ledger entries) will change as a result of the transaction execution.

StateDiff       []LedgerEntryDiff            `json:"stateDiff,omitempty"`   

type LedgerEntryDiff struct {
	Before string `json:"before,omitempty"` // LedgerEntry XDR in base64
	After  string `json:"after,omitempty"`  // LedgerEntry XDR in base64
}

• Add ledger Range to getHealth RPC: Add ledger range to getHealth endpoint stellar/soroban-rpc#133

New Ledger Range and Ledger Retention Window in getHealth Response

type HealthCheckResult struct {
	Status                string `json:"status"`
	LatestLedger          uint32 `json:"latestLedger"` // New
	OldestLedger          uint32 `json:"oldestLedger"` // New
	LedgerRetentionWindow uint32 `json:"ledgerRetentionWindow"` // New
}

Horizon API Changes:

• There are no changes to Horizon APIs

Reference Implementations

Reference implementation authored by SDF:

• JavaScript: Epic: Add support for new endpoints and fields in the Soroban RPC SDK. stellar/js-stellar-sdk#935

You can follow each respective issue to its implementation PRs.

[christian-rogobete]

Hello @psheth9 , thank you for adding this issue. It has been resolved in release 1.8.0