You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed offline with @PierreOssun , using MultiAddress type for ink! contract address is mainly because of dispatch-able calls in the previous pallet-xvm impl. And as we won't add dispatch-able calls to refreshed pallet-xvm design, there is no need the wrap the AccountId type ink! contract address in MultiAddress.
The text was updated successfully, but these errors were encountered:
And update tests.
Context
As discussed offline with @PierreOssun , using
MultiAddress
type for ink! contract address is mainly because of dispatch-able calls in the previouspallet-xvm
impl. And as we won't add dispatch-able calls to refreshedpallet-xvm
design, there is no need the wrap theAccountId
type ink! contract address inMultiAddress
.The text was updated successfully, but these errors were encountered: