From 25c52c5bd7c7f86b5b04ef317b8b92f309e5fe16 Mon Sep 17 00:00:00 2001 From: primata Date: Tue, 7 Jan 2025 16:45:46 -0300 Subject: [PATCH 01/10] features MD --- MD/md-75/README.md | 119 +++++++++++++++++++++++++++++++++++++++++++ MIP/mip-75/README.md | 60 ++++++++++++++++++++++ 2 files changed, 179 insertions(+) create mode 100644 MD/md-75/README.md create mode 100644 MIP/mip-75/README.md diff --git a/MD/md-75/README.md b/MD/md-75/README.md new file mode 100644 index 00000000..8c1fe29d --- /dev/null +++ b/MD/md-75/README.md @@ -0,0 +1,119 @@ +# MD-15: Movement Mainnet Feature Flags + +- **Description**: Define and manage feature flags for the Movement mainnet to optimize the network's launch with community-driven and developer-focused features. +- **Authors**: [Liam Monninger](mailto\:liam@movementlabs.xyz) +- **Reviewer**: Andreas Penzkofer + +## Overview + +To ensure the Movement mainnet launches with a robust feature set that meets the expectations of the community and developers, we propose introducing a feature flag system. This system will allow Movement Labs to toggle specific features, many of which are familiar to users from the testnet or analogous to features in Aptos. This document establishes the framework for defining, managing, and evolving these feature flags. + +## Desiderata + +### D1: Enable Fungible Asset as Gas Token + +**User Journey**: MOVE coin can be used as both a fungible asset and the native gas token for transactions on the Movement mainnet. + +**Justification**: This feature aligns with the community’s preference and facilitates interoperability and ease of use. This way we also do not need to go through the migration process. Aptos Mainnet has already gone through governance process to enable this feature with [AIP-70](https://governance.aptosfoundation.org/proposal/107), [AIP-85](https://github.com/aptos-foundation/AIPs/blob/main/aips/aip-85.md) and merged [gas charging](https://github.com/aptos-labs/aptos-core/pull/13194). + +**Recommendations**: + +- Implement MOVE as a [Fungible Asset](https://github.com/aptos-labs/aptos-core/blob/main/aptos-move/framework/aptos-framework/sources/fungible_asset.move). +- Configure MOVE to serve as the native gas token to streamline user interactions. +- Features 61, 64,65 and 68 should be toggled true. + +### D2: Remove Token Authorization Requirement + +**User Journey**: Users can send tokens to any account without requiring prior authorization. + +**Justification**: Simplifying token transfers encourages user adoption and aligns with community feedback. + +**Recommendations**: + +- Ensure tokens can be sent to accounts by default, without requiring explicit authorization. +- Implement this as a default setting for all accounts upon creation. + +### D3: Turn on Binary Format V7 + +**User Journey**: Users can use the latest Binary Format used in Aptos. + +**Justification**: Compatibility with Aptos deployments. + +**Recommendations**: + +- Feature 40 should be toggled true. + +## Feature Flags + +Below is the table of features for Aptos mainnet, testnet, devnet, and their comparison with Movement. + +| Feature\_ID | Feature\_Name | Mainnet\_Status | Testnet\_Status | Devnet\_Status | Movement\_Status | Consider\_Toggling | +| ----------- | ------------------------------------------------------- | --------------- | --------------- | -------------- | ---------------- | ---------------- | +| 1 | CODE\_DEPENDENCY\_CHECK | True | True | True | True | False | +| 2 | TREAT\_FRIEND\_AS\_PRIVATE | True | True | True | True | False | +| 3 | SHA\_512\_AND\_RIPEMD\_160\_NATIVES | True | True | True | True | False | +| 4 | APTOS\_STD\_CHAIN\_ID\_NATIVES | False | False | True | True | False | +| 5 | VM\_BINARY\_FORMAT\_V6 | True | True | True | True | False | +| 6 | COLLECT\_AND\_DISTRIBUTE\_GAS\_FEES | False | False | False | False | False | +| 7 | MULTI\_ED25519\_PK\_VALIDATE\_V2\_NATIVES | True | True | True | True | False | +| 8 | BLAKE2B\_256\_NATIVE | True | True | True | True | False | +| 9 | RESOURCE\_GROUPS | True | True | True | True | False | +| 10 | MULTISIG\_ACCOUNTS | True | True | True | True | False | +| 11 | DELEGATION\_POOLS | True | True | True | True | False | +| 12 | CRYPTOGRAPHY\_ALGEBRA\_NATIVES | True | True | True | True | False | +| 13 | BLS12\_381\_STRUCTURES | True | True | True | True | False | +| 14 | ED25519\_PUBKEY\_VALIDATE\_RETURN\_FALSE\_WRONG\_LENGTH | True | True | True | True | False | +| 15 | STRUCT\_CONSTRUCTORS | True | True | True | True | False | +| 16 | PERIODICAL\_REWARD\_RATE\_DECREASE | True | True | False | False | False | +| 17 | PARTIAL\_GOVERNANCE\_VOTING | True | True | False | False | False | +| 20 | CHARGE\_INVARIANT\_VIOLATION | True | True | True | True | False | +| 21 | DELEGATION\_POOL\_PARTIAL\_GOVERNANCE\_VOTING | True | True | False | False | False | +| 22 | FEE\_PAYER\_ENABLED | True | True | True | True | False | +| 23 | APTOS\_UNIQUE\_IDENTIFIERS | True | True | True | True | False | +| 24 | BULLETPROOFS\_NATIVES | True | True | True | True | False | +| 25 | SIGNER\_NATIVE\_FORMAT\_FIX | True | True | True | True | False | +| 26 | MODULE\_EVENT | True | True | True | True | False | +| 29 | SIGNATURE\_CHECKER\_V2\_SCRIPT\_FIX | True | True | True | True | False | +| 31 | SAFER\_RESOURCE\_GROUPS | True | True | True | True | False | +| 32 | SAFER\_METADATA | True | True | True | True | False | +| 33 | SINGLE\_SENDER\_AUTHENTICATOR | True | True | True | True | False | +| 34 | SPONSORED\_AUTOMATIC\_ACCOUNT\_CREATION | True | True | True | True | False | +| 35 | FEE\_PAYER\_ACCOUNT\_OPTIONAL | True | True | True | True | False | +| 38 | LIMIT\_MAX\_IDENTIFIER\_LENGTH | True | True | True | True | False | +| 39 | OPERATOR\_BENEFICIARY\_CHANGE | True | True | True | True | False | +| 40 | VM\_BINARY\_FORMAT\_V7 | True | True | True | False | True | +| 41 | RESOURCE\_GROUPS\_SPLIT\_IN\_VM\_CHANGE\_SET | True | True | True | True | False | +| 42 | COMMISSION\_CHANGE\_DELEGATION\_POOL | True | True | True | True | False | +| 43 | BN254\_STRUCTURES | True | True | True | True | False | +| 45 | RECONFIGURE\_WITH\_DKG | False | False | False | False | False | +| 46 | KEYLESS\_ACCOUNTS | True | True | True | True | False | +| 47 | KEYLESS\_BUT\_ZKLESS\_ACCOUNTS | False | False | True | True | False | +| 49 | JWK\_CONSENSUS | True | True | True | True | False | +| 50 | CONCURRENT\_FUNGIBLE\_ASSETS | True | True | True | True | False | +| 52 | OBJECT\_CODE\_DEPLOYMENT | True | True | True | True | False | +| 53 | MAX\_OBJECT\_NESTING\_CHECK | True | True | True | True | False | +| 54 | KEYLESS\_ACCOUNTS\_WITH\_PASSKEYS | False | False | True | True | False | +| 55 | MULTISIG\_V2\_ENHANCEMENT | True | True | True | True | False | +| 56 | DELEGATION\_POOL\_ALLOWLISTING | True | True | True | True | False | +| 57 | MODULE\_EVENT\_MIGRATION | False | False | True | True | False | +| 59 | TRANSACTION\_CONTEXT\_EXTENSION | True | True | True | True | False | +| 60 | COIN\_TO\_FUNGIBLE\_ASSET\_MIGRATION | True | True | True | True | False | +| 61 | PRIMARY\_APT\_FUNGIBLE\_STORE\_AT\_USER\_ADDRESS | False | False | False | False | True | +| 62 | OBJECT\_NATIVE\_DERIVED\_ADDRESS | True | True | True | True | False | +| 63 | DISPATCHABLE\_FUNGIBLE\_ASSET | True | True | True | True | False | +| 64 | NEW\_ACCOUNTS\_DEFAULT\_TO\_FA\_APT\_STORE | False | False | False | False | True | +| 65 | OPERATIONS\_DEFAULT\_TO\_FA\_APT\_STORE | False | False | False | False | True | +| 66 | AGGREGATOR\_V2\_IS\_AT\_LEAST\_API | True | True | True | True | False | +| 67 | CONCURRENT\_FUNGIBLE\_BALANCE | True | True | True | True | False | +| 68 | DEFAULT\_TO\_CONCURRENT\_FUNGIBLE\_BALANCE | False | False | False | False | True | +| 70 | ABORT\_IF\_MULTISIG\_PAYLOAD\_MISMATCH | True | True | True | True | False | +| 71 | ?/NATIVE\_BRIDGE | True | True | True | False | False | +| 78 | TRANSACTION\_SIMULATION\_ENHANCEMENT | True | True | True | null | False | +| 79 | COLLECTION\_OWNER | True | True | True | null | False | +| 80 | NATIVE\_MEMORY\_OPERATIONS | True | True | True | null | False | + +## Errata + +**Transparency and Clarity**: Any corrections or updates to this document will be tracked and published here to ensure accuracy. + +**Accountability**: Updates will include a reference to the date and version in which the error was identified and corrected. \ No newline at end of file diff --git a/MIP/mip-75/README.md b/MIP/mip-75/README.md new file mode 100644 index 00000000..61f81a6c --- /dev/null +++ b/MIP/mip-75/README.md @@ -0,0 +1,60 @@ +# MIP-0: MIPs +- **Description**: Movement Improvement Proposals standardize and formalize specifications for Movement technologies. +- **Authors**: [Liam Monninger](mailto:liam@movementlabs.xyz) +- **Desiderata**: [MD-0](../MD/md-0) + +## Abstract + +Movement Improvement Proposals (MIPs) serve as a mechanism to propose, discuss, and adopt changes or enhancements to Movement technologies. By providing a standardized and formalized structure for these proposals, MIPs ensure that proposed improvements are well-defined, transparent, and accessible to the wider community. + +## Motivation + +Movement technologies continually evolve, and there's a need to ensure that the process of proposing and adopting changes is both organized and standardized. By establishing MIPs, we aim to facilitate the introduction of new features or improvements, making sure they are well-vetted, discussed, and documented. This ensures the integrity of Movement technologies, making it easier for third parties to adopt and adapt to these changes. + +## Specification + +A Movement Improvement Proposal (MIP) is a design document that provides information to the Movement community, describing a new feature or improvement for Movement technologies. + +- **Structure**: Each MIP must adhere to the given template, which requires details like title, description, author, status, and more. A MIP also includes sections like Abstract, Motivation, Specification, Reference Implementation, Verification, Errata, and Appendix. + + - An md-template is provided in the [MIP Repository](https://github.com/movemntdev/MIP) which further specifies this structure. This MIP is an example of said structure. + +- **Lifecycle**: An MIP starts as a draft, after which it undergoes discussions and revisions. Once agreed upon, it moves to a 'published' status. An MIP can also be deprecated if it becomes obsolete. + +- **Storage**: MIPs should be stored in the MIPs directory at [MIP Repository](https://github.com/movemntdev/MIP). + +- **Definitions** : Provide definitions that you think will empower the reader to quickly dive into the topic. + +## Reference Implementation + +A reference implementation or a sample MIP following the MIP template can be provided to guide potential proposers. This MIP (MIP-0) serves as a practical example, aiding in understanding the format and expectations. + +## Verification + +1. **Correctness**: Each MIP must convincingly demonstrate its correctness. + +This MIP is correct insofar as it uses a structure established by Ethereum for Improvement Proposals which has hitherto been successful. + +2. **Security Implications**: Each MIP should be evaluated for any potential security risks it might introduce to Movement technologies. + +The primary security concern associated with this MIP is the exposure of proprietary technologies or information via the ill-advised formation of an MIP which the MIP process might encourage. + +3. **Performance Impacts**: The implications of the proposal on system performance should be analyzed. + +The primary performance concern associated with this MIP is its potential for overuse. Only specifications that are non-trivial and very high-quality should be composed as MIPs. + +4. **Validation Procedures**: To the extent possible, formal, analytical, or machined-aided validation of the above should be pursued. + +I'm using spellcheck while writing this MIP. You can verify that I am using valid grammar by pasting this sentence into Google Docs. + +5. **Peer Review and Community Feedback**: A section should be included that captures significant feedback from the community, which may influence the final specifications of the MIP. + +The Movement Labs team is currently reviewing and assessing this process. + +## Errata + +Post-publication corrections, if any, to the MIPs should be documented in this section. This ensures transparency and provides readers with accurate and up-to-date information. + +## Appendix + +The Appendix should contain references and notes related to the MIP. Materials referenced in the MIP should be marked with specific labels (e.g., ⟨R1⟩) for easy tracking and understanding. From 5bdf640393de28ef3508217c411a103f334ef641 Mon Sep 17 00:00:00 2001 From: primata Date: Tue, 7 Jan 2025 16:46:25 -0300 Subject: [PATCH 02/10] remove mip-75 text --- MIP/mip-75/README.md | 60 -------------------------------------------- 1 file changed, 60 deletions(-) diff --git a/MIP/mip-75/README.md b/MIP/mip-75/README.md index 61f81a6c..e69de29b 100644 --- a/MIP/mip-75/README.md +++ b/MIP/mip-75/README.md @@ -1,60 +0,0 @@ -# MIP-0: MIPs -- **Description**: Movement Improvement Proposals standardize and formalize specifications for Movement technologies. -- **Authors**: [Liam Monninger](mailto:liam@movementlabs.xyz) -- **Desiderata**: [MD-0](../MD/md-0) - -## Abstract - -Movement Improvement Proposals (MIPs) serve as a mechanism to propose, discuss, and adopt changes or enhancements to Movement technologies. By providing a standardized and formalized structure for these proposals, MIPs ensure that proposed improvements are well-defined, transparent, and accessible to the wider community. - -## Motivation - -Movement technologies continually evolve, and there's a need to ensure that the process of proposing and adopting changes is both organized and standardized. By establishing MIPs, we aim to facilitate the introduction of new features or improvements, making sure they are well-vetted, discussed, and documented. This ensures the integrity of Movement technologies, making it easier for third parties to adopt and adapt to these changes. - -## Specification - -A Movement Improvement Proposal (MIP) is a design document that provides information to the Movement community, describing a new feature or improvement for Movement technologies. - -- **Structure**: Each MIP must adhere to the given template, which requires details like title, description, author, status, and more. A MIP also includes sections like Abstract, Motivation, Specification, Reference Implementation, Verification, Errata, and Appendix. - - - An md-template is provided in the [MIP Repository](https://github.com/movemntdev/MIP) which further specifies this structure. This MIP is an example of said structure. - -- **Lifecycle**: An MIP starts as a draft, after which it undergoes discussions and revisions. Once agreed upon, it moves to a 'published' status. An MIP can also be deprecated if it becomes obsolete. - -- **Storage**: MIPs should be stored in the MIPs directory at [MIP Repository](https://github.com/movemntdev/MIP). - -- **Definitions** : Provide definitions that you think will empower the reader to quickly dive into the topic. - -## Reference Implementation - -A reference implementation or a sample MIP following the MIP template can be provided to guide potential proposers. This MIP (MIP-0) serves as a practical example, aiding in understanding the format and expectations. - -## Verification - -1. **Correctness**: Each MIP must convincingly demonstrate its correctness. - -This MIP is correct insofar as it uses a structure established by Ethereum for Improvement Proposals which has hitherto been successful. - -2. **Security Implications**: Each MIP should be evaluated for any potential security risks it might introduce to Movement technologies. - -The primary security concern associated with this MIP is the exposure of proprietary technologies or information via the ill-advised formation of an MIP which the MIP process might encourage. - -3. **Performance Impacts**: The implications of the proposal on system performance should be analyzed. - -The primary performance concern associated with this MIP is its potential for overuse. Only specifications that are non-trivial and very high-quality should be composed as MIPs. - -4. **Validation Procedures**: To the extent possible, formal, analytical, or machined-aided validation of the above should be pursued. - -I'm using spellcheck while writing this MIP. You can verify that I am using valid grammar by pasting this sentence into Google Docs. - -5. **Peer Review and Community Feedback**: A section should be included that captures significant feedback from the community, which may influence the final specifications of the MIP. - -The Movement Labs team is currently reviewing and assessing this process. - -## Errata - -Post-publication corrections, if any, to the MIPs should be documented in this section. This ensures transparency and provides readers with accurate and up-to-date information. - -## Appendix - -The Appendix should contain references and notes related to the MIP. Materials referenced in the MIP should be marked with specific labels (e.g., ⟨R1⟩) for easy tracking and understanding. From 5e6e7678113351a1bb055015fbf75db5a7ebcfd2 Mon Sep 17 00:00:00 2001 From: primata Date: Tue, 7 Jan 2025 16:49:17 -0300 Subject: [PATCH 03/10] native bridge --- MD/md-75/README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/MD/md-75/README.md b/MD/md-75/README.md index 8c1fe29d..c11e379e 100644 --- a/MD/md-75/README.md +++ b/MD/md-75/README.md @@ -107,7 +107,8 @@ Below is the table of features for Aptos mainnet, testnet, devnet, and their com | 67 | CONCURRENT\_FUNGIBLE\_BALANCE | True | True | True | True | False | | 68 | DEFAULT\_TO\_CONCURRENT\_FUNGIBLE\_BALANCE | False | False | False | False | True | | 70 | ABORT\_IF\_MULTISIG\_PAYLOAD\_MISMATCH | True | True | True | True | False | -| 71 | ?/NATIVE\_BRIDGE | True | True | True | False | False | +| 71 | ? | True | True | True | False | False | +| 72 | NATIVE\_BRIDGE | True | True | True | False | False | | 78 | TRANSACTION\_SIMULATION\_ENHANCEMENT | True | True | True | null | False | | 79 | COLLECTION\_OWNER | True | True | True | null | False | | 80 | NATIVE\_MEMORY\_OPERATIONS | True | True | True | null | False | From ea38ba3c30f68324663f563ebaf005a6559eb79f Mon Sep 17 00:00:00 2001 From: primata Date: Tue, 7 Jan 2025 16:52:36 -0300 Subject: [PATCH 04/10] change to primata --- MD/md-75/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/MD/md-75/README.md b/MD/md-75/README.md index c11e379e..340e95a4 100644 --- a/MD/md-75/README.md +++ b/MD/md-75/README.md @@ -1,8 +1,8 @@ # MD-15: Movement Mainnet Feature Flags - **Description**: Define and manage feature flags for the Movement mainnet to optimize the network's launch with community-driven and developer-focused features. -- **Authors**: [Liam Monninger](mailto\:liam@movementlabs.xyz) -- **Reviewer**: Andreas Penzkofer +- **Authors**: [Primata](mailto:primata@movementlabs.xyz) +- **Reviewer**: ## Overview From fb9fef67a15c7316081df7590a530d65e90d3a09 Mon Sep 17 00:00:00 2001 From: primata Date: Tue, 7 Jan 2025 16:54:32 -0300 Subject: [PATCH 05/10] bump id to 81 --- MD/{md-75 => md-81}/README.md | 2 +- MIP/{mip-75 => mip-81}/README.md | 0 2 files changed, 1 insertion(+), 1 deletion(-) rename MD/{md-75 => md-81}/README.md (99%) rename MIP/{mip-75 => mip-81}/README.md (100%) diff --git a/MD/md-75/README.md b/MD/md-81/README.md similarity index 99% rename from MD/md-75/README.md rename to MD/md-81/README.md index 340e95a4..51bdebd5 100644 --- a/MD/md-75/README.md +++ b/MD/md-81/README.md @@ -1,4 +1,4 @@ -# MD-15: Movement Mainnet Feature Flags +# MD-81: Movement Mainnet Feature Flags - **Description**: Define and manage feature flags for the Movement mainnet to optimize the network's launch with community-driven and developer-focused features. - **Authors**: [Primata](mailto:primata@movementlabs.xyz) diff --git a/MIP/mip-75/README.md b/MIP/mip-81/README.md similarity index 100% rename from MIP/mip-75/README.md rename to MIP/mip-81/README.md From 3ff7a02f70e580e3a729a1bb542c82ab2d3c0a94 Mon Sep 17 00:00:00 2001 From: apenzk Date: Tue, 7 Jan 2025 21:19:27 +0100 Subject: [PATCH 06/10] add codeowner --- .github/CODEOWNERS | 2 ++ MD/md-81/README.md | 1 - 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS index 505f0263..ad71cf09 100644 --- a/.github/CODEOWNERS +++ b/.github/CODEOWNERS @@ -16,3 +16,5 @@ /MD/md-15/ @l-monninger @apenzk /MIP/mip-39/ @franck44 /MIP/mip-53/ @l-monninger +/MD/md-81/ @primata +/MIP/mip-81/ @primata diff --git a/MD/md-81/README.md b/MD/md-81/README.md index 51bdebd5..6d5a3330 100644 --- a/MD/md-81/README.md +++ b/MD/md-81/README.md @@ -2,7 +2,6 @@ - **Description**: Define and manage feature flags for the Movement mainnet to optimize the network's launch with community-driven and developer-focused features. - **Authors**: [Primata](mailto:primata@movementlabs.xyz) -- **Reviewer**: ## Overview From a769052adbfdcac18489148f99295857bb81940a Mon Sep 17 00:00:00 2001 From: primata Date: Tue, 7 Jan 2025 20:38:20 -0300 Subject: [PATCH 07/10] change logs --- MD/md-81/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MD/md-81/README.md b/MD/md-81/README.md index 6d5a3330..8faa5895 100644 --- a/MD/md-81/README.md +++ b/MD/md-81/README.md @@ -112,7 +112,7 @@ Below is the table of features for Aptos mainnet, testnet, devnet, and their com | 79 | COLLECTION\_OWNER | True | True | True | null | False | | 80 | NATIVE\_MEMORY\_OPERATIONS | True | True | True | null | False | -## Errata +## Change Logs **Transparency and Clarity**: Any corrections or updates to this document will be tracked and published here to ensure accuracy. From c0aaf819e22197b21251976999d7744e614063c5 Mon Sep 17 00:00:00 2001 From: apenzk Date: Tue, 28 Jan 2025 14:55:37 +0100 Subject: [PATCH 08/10] delete file and udpate codeowners --- .github/CODEOWNERS | 5 ----- MIP/mip-81/README.md | 0 2 files changed, 5 deletions(-) delete mode 100644 MIP/mip-81/README.md diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS index ad71cf09..b43b09bd 100644 --- a/.github/CODEOWNERS +++ b/.github/CODEOWNERS @@ -1,20 +1,15 @@ # Reviewers that should be generally notified. * @l-monninger -* @andyjsbell * @apenzk # Authors and reviewers that should be added for specific files /MIP/mip-0/ @l-monninger @apenzk /MD/md-0/ @l-monninger @apenzk /MG/mg-0/ @l-monninger @apenzk - /MIP/mip1/ @l-monninger - /MD/md-3/ @l-monninger - /MIP/mip-15/ @l-monninger @apenzk /MD/md-15/ @l-monninger @apenzk /MIP/mip-39/ @franck44 /MIP/mip-53/ @l-monninger /MD/md-81/ @primata -/MIP/mip-81/ @primata diff --git a/MIP/mip-81/README.md b/MIP/mip-81/README.md deleted file mode 100644 index e69de29b..00000000 From 68a8cfe2d18dfa002d9a55874be7304504de20ae Mon Sep 17 00:00:00 2001 From: apenzk Date: Thu, 20 Feb 2025 09:23:24 +0100 Subject: [PATCH 09/10] edits --- .vscode/spellright.dict | 3 +++ MD/md-81/README.md | 6 +----- 2 files changed, 4 insertions(+), 5 deletions(-) diff --git a/.vscode/spellright.dict b/.vscode/spellright.dict index e791c9ca..882ebeff 100644 --- a/.vscode/spellright.dict +++ b/.vscode/spellright.dict @@ -1,7 +1,10 @@ Aptos Changelog +devnet Fastconfirmation +mainnet multisig +testnet timelock timelocks trustlessness diff --git a/MD/md-81/README.md b/MD/md-81/README.md index 8faa5895..216373e8 100644 --- a/MD/md-81/README.md +++ b/MD/md-81/README.md @@ -1,4 +1,4 @@ -# MD-81: Movement Mainnet Feature Flags +# MD-81: Movement Mainnet feature flags - **Description**: Define and manage feature flags for the Movement mainnet to optimize the network's launch with community-driven and developer-focused features. - **Authors**: [Primata](mailto:primata@movementlabs.xyz) @@ -113,7 +113,3 @@ Below is the table of features for Aptos mainnet, testnet, devnet, and their com | 80 | NATIVE\_MEMORY\_OPERATIONS | True | True | True | null | False | ## Change Logs - -**Transparency and Clarity**: Any corrections or updates to this document will be tracked and published here to ensure accuracy. - -**Accountability**: Updates will include a reference to the date and version in which the error was identified and corrected. \ No newline at end of file From a50bfe937b9d6976cd22363f913444b5df2c6bfc Mon Sep 17 00:00:00 2001 From: primata Date: Thu, 20 Feb 2025 17:18:15 +0800 Subject: [PATCH 10/10] alter bridges features --- MD/md-81/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/MD/md-81/README.md b/MD/md-81/README.md index 8faa5895..9897adba 100644 --- a/MD/md-81/README.md +++ b/MD/md-81/README.md @@ -106,8 +106,8 @@ Below is the table of features for Aptos mainnet, testnet, devnet, and their com | 67 | CONCURRENT\_FUNGIBLE\_BALANCE | True | True | True | True | False | | 68 | DEFAULT\_TO\_CONCURRENT\_FUNGIBLE\_BALANCE | False | False | False | False | True | | 70 | ABORT\_IF\_MULTISIG\_PAYLOAD\_MISMATCH | True | True | True | True | False | -| 71 | ? | True | True | True | False | False | -| 72 | NATIVE\_BRIDGE | True | True | True | False | False | +| 71 | NATIVE\_BRIDGE | True | True | True | False | False | +| 72 | ATOMIC\_BRIDGE | True | True | True | False | False | | 78 | TRANSACTION\_SIMULATION\_ENHANCEMENT | True | True | True | null | False | | 79 | COLLECTION\_OWNER | True | True | True | null | False | | 80 | NATIVE\_MEMORY\_OPERATIONS | True | True | True | null | False | @@ -116,4 +116,4 @@ Below is the table of features for Aptos mainnet, testnet, devnet, and their com **Transparency and Clarity**: Any corrections or updates to this document will be tracked and published here to ensure accuracy. -**Accountability**: Updates will include a reference to the date and version in which the error was identified and corrected. \ No newline at end of file +**Accountability**: Updates will include a reference to the date and version in which the error was identified and corrected.