To to run a full node that we can connect to, we need to open the RPC interface, this can be done by:
./echo_node \--seed-node=echo-testnet-us-1.echo-dev.io:6310 \--seed-node=echo-testnet-eu-1.echo-dev.io:6310 \--rpc-endpoint=127.0.0.1:6311 --testnet
This will open port
Note, that at the first run, the node will need to synchronize the blockchain with the network first, which may take a few minutes.
The CLI wallet is used to interact with the Echo blockchain and use to generate signatures.
All it takes for the CLI wallet to run is a trusted API server to connect to the blockchain. Businesses and individuals run these public API servers.
./echo_wallet -s wss://testnet.echo-dev.io/ws
In this example, we use the public Echo node API and connect via a secured websocket connection. But you can yse your local node IP and PORT like this:
./echo_wallet -s ws://127.0.0.1:6311/ws
This will open the CLI wallet and will ask you to provide a passphrase for your local wallet.
Once a new wallet has been created (default wallet file is
wallet.json), it will prompt with:
Please use the set_password method to initialize a new wallet before continuingnew >>>
A new wallet needs to be initialized before its first use, by setting a password using the
IMPORTANT: Private data, such as a passphrase or private keys, aren't stored by the wallet.
new >>> set_passwordInput private data:supersecretpassphraselocked >>>
Now the wallet can be unlocked by providing the passphrase:
locked >>> unlockInput private data:supersecretpassphraseunlocked >>>
You can get a detailed list of all commands by calling the
TAB you can get a list of autocomplete commands or complete current if there are no alternatives.
The CLI wallet can open an RPC port, so that in be accessed by applications or scripts. This can be done via either:
websocket RPC via the
HTTP RPC via the
./echo_wallet -s ws://127.0.0.1:6311/ws -H 127.0.0.1:8092 -r 127.0.0.1:8093