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 of right now those call data structures need to be constructed manually which is quite cumbersome. We need some code generation that constructs the Call enum of a runtime from metadata which can then be passed to call_runtime.
The code for this should already exist within subxt. We need to make it conveniently accessible within ink!.
call_runtime will be deprecated in favour of execute_xcm as the Call is not stable enough to use it in contracts. Hence we don't want to build more codegen around it. We rather double down on XCM.
The
call_runtime
API offered by pallet-contracts allows contracts to pass an encodedCall
to the runtime which then executes it.The API still has a few issues:
Ok
. This is a constraint in FRAME. But I think it can be changed (I am looking into this).call_runtime
in ink!, yet ( Supportcall_runtime
#1641).As of right now those call data structures need to be constructed manually which is quite cumbersome. We need some code generation that constructs the
Call
enum of a runtime from metadata which can then be passed tocall_runtime
.The code for this should already exist within
subxt
. We need to make it conveniently accessible within ink!.This is the inverse direction of #1674.
The text was updated successfully, but these errors were encountered: