Implement account aliases feature

[aschran]

Description

This feature allows users to modify the set of signers that are allowed to act as a given sender. It depends on the addition of Mysticeti fast path, and the removal of fast pay.

• Adds API to configure aliases in Move framework.
• Updates signature verification flows to use aliases.
• Adds a new version of CheckpointContents that records the version of aliases used to verify signatures for each transaction.

Test plan

Todo: add a test that forces out-of-order aliases using soft bundles.

---

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.

• [x] Protocol: Adds account aliases feature.
• [ ] Nodes (Validators and Full nodes):
• [ ] gRPC:
• [ ] JSON-RPC:
• [ ] GraphQL:
• [ ] CLI:
• [ ] Rust SDK:

[vercel[bot]]

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

Project	Deployment	Preview	Comments	Updated (UTC)
sui-docs	Ready	Preview	Comment	Dec 6, 2025 0:11am

2 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
multisig-toolkit	Ignored	Preview		Dec 6, 2025 0:11am
sui-kiosk	Ignored	Preview		Dec 6, 2025 0:11am

[lxfind]

It depends on the the removal of fast pay.

This seems very far fetched?

[aschran]

It depends on the the removal of fast pay.

This seems very far fetched?

Does it? Note "fast pay", not "fast path"

Edit to add: I am using "fast pay" to refer to the existing protocol involving two-step calls to handle_transaction followed by handle_certificate