First you’ll need to initialize the LiquidAccounts implementation with the
chain_idof the platform you’re operating on. If you are using the
#define VACCOUNTS_SUBSCRIBERdefinition to use LiquidAccounts from another host account, that host account must be used in place of the
When running the test commands, if you're using leap version 3.0.0+ you'll need to add
--use-old-send-rpc -t falseto the cleos command to not use the
send_transaction2rpc by default as seen below. If using the legacy eos software, that flag is not required.
cleos -u $DSP_ENDPOINT push action $KYLIN_TEST_ACCOUNT xvinit "[\"$CHAIN_ID\"]" -p $KYLIN_TEST_ACCOUNT
# if using VACCOUNTS_CROSSCHAIN
cleos -u $DSP_ENDPOINT push action $KYLIN_TEST_ACCOUNT xvinit "[\"$CHAIN_ID\",\"$HOST_CHAIN\",\"$HOST_CODE\"]" -p $KYLIN_TEST_ACCOUNT
# if using VACCOUNTS_SUBSCRIBER
cleos -u $DSP_ENDPOINT push action $KYLIN_TEST_ACCOUNT xvinit "[\"$HOST_ACCOUNT_NAME\"]" -p $KYLIN_TEST_ACCOUNT
Then you can begin registering accounts. You will need to do this either in a nodejs environment using the
dapp-client-lib, or you can use the
zeus vaccounts push-action. Here is an example of using the lib to register an account..
All payloads must include a key value pair with
"vaccount":"vaccountname"or the transaction will fail. This is so the
dapp-clientcan fetch the nonce associated with the LiquidAccount.