Test - LiquidApps Documentation

First you’ll need to initialize the LiquidAccounts implementation with the chain_id of the platform you’re operating on. If you are using the #define VACCOUNTS_SUBSCRIBER definition to use LiquidAccounts from another host account, that host account must be used in place of the chain_id.
1
# kylin
2
export CHAIN_ID=5fff1dae8dc8e2fc4d5b23b2c7665c97f9e9d8edf2b6485a86ba311c25639191
3
cleos -u $DSP_ENDPOINT push action $KYLIN_TEST_ACCOUNT xvinit "[\"$CHAIN_ID\"]" -p $KYLIN_TEST_ACCOUNT
4
# if using VACCOUNTS_CROSSCHAIN
5
export CHAIN_ID=5fff1dae8dc8e2fc4d5b23b2c7665c97f9e9d8edf2b6485a86ba311c25639191
6
export HOST_CHAIN=chainname
7
export HOST_CODE=vaccnthost
8
cleos -u $DSP_ENDPOINT push action $KYLIN_TEST_ACCOUNT xvinit "[\"$CHAIN_ID\",\"$HOST_CHAIN\",\"$HOST_CODE\"]" -p $KYLIN_TEST_ACCOUNT
9
# if using VACCOUNTS_SUBSCRIBER
10
export HOST_ACCOUNT_NAME=kylinhost
11
cleos -u $DSP_ENDPOINT push action $KYLIN_TEST_ACCOUNT xvinit "[\"$HOST_ACCOUNT_NAME\"]" -p $KYLIN_TEST_ACCOUNT
Copied!
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-client can fetch the nonce associated with the LiquidAccount.

Staking for services

DAPP Client

Last modified 8mo ago

Copy link