Skip to content

wip(registry/display): enable Display Registry#25241

Merged
amnn merged 1 commit intoml/display-registryfrom
amnn/disp-enable
Feb 5, 2026
Merged

wip(registry/display): enable Display Registry#25241
amnn merged 1 commit intoml/display-registryfrom
amnn/disp-enable

Conversation

@amnn
Copy link
Copy Markdown
Contributor

@amnn amnn commented Feb 3, 2026

Description

Enables Display Registry in Protocol Config 109, for non-production networks. This is to unblock E2E tests in integration PRs, but should not be landed until we are comfortable with Display Registry going out to Devnet.

Test plan

E2E tests further up the stack.

Stack


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: Enables Display v2 Registry on non-production networks.
  • Nodes (Validators and Full nodes):
  • gRPC:
  • JSON-RPC:
  • GraphQL:
  • CLI:
  • Rust SDK:
  • Indexing Framework:

@amnn amnn self-assigned this Feb 3, 2026
@amnn amnn requested a review from mystenmark as a code owner February 3, 2026 14:59
@amnn amnn temporarily deployed to sui-typescript-aws-kms-test-env February 3, 2026 14:59 — with GitHub Actions Inactive
@vercel
Copy link
Copy Markdown

vercel bot commented Feb 3, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
sui-docs Ready Ready Preview, Comment Feb 5, 2026 1:13pm
2 Skipped Deployments
Project Deployment Actions Updated (UTC)
multisig-toolkit Ignored Ignored Preview Feb 5, 2026 1:13pm
sui-kiosk Ignored Ignored Preview Feb 5, 2026 1:13pm

Request Review

@amnn amnn mentioned this pull request Feb 3, 2026
8 tasks
@amnn amnn force-pushed the amnn/disp-enable branch from 4a48f9a to dc00abf Compare February 5, 2026 12:45
@amnn amnn temporarily deployed to sui-typescript-aws-kms-test-env February 5, 2026 12:46 — with GitHub Actions Inactive
@amnn amnn temporarily deployed to sui-typescript-aws-kms-test-env February 5, 2026 12:46 — with GitHub Actions Inactive
Base automatically changed from amnn/disp-integ to ml/display-registry February 5, 2026 13:10
@amnn amnn requested a review from a team as a code owner February 5, 2026 13:10
## Description
Enables Display Registry in Protocol Config 109, for non-production
networks. This is to unblock E2E tests in integration PRs, but should
not be landed until we are comfortable with Display Registry going out
to Devnet.

## Test plan
E2E tests further up the stack.

wip: display v2 integration
@amnn amnn force-pushed the amnn/disp-enable branch from dc00abf to f0dfa98 Compare February 5, 2026 13:12
@amnn amnn temporarily deployed to sui-typescript-aws-kms-test-env February 5, 2026 13:12 — with GitHub Actions Inactive
@amnn amnn merged commit 67c8f2e into ml/display-registry Feb 5, 2026
21 of 25 checks passed
@amnn amnn deleted the amnn/disp-enable branch February 5, 2026 13:12
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:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants