Open
Conversation
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
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.
Add Movement namespace
This PR introduces the Movement namespace to the ChainAgnostic namespaces registry.
Added Files
movement/README.md- Namespace profile for Movement Networkmovement/caip2.md- CAIP-2 chain identification specification for Movementmovement/caip10.md- CAIP-10 account identification specification for MovementSummary
Movement is a Layer 2 network built on Move, featuring parallel execution for high throughput. This PR establishes the
movementnamespace for identifying Movement-based chains and accounts.Chain Identification (CAIP-2)
Chains in the Movement namespace are identified by their numeric
chain_id, which is assigned at genesis and requires no transformation to be used as a CAIP-2 reference.movement:126movement:250Account Identification (CAIP-10)
Movement accounts are identified by 32-byte hexadecimal addresses with a
0xprefix. Account identifiers follow the formatmovement:<chain_id>:<address>.Example:
movement:126:0xd5fb7899ac1e3b4a51bfbf0dcafaa78453bb8e9a64a93a8e47fedad6b8c48171Resolution
Chain IDs can be resolved by querying the REST API of any Movement fullnode:
The
chain_idfield in the response provides the identifier.Account existence can be verified via:
References