Skip to content

docs(aptos): document why framework dependency revisions are pinned#3690

Open
0xghost42 wants to merge 1 commit into
pyth-network:mainfrom
0xghost42:chore/2511-aptos-framework-rev-comment
Open

docs(aptos): document why framework dependency revisions are pinned#3690
0xghost42 wants to merge 1 commit into
pyth-network:mainfrom
0xghost42:chore/2511-aptos-framework-rev-comment

Conversation

@0xghost42
Copy link
Copy Markdown

@0xghost42 0xghost42 commented May 13, 2026

Summary

Closes #2511.

The Move.toml in target_chains/aptos/contracts/ pins AptosFramework, MoveStdlib, AptosStdlib, and AptosToken to a specific aptos-core revision that predates several recent mainnet upgrades. Without context, contributors keep proposing to bump these to "latest mainnet" — which would silently break ABI compatibility with the on-chain Wormhole package the Pyth contract depends on.

This PR adds a short comment above the [dependencies] block explaining:

  • Why the rev is locked (must match the aptos-core rev that the deployed Wormhole package was compiled against).
  • That bumping it in isolation produces bytecode that no longer links against the deployed Wormhole package.
  • That the only safe update path is a coordinated Wormhole upgrade across all supported networks.

Change

One file, six lines of comments added — no code or version changes:

  • target_chains/aptos/contracts/Move.toml

Verification

  • Comment is in a TOML [dependencies] table, parsed identically to the existing trailing [dev-addresses] comment (line 20–21).
  • No actual dependency rev changes — move build produces identical bytecode.

Out of scope

The issue also asks about updating the rev to a newer mainnet version. That's a deployment-coordination question (needs Wormhole + Pyth governance + redeploy on every chain) and well outside what an outside PR should attempt. This change just documents the lock so the question doesn't keep recurring.


Open in Devin Review

Closes pyth-network#2511.

The Move.toml in target_chains/aptos/contracts pins AptosFramework,
MoveStdlib, AptosStdlib, and AptosToken to a specific aptos-core
revision that predates several recent mainnet upgrades. Without context,
contributors keep filing issues / PRs proposing to bump these revs to
'latest mainnet' — which would silently break ABI compatibility with
the on-chain Wormhole package the Pyth contract depends on.

Add a comment above the dependencies block explaining why the rev is
locked and that it cannot be bumped in isolation from a coordinated
Wormhole upgrade on every supported network.
@vercel
Copy link
Copy Markdown

vercel Bot commented May 13, 2026

@0xghost42 is attempting to deploy a commit to the Pyth Network Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration Bot left a comment

Choose a reason for hiding this comment

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

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Open in Devin Review

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.

Update aptos-move/framework dependency and add comment for deployment revision

1 participant