Darwinia balance precise migration checklist(In case we will do it)

[hackfisher]

• Check read and mute entry points
• Ethereum bridge precision conversion

I would suggest modify the event in substrate side to avoid fork of smart contract in Ethereum side. (Anyway it will be deprecated soon, and could be batch processed in one time)

darwinia-common/frame/wormhole/backing/ethereum/src/lib.rs

Line 361 in ca11138

ring_to_lock,

https://github.com/darwinia-network/darwinia-bridge-sol/blob/b2f8940fbb1caba6ce9b38fa90d8083dfc05b060/contracts/deprecated/issuing-backing/contracts/ethereum/TokenIssuing.sol#L115

• Substrate to substrate bridge and maybe xRING contract decimal?
• subql and wormhole-backend?
• wormhole ui?
• Smart app
• Apps and Polkadot.js
• CEX?

[hackfisher]

• Staking Ledger and the other pallets which stores Balance related data.

[hackfisher]

                                        ┌────────────────────────┐
                                        │                        │
          ┌─────────────────────────────┤   CEX                  │
          │                             │                        │
          │                             │                        │
          │                             └────────────────────────┘
┌─────────▼──────────┐
│                    │
│Darwinia Precision  │
│                    │
│ 9 -> 18            │
└──────────▲─────────┘                  ┌─────────────────────────┐           ┌───────────────────────┐
           │                            │                         │           │                       │
           │                            │ Darwinia Support        │           │  BSC Message Pallet   │
           └────────────────────────────┤                         ◄───────────┤                       │
                                        │     DVM                 │           │      & Wormhole       │
                                        └─────────────────────────┘           └───────────────────────┘

I'm not convinced before we finally test the solution in Pangoro, but if we want it, we should give it a try, the order and priority should before DVM, and maybe after the Balance pallet replacement. darwinia-network/darwinia-2.0#8

[hackfisher]

https://docs.binance.org/smart-chain/developer/cross-chain-transfer.html

Like BC and BSC also have different precisions, this is also acceptable.

[hackfisher]

After considering the complexity and scope of engineering and infrastructure integration, and the engineering arrangement of tasks with higher priories, from a pragmatic point of view, I decide not to make the change finally.

The concept elaboration borrow from BC and BSC is enough for education and docs. Only Dispatch precompile which is calling from Darwinia Smart Chain to native chain(Darwinia Chain) requires attention of precision conversion.

And changing only Darwinia will cause different practice between Crab and Darwinia, which is not good for Crab in this part as canary role.