-
Notifications
You must be signed in to change notification settings - Fork 24
Open
Description
Description
Research and document how XCM (Cross-Consensus Message Format) handles account IDs during token transfers, with specific focus on how this will impact Ethereum-compatible keys and addresses.
Tasks
- Analyze current XCM implementation for account ID handling
- Document how account IDs are mapped during token transfers
- Identify potential issues when using Ethereum-compatible addresses
- Research solutions implemented by other projects
- Propose modifications needed for our XCM implementation
Acceptance Criteria
- Technical document explaining XCM account ID mapping
- Analysis of potential issues with Ethereum-compatible addresses
- Comparison of solutions from other projects
- Proposed approach for our system with pros and cons
- Identified changes needed in our XCM implementation
Engineering Notes
- We would need to ensure that mapped accountID would work as expected when used with XCM through the path that they took from contract -> pallet -> Relay-Chain -> Asset-hub -> SnowBridge and the other way around when getting an XCM message.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels