Aidan Musnitzky
Aidan Musnitzky
Hmm I suppose if I extend the ParseUser class, and still call it a ParseUser under my own namespace it should work fine? Should this 'constraint' be fixed or else...
regarding adding additional attributes, related to #50
@philipstanislaus we still want it in, but it's low prio until we're 100% done with the new interfaces for incentivized channel and full grandpa light client relayersmart contract stuff
looks good, agree with @vgeddes 's comments. @wildmolasses also once this is all merged in it would be great to have a doc/diagram covering an explanation of all the points...
looks good! @vgeddes plz review too, thanks!
This is great thanks! We're definitely in agreement for Option 3 and that's our next most important step to make! In addition, we're also speccing out something like Option 2...
@rakanalh i think we may want both. for a true low level call, as vincent's been looking into, the dispatch pallet or some new pallet will send the xcm. for...
Thanks! We're actually busy looking at fee structures for XCM at the moment - @vgeddes will you look into this/incorporate it into our XCM fee plans
@hujw77 Taking another quick look - Using a multiproof instead of an array of individual proofs looks like a great idea and optimization! We'll need to build the proof creation...