Skip to content
This repository has been archived by the owner on Oct 4, 2024. It is now read-only.

The format for calling js contracts should be simplified #930

Open
ilblackdragon opened this issue Feb 9, 2022 · 0 comments
Open

The format for calling js contracts should be simplified #930

ilblackdragon opened this issue Feb 9, 2022 · 0 comments
Labels
bug Something isn't working T-dev-tools

Comments

@ilblackdragon
Copy link
Member

ilblackdragon commented Feb 9, 2022

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.

@ilblackdragon ilblackdragon added the bug Something isn't working label Feb 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working T-dev-tools
Projects
None yet
Development

No branches or pull requests

1 participant