LiquidApps Documentation

Zeus vaccounts push-action

Push LiquidAccount actions easily with zeus’s wrapper of the dapp-client library. You can pass a --dsp-url for your DAPP Service Provider’s API endpoint. Then pass the name of the contract that the LiquidAccount code is deployed to, the action name (regaccount for example), and the payload.
You also have the ability to store your private keys with or without encryption. If you choose to encrypt, you can pass the --encrypted flag when creating a new account to store the keys. You can provide a password by command line, or with the flag --password. If you use the account again, zeus will look for the key based on what network you are operating on. If it finds it, it will use that key to sign and prompt for a password if needed.
zeus vaccounts push-action <CONTRACT> <ACTION> <PAYLOAD> --dsp-url https://kylin-dsp-2.liquidapps.io
# optional flags:
--dsp-url # url to DAPP Service Provider's API endpoint
# default: https://kylin-dsp-2.liquidapps.io
--private-key # LiquidAccount private key, can be provided or auto generated
# will be auto generated and stored in the storage path if not provided
--encrypted # Encrypt the LiquidAccount keys with a password
# default: false
--password # password to encrypt the keys with
--network # network LiquidAccount contract deployed on (other options: kylin, jungle, mainnet)
# development (local)
--storage-path # path to the wallet which will store the LiquidAccount key
# default: path.join(require('os').homedir(), '.zeus')
# Example:
zeus vaccounts push-action test1v regaccount '{"vaccount":"vaccount1"}'
zeus vaccounts push-action vacctstst123 regaccount '{"vaccount":"vaccount2"}' --private-key 5KJL... -u https://kylin-dsp-2.liquidapps.io
zeus vaccounts push-action vacctstst123 regaccount '{"vaccount":"vaccount3"}' -u http://kylin-dsp-2.liquidapps.io/ --encrypted --network=kylin --password=password