Governance · Movement Labs
Movement Improvement Proposals
The specification track, where the bridge design, the upgradeability model and the feature-flag policy were argued out before any of them shipped.
- Period
- 2024 - 2026
- Role
- Author and reviewer
- PRs authored
- 12
- Source
- Public
The problem
A protocol decision that only exists in code is hard to review and harder to revisit. Nobody outside the pull request sees the alternatives that were weighed, and a year later the reasoning is gone even though the code is still there. The bridge redesign, the upgradeability model and the fee structure all needed somewhere people could disagree with them before they shipped.
What I did
- MIP-58, lock/mint bridge design. MD-21, native bridge with attesters.
- MIP-18, stage-0 upgradeability and multisigs. MIP-27, contract deployment pipeline.
- MD-14, a more secure timelock for the bridge. MD-17, bridge fees.
- MD-30, Movement Name Service. MD-81, mainnet feature flags.
- Also authored the original Move Name Service and external documentation RFCs.
Stack
SpecificationProtocol designMove