-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DVM: Function SIGNER() [3.5.2-114.DEROHE.STARGATE] --testnet #105
Comments
Working fine on my end. curl http://127.0.0.1:40403/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"scinvoke","params":{ "scid":"xxx", "sc_rpc":[{"name":"entrypoint","datatype":"S","value":"Tsign"}], "ringsize":2 }}' -H 'Content-Type: application/json' |
Thanks, that is a working solution. But it would also break all privacy inside the smart contracts, because now its obviously written forever to the blockchain and for everyone to read what wallet address had done the call? Or may I wrong? |
Just a AddOn: See https://explorer.dero.io/tx/36a7dd6aa109b11bd9d096b9f774dd72afd5f02e2aebeef20d8c90444e926183 With this small Block I could get the Smart Contract in Plain: und also know that Address dero1qywluvt6rul2wxaza7zrh2stxhvlaz0y6hj2759exfpfh7v8m7rsgqg7y8vrw had call Bid with 11 Units to that Contract ... |
It depends on the use case. You have to set ringsize to 2 when the SIGNER() function is used. |
{"Version": "3.5.2-114.DEROHE.STARGATE+01102022"} on --testnet
Use this sample smart contract:
At Initialization the Key "signer" will correctly stored.
But by calling "Tsign" the Key "signer" will only written as "000000000000000000000000000000000000000000000000000000000000000000".
Tested with different Wallets.
Test commands (40402 daemon,40403 wallet1,40404 wallet2):
curl --request POST --data-binary @t.bas http://127.0.0.1:40403/install_sc
curl http://127.0.0.1:40402/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getsc","params":{ "scid":"xxx" , "code":false, "variables":true}}' -H 'Content-Type: application/json'
curl http://127.0.0.1:40403/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"scinvoke","params":{ "scid":"xxx", "sc_rpc":[{"name":"entrypoint","datatype":"S","value":"Tsign"}] }}' -H 'Content-Type: application/json'
curl http://127.0.0.1:40404/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"scinvoke","params":{ "scid":"xxx", "sc_rpc":[{"name":"entrypoint","datatype":"S","value":"Tsign"}] }}' -H 'Content-Type: application/json'
The text was updated successfully, but these errors were encountered: