margin v5: register mainnet package 0x124bb3d8#1018
Merged
Conversation
- Indexer: backfill v4 (0x7767…5a98) which was never added, and append v5 (0x124b…cff2e) as the new Latest in MAINNET_MARGIN_PACKAGES. - Published.toml mainnet: bump published-at to v5 and version = 5. - adminInjectCapital.ts: point MARGIN_PACKAGE at v5. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
0xaslan
approved these changes
May 19, 2026
pei-mysten
approved these changes
May 19, 2026
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
3 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.
Summary
0x124bb3d8105d6d301c0d40feaa54d65df6b301e4d8ddd5eb8475b0f8a18cff2etoMAINNET_MARGIN_PACKAGESas the new Latest.0x7767428727629a08dfd196bd4fc00d8a060e30da33aa63f4087fb3271e615a98) which was missed when it was published — without it, the indexer would not recognize v4 events.packages/deepbook_margin/Published.tomlmainnet topublished-at = v5,version = 5so future upgrades resolve from v5.scripts/transactions/adminInjectCapital.tsMARGIN_PACKAGEat v5.Key decisions
MAINNET_MARGIN_PACKAGESrather than replacing them. The indexer matches any of them, and existing manager objects on v3/v4 still need their wind-down (repay/withdraw/reduce-only) events captured per theMARGIN_VERSIONbump in434a5085a.original-idandupgrade-capabilityinPublished.tomlare unchanged (upgrade cap is an owned object, not regenerated per upgrade).Test plan
cargo fmt -p deepbook-indexercargo build -p deepbook-indexersui move buildinpackages/deepbook_margin