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
This quickly presents my current understanding of the dependencies (aka architecture) of a SC (implemented in AS with hand written bindings) and how the architecture would be transformed to support wit interface/bindings.
calls from smart contracts to Massa ABI (function in abi.rs inside massa-sc-runtime repos)
calls between smart contracts
Smart Contract "wit based" means: a SC compiled into wasm and written in any language that is supported by wai-bindgen (https://github.com/wasmerio/wai). massa-wit-sdk: is a generic term that correspond to the bindings generated by wai-bindgen for the chosen language (provided it is in the supported list ^^).
So one can see this as*:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
This quickly presents my current understanding of the dependencies (aka architecture) of a SC (implemented in AS with hand written bindings) and how the architecture would be transformed to support wit interface/bindings.
Current architecture
New architecture
"extern calls" include:
Smart Contract "wit based" means: a SC compiled into
wasm
and written in any language that is supported bywai-bindgen
(https://github.com/wasmerio/wai).massa-wit-sdk: is a generic term that correspond to the bindings generated by
wai-bindgen
for the chosen language (provided it is in the supported list ^^).So one can see this as*:
*: check compatibility list
Beta Was this translation helpful? Give feedback.
All reactions