Closed Shaptic closed 8 months ago
There is an additional schema change: the getLedgerEntries RPC response will use liveUntilLedgerSeq rather than expirationLedgerSeq in the final build (ref: stellar/soroban-tools#1029)
@christian-rogobete the intent was only to add the comment at the end, apologies for the dupe
n.p. done in release 1.6.8
SDKs need to be updated to adapt to breaking changes that have occurred since Preview 11 (i.e. the current testnet release candidate) coming to Protocol 20.
Summary of Breaking Changes
This is likely irrelevant to SDK maintainers, but do note sandbox mode has been removed from the Soroban CLI (https://github.com/stellar/soroban-tools/issues/983).
XDR
The XDR needs to be updated to https://github.com/stellar/stellar-xdr/commit/6a620d160aab22609c982d54578ff6a63bfcdc01. This includes a non-trivial list of breaking changes (mostly renames):
BumpFootprintExpirationOp
is nowExtendFootprintTTLOp
and itsledgersToExpire
field is now namedextendTo
, but it serves the same purpose.ContractExecutable.contractExecutableToken
is nowcontractExecutableStellarAsset
SorobanTransactionData.refundableFee
is nowresourceFee
RPC
getEvents
RPC endpoint structure has changed:value: { xdr: string }
is now justvalue: string
(https://github.com/stellar/soroban-tools/pull/1015)contractId
will always be a contract strkey (C...
format) if present (https://github.com/stellar/soroban-tools/issues/1007)getLedgerEntries
RPC endpoint now includes expiration info (https://github.com/stellar/soroban-tools/pull/1010):expirationLedgerSeq
is a string-ifieduint32
present if the requested entries have expiration