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
{{ message }}
This repository has been archived by the owner on Oct 4, 2024. It is now read-only.
Frontier Tools added an option to call JS enclave contracts like this: near call jsvm.testnet call_js_contract --accountId user.testnet --base64 --args $(node encode_call.js somejscontract.testnet some_method '
{"arg1":"aaa"}
');
This is too complex.
Simplify to ‘call_js ‘ which is the same as call_evm
My understanding is that for non enclave js contracts call should be the same as usual.
generally given we have few different kinds of enclaves now we either have a common format of a call (call_evm, call_js) or path a kind of enclave as parameter.
different parameters for better with plugin system.
The text was updated successfully, but these errors were encountered:
Describe the bug
Described in https://gov.near.org/t/engineering-weekly-update-2022-02-01/14797
Frontier Tools added an option to call JS enclave contracts like this: near call jsvm.testnet call_js_contract --accountId user.testnet --base64 --args $(node encode_call.js somejscontract.testnet some_method '
{"arg1":"aaa"}
');
This is too complex.
Simplify to ‘call_js ‘ which is the same as call_evm
My understanding is that for non enclave js contracts call should be the same as usual.
generally given we have few different kinds of enclaves now we either have a common format of a call (call_evm, call_js) or path a kind of enclave as parameter.
different parameters for better with plugin system.
The text was updated successfully, but these errors were encountered: