registry/display: complete integration with genesis and execution layer#25240
Merged
amnn merged 3 commits intoml/display-registryfrom Feb 5, 2026
Merged
registry/display: complete integration with genesis and execution layer#25240amnn merged 3 commits intoml/display-registryfrom
amnn merged 3 commits intoml/display-registryfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
This was referenced Feb 3, 2026
## Description Previously, the Move Compiler's ID Leak check was updated, but not the verifier used during execution. This change also switches Display Registry to be created at its well-known address (0xd). ## Test plan Without this change, E2E tests would fail to execute the transaction that creates the Display Registry.
## Description Regenerate sui framework snapshots for Display Registry changes. ## Test plan CI
## Description Make it so that if Display Registry is enabled at Genesis, the Display Registry object is created. ## Test plan Used for E2E tests up the stack.
amnn
added a commit
that referenced
this pull request
Mar 10, 2026
## Description GraphQL will look for and preference `sui::display_registry::Display<T>` over `sui::display::Display<T>` (+ its events) when computing the Display output for a given Move Value. ## Test plan New E2E tests: ``` $ cargo nextest run \ -p sui-indexer-alt-e2e-tests \ --test transactional_tests \ -- display_v2 ``` ## Stack - #23710 - #25240 - #25241 --- ## Release notes Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required. For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates. - [ ] Protocol: - [ ] Nodes (Validators and Full nodes): - [ ] gRPC: - [ ] JSON-RPC: - [x] GraphQL: Adds support for Display Registry to GraphQL: `MoveValue.display` will look for a `Display<T>` stored in the Display Registry and will use that as the source of truth for its type's format. This takes precedence over any Display v1 formats that exist for this type. - [ ] CLI: - [ ] Rust SDK: - [ ] Indexing Framework:
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
2 participants
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.
Description
0xd).Test plan
How did you test the new or updated feature?
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.