Regenerate with ids on contract spec entries - #568
Closed
leighmcculloch wants to merge 4 commits into
Closed
Conversation
This was referenced Aug 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
Part of a stack of PRs that must merge in this order.
A first group of PRs deliver const-encoded contract specs, so that contract specs are produced at compile time instead of at proc-macro execution time. This provides the foundation for the capability to construct the specs from information that is not known at proc-macro execution and only known at compile time, like the fully qualified name of a type:
A second group of PRs deliver ids on contract spec entries and in spec references. Every entry carries an 8-byte id hashed from the fully qualified name of the item it describes, and a reference to a user-defined type carries the id of the entry it refers to, so references stay unambiguous even when items share a name. This resolves the type identity problem (stellar/rs-soroban-sdk#1570) and type alias limitations (stellar/rs-soroban-sdk#1857):
What
Regenerate the Rust types from stellar/stellar-xdr#313: a new
ScSpecEntryV2struct pairing an 8-byteidwith aScSpecEntryV2Bodyunion that reuses the existing V0 entry bodies, exposed as a newScSpecEntry::V2arm; aScSpecTypeUdtv2reference carrying the referenced type's name and the id of the entry it refers to; and theSC_SPEC_ID_LENconst. All new types come with the const-writable View counterparts, so the SDK's proc macros can encode them at compile time.Why
Ids on spec entries identify each entry exactly — the id is the truncated SHA-256 of the fully qualified name of the item the entry describes — so every entry has a unique identifier, and a reference carrying an id refers to one entry precisely, even when entries share a name.