Shumo Chu

One thing that nice to specify (not sure how to enforce) is the canonical serialization/deserialization of things like group element. The ultimate control is the upstream library tho.

Hi @KiChjang, Thanks for the feedback, this is really helpful. Thanks for the `XCM V3` and `Bounded Vec` suggestions. We should definitely leverage them. Here let's address the two major...

> What I would argue instead is whether you can think of a way to introduce a new XCM instruction that sidesteps this issue. Remember, _any_ XCM instruction is capable...

Since @daira's concern about the inner node empty value is not specific to this PR. Please let me know whether I should address her concern in this PR or not....

Nice! We potentially get some performance improvement here I guess.

@Dengjianping as we discussed, please add the result after removing the unnecessary deserialization.

One way to get around of this is to use https://github.com/snapview/tungstenite-rs (idea from @bhgomes)

@rphmeier sorry for lacking of context, here is the work flow (the UTXO is not very relevant here). Say a user of Acala want to privatize her `aUSD` on Manta....

@KiChjang @gavofyork one work-around that we can think of is to slicing the proofs (192 bytes) to several 32 bytes chunks and encoded in XCM multi-location. It is a kind...

> Reposting what Gav said in a channel: > > > You are misusing MultiLocation/Junction. > > > MultiLocation is a type to identify a single data-structure element held in...