Send and Receive Tokens
This page decribes how to receive and send RENEC tokens using the command line tools with a command line wallet such as a paper wallet, a file system wallet, or a hardware wallet. Before you begin, make sure you have created a wallet and have access to its address (pubkey) and the signing keypair. Check out our conventions for entering keypairs for different wallet types.
Testing your Wallet#
Before sharing your public key with others, you may want to first ensure the key is valid and that you indeed hold the corresponding private key.
In this example, we will create a second wallet in addition to your first wallet, and then transfer some tokens to it. This will confirm that you can send and receive tokens on your wallet type of choice.
This test example uses our Developer Testnet, called devnet. Tokens issued on devnet have no value, so don't worry if you lose them.
Airdrop some tokens to get started#
First, airdrop yourself some play tokens on the devnet.
where you replace the text <RECIPIENT_ACCOUNT_ADDRESS> with your base58-encoded
public key/wallet address.
A response with the signature of the transaction will be returned. If the balance of the address does not change by the expected amount, run the following command for more information on what potentially went wrong:
Check your balance#
Confirm the airdrop was successful by checking the account's balance.
It should output 1 RENEC:
Create a second wallet address#
We will need a new address to receive our tokens. Create a second keypair and record its pubkey:
The output will contain the address after the text pubkey:. Copy the
address. We will use it in the next step.
You can also create a second (or more) wallet of any type: paper, file system, or hardware.
Transfer tokens from your first wallet to the second address#
Next, prove that you own the airdropped tokens by transferring them. The Renec cluster will only accept the transfer if you sign the transaction with the private keypair corresponding to the sender's public key in the transaction.
where you replace <KEYPAIR> with the path to a keypair in your first wallet,
and replace <RECIPIENT_ACCOUNT_ADDRESS> with the address of your second
wallet.
Confirm the updated balances with renec balance:
where <ACCOUNT_ADDRESS> is either the public key from your keypair or the
recipient's public key.
Full example of test transfer#
Receive Tokens#
To receive tokens, you will need an address for others to send tokens to. In Renec, the wallet address is the public key of a keypair. There are a variety of techniques for generating keypairs. The method you choose will depend on how you choose to store keypairs. Keypairs are stored in wallets. Before receiving tokens, you will need to create a wallet. Once completed, you should have a public key for each keypair you generated. The public key is a long string of base58 characters. Its length varies from 32 to 44 characters.
Send Tokens#
If you already hold RENEC and want to send tokens to someone, you will need
a path to your keypair, their base58-encoded public key, and a number of
tokens to transfer. Once you have that collected, you can transfer tokens
with the renec transfer command:
Confirm the updated balances with renec balance: