Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[shared-object-deletion] Turn on shared object deletion in mainnet #16008

Merged
merged 1 commit into from
Jan 31, 2024

Conversation

tzakian
Copy link
Contributor

@tzakian tzakian commented Jan 30, 2024

Description

Turn on shared object deletion in mainnet. This is a flag-only PR (+ updates) that adds a new protocol version (version 36).

Test Plan

Existing tests + has been running in devnet/testnet for the past couple months.


If your changes are not user-facing and do not break anything, you can skip the following section. Otherwise, please briefly describe what has changed under the Release Notes section.

Type of Change (Check all that apply)

  • protocol change
  • user-visible impact
  • breaking change for a client SDKs
  • breaking change for FNs (FN binary must upgrade)
  • breaking change for validators or node operators (must upgrade binaries)
  • breaking change for on-chain data layout
  • necessitate either a data wipe or data migration

Release notes

Enable shared object deletion in mainnet.

Copy link

vercel bot commented Jan 30, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
mysten-ui ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 31, 2024 5:09pm
sui-core ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 31, 2024 5:09pm
sui-typescript-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 31, 2024 5:09pm
3 Ignored Deployments
Name Status Preview Comments Updated (UTC)
explorer ⬜️ Ignored (Inspect) Visit Preview Jan 31, 2024 5:09pm
multisig-toolkit ⬜️ Ignored (Inspect) Visit Preview Jan 31, 2024 5:09pm
sui-kiosk ⬜️ Ignored (Inspect) Visit Preview Jan 31, 2024 5:09pm

Copy link
Contributor

@lavindir lavindir left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

really excited to see this go out :)

"sequenceNumber": 0
},
"last": {
"digest": "4KMiBygiY5pNj53QJKDmHGkcXywEUrEwg85KRQFjAhty",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

curious why all these values changed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They just generally have shifted every time there is a new protocol version. So my understanding is there's some deterministic state (e.g., genesis) that changes with the new protocol version (similar to the configs that also need to be updated with new values after a protocol version bump).

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.

None yet

2 participants