NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules
Go modules, #1465 by repository stars
Latest stable
v0.8.0
Last release 16 days ago
06 Nov 2026
Ships on a steady schedule
a new release about every 1 weeks
Nearly every release is documented
notes for 12 of 12 stable releases
Nothing withdrawn
no release was ever pulled
9 years old
165 releases · first in 2018
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
…XDR stellar-core 30.0.0 pins. This release has breaking changes; see the CHANGELOG.
Protocol 30 (CAP-0084, CAP-0087, CAP-0088), with the XDR regenerated from stellar-xdr 4f524bba, the XDR stellar-core 30.0.0 pins. This release has breaking changes; see the CHANGELOG.
Full Changelog: https://github.com/stellar/go-stellar-sdk/compare/v0.7.3...v0.8.0
XDR_FEATURES is now empty.SC_SPEC_TYPE_NAME_LIMIT (1024 bytes), and ScSpecEventV0.Name is now a string instead of an ScSymbol (stellar/stellar-xdr#312). This arrives with the same regeneration but is not part of any CAP.OnDiskCache, MakeOnDiskCache, ConnectOptions.Wrap, ArchiveBucketCache and CacheOptions. They have had no callers since lighthorizon was removed (#5334) and Horizon moved to fscache (#5197). An early exit from a bucket read left a partial file in OnDiskCache that later reads served as complete (#6017)ScAddressTypeScAddressTypeMuxedContract arm of ScAddress. ScAddress.String() renders it as a W... muxed contract strkey.StellarValue: StellarValueTypeStellarValueSignedMs (SignedMsValue) and StellarValueTypeStellarValueEmptyTxSetMs (ProposedMsValue), and the TimePointMs type. Every ledger after the Protocol 30 upgrade ledger uses one of these arms, so earlier SDK versions cannot decode them.ContractCostType values 86–94 (MlDsa{44,65,87}DecodeVerifyingKey, MlDsa{44,65,87}DecodeSignature, VerifyMlDsa{44,65,87}Sig). These are names only; cost params are positional, so they decoded before.StellarValueExt.LedgerCloseValueSignature(), which returns the close-value signature from whichever StellarValue arm carries one: SIGNED, EMPTY_TX_SET (CAP-0083), SIGNED_MS or EMPTY_TX_SET_MS (CAP-0088). The generated GetLcValueSignature() only reads the SIGNED arm, so it finds no signature on any ledger after the Protocol 30 upgrade.VersionByteMuxedContract (W...), MuxedContract, DecodeMuxedContract, and IsValidMuxedContractAddress.ContractMuxed (contract_muxed) and ContractMuxedID (contract_muxed_id) to ContractCredited, set when the credit went to a muxed contract address (CAP-0084).Stream.ResumeFrom, which positions a new stream at the last record boundary of a failed one and continues its SHA-256 from there, so ValidateHash on the new stream covers both (#6017)QueryEventsRequest/QueryEventsResponse, QueryEventsFilter, scan statuses, typed error.data payloads), transcribed from the accepted proposal (#5971){amount, to_muxed_id}). A SAC transfer to a muxed destination (CAP-0067 M..., CAP-0084 W...) previously parsed as a transfer with Amount zero and no error. Event data with no amount now returns ErrNotTransferEvent instead of a zero-amount event.LedgerFileIter when the datastore contains directory placeholder objects, and reject a bucket path with empty, . or .. segments at startup (#6014)CheckpointChangeReader now resumes a failed bucket download from the last record boundary and continues the first download's SHA-256 from there, so the final hash check covers every record the reader returned. Before, the second download had its own hash and the records already returned from the first were not covered. A closed read channel now always means the producer has finished, so concurrent Read() callers cannot see io.EOF after a failure. xdr.Stream.Close is idempotent; a second close used to panic with the fscache-backed archive. NewHotArchiveIterator no longer blocks when the consumer stops early. Progress() returns 0 instead of NaN before the first bucket size is known (#6017)SetOptions values can be reused: BuildXDR no longer emits fields cleared after an earlier build, and FromXDR replaces every field instead of merging into the receiver; see the txnbuild changelog (#6021)Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
changelog: cut the Pending section as 0.7.2, and record 0.7.1 by @Shaptic in https://github.com/stellar/go-stellar-sdk/pull/5980
Full Changelog: https://github.com/stellar/go-stellar-sdk/compare/v0.7.2...v0.7.3
LedgerCloseMetaView.LedgerHeader(), exposing the version-resolving header accessor that already backs LedgerSequence, LedgerCloseTime, LedgerHash, and PreviousLedgerHash (#5982)Client.URL() to expose the configured RPC server URL (#5885)to_muxed_id bound to Void in V4 event data. CAP-0067 specifies that the key is simply absent when there is no muxed destination, and that form already parsed. Void is what a contract emits instead if it publishes its event data as a #[contracttype] struct with an Option field — the natural way to write it before CAP-0086's sparse maps, which omit the key. Such an event previously failed to parse and was dropped from the event stream entirely, silently (#5983)to_muxed_id of type ScvBytes at the length the contract emitted. It was previously copied into a fixed 32-byte buffer, so a shorter value was right-padded with zeroes and a longer one truncated, reporting a muxed id that was never emitted. Only a classic transaction memo maps to a fixed 32 bytes here; a contract may put any byte string in to_muxed_id (#5984)Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
xdr: compare assets by their XDR encoding, and use Equals for asset equality by @karthikiyer56 in https://github.com/stellar/go-stellar-sdk/pull/5974
Full Changelog: https://github.com/stellar/go-stellar-sdk/compare/v0.7.1...v0.7.2
Decode and DecodeAny now validate the payload length against the version byte per SEP-23. Fixed-length keys (account ID, seed, muxed account, contract, liquidity pool, claimable balance, hashTx, hashX) must decode to their exact canonical size, and signed payloads must carry a declared payload length of 1–64 bytes matched by their zero padding. Inputs with a valid checksum but a wrong-length payload — previously accepted by Decode, DecodeAny, and every IsValid* helper — are now rejected. (#5977)
NewSignedPayload rejects empty payloads, matching CAP-40 (the protocol fails such signers with SET_OPTIONS_BAD_SIGNER/txMALFORMED) and keeping SignedPayload.Encode output decodable.Decode now subsumes were removed from xdr.AccountId.SetAddress, xdr.MuxedAccount.SetAddress, xdr.SignerKey.SetAddress, xdr.ClaimableBalanceId.DecodeFromStrkey, strkey.DecodeMuxedAccount, strkey.MuxedAccount.SetAccountID, and txnbuild contract-address parsing. For wrong-length inputs, the xdr and txnbuild callers now return strkey's invalid payload length error instead of their own; the strkey muxed-account helpers keep their generic invalid muxed account / invalid ed25519 public key errors; xdr.MuxedAccount.SetAddress is unchanged (it rejects on encoded string length before decoding).keypair.ParseAddress wraps every decode failure with ErrInvalidKey, so errors.Is(err, ErrInvalidKey) keeps matching wrong-length keys (and now also matches checksum/encoding failures, which previously returned the bare strkey error).DecodeSignedPayload delegates structure validation to Decode; structurally invalid inputs now uniformly error with invalid signed payload (previously signed payload too short: ... or invalid signed payload padding).Asset.LessThan now orders assets the way the protocol does — by the raw 32-byte issuer key — instead of by base32 strkey text, and xdr.NewPoolId requires strictly a < b, rejecting reversed and identical pairs (#5974)ApplyLedgerMetadata now closes the datastore and the ledger backend, and returns the PrepareRange error instead of discarding it — an early return previously stranded one goroutine per configured worker and a failed prepare went unnoticed (#5974)mergeInputLenAndMaxSize so a variable-length field whose length prefix ends the input keeps both its schema and input-length bounds. Every generated type decodes through this decoder (#5974)Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.