1a) Install and build it from BitShares-Core
- BitShares offers you to install BitShares-Core into different platforms; Ubuntu (x64), OSx, and Windows. Please refer installation-guide.

1b) Use the CLI-Wallet tools for Windows (x64)
- This option you do not need to install BitShates Core. To obtain the tool, go to a BitShares release page and download the BitShares-Core-*-x64-cli-tools.zip.

To reduce compilation time, you can tell the compile infrastructure to only compile the witness node by running.:

The cli_wallet creates a local wallet.json file that contains the encrypted private keys required to access the funds in your account. It requires a running witness node (not necessarily locally) and connects to it on launch.

programs/cli_wallet/cli_wallet-sws://127.0.0.1:8090

Depending on the actual chain that you want to connect to your may need to specify –chain-id.

The below section shows two example patterns how to launch the cli_wallet. The first example, we use the public API server node to connect the cli_wallet and also open WebSocket RPC or RPC-HTTP ports. The cli_wallet opens an RPC port for Wallet operations (i.e., spend, buy, sell…). The second example, we use an IP address (localhost) and also open the port for HTTP-RPC.

<Examples>

1.Connecting a Cli-Wallet by using the public API server node

2.Connecting a Cli-Wallet by an IP address (localhost)

<Example 1> Connecting a Cli-Wallet by using the public API server node

We use the public API node of OpenLedger wss://bitshares.openledger.info/ws and connect via secured WebSocket connection:

This will open the cli-wallet and two RPC ports. In order to allow RPC calls for wallet operations (spend, buy, sell, …), you need to specify the RPC port(s) and set a parameter to choose between WebSocket RPC -r or RPC-HTTP -H requests.

Note

The cli-wallet can open a RPC port so that you can interface your application with it. You have the choices of Websocket RPC via the -r parameter, and HTTP RPC via the -H parameter

<Example 2> Connecting a Cli-Wallet by an IP address (localhost)

./programs/cli_wallet/cli_wallet-sws://127.0.0.1:8090-H127.0.0.1:8091

This will open the port 8091 for HTTP-RPC requests and has the capabilities to handle accounts (by Wallet API Calls) while the witness_node can only answer queries to the blockchain.

After opening the cli-wallet, if you have not had a local wallet yet, you will receive >>>new prompt to provide a pass-phrase for the local wallet. Once a wallet has been created (default wallet file is wallet.json), then it will prompt with locked>>>.

In Graphene, balances are contained in accounts. To claim an account that exists in the Graphene genesis, imports the private key for an existing account. The private key must match either an owner key or an active key for the named account.

import_key

>>> import_key<name>"<wifkey>"

Funds are stored in genesis balance objects. These funds can be claimed, with no fee, by using the import_balance command. This call will construct transaction(s) that will claim all balances controlled by wif_keys and deposit them into the given account.

In transfer, if the broadcast flag is False, the wallet will construct and sign, but not, broadcast the transaction.

transfer:

unlocked>>transfer<from><to><amount><asset><memo><broadcast>

<Example> `faucet` wants to send 100000 `CORE` to `alpha` user.:

unlocked>>transferfaucetalpha100000CORE"here is the cash"true

The wallet will return the actually signed transaction.

Note

In order to transfer, the wallet must be unlocked. If the broadcast flag is False, the wallet will construct and sign, but not broadcast the transaction. This can be very useful for a cold storage setup or to verify transactions.