Test keys and accounts
When a user sends a transaction to the blockchain, the transaction needs to be signed with the user's private key. A standard user account includes the following details:
- User public key
- User private key
- User address
Gamma CLI simulates transactions for testing contracts and therefore needs a set of demo user accounts.
When Gamma server is first started, Gamma CLI automatically creates 10 testing accounts and saves their details in a JSON file named
orbs-test-keys.jsonin the local directory.
These keys are for testing only and should not be used in secure production environments.
Every account is assigned a textual ID, from
user10which can be provided as a command line argument to Gamma CLI to specify that a specific account should sign a transaction.
To replace the keys with a new batch of 10 accounts run in terminal
This will override
orbs-test-keys.jsonwith new data.
The JSON format of
Feel free to edit the file manually and add your own accounts. "Real-life" accounts are usually created using the Orbs Client SDK.
The fields are encoded as follows:
- Textual IDs for every account (eg.
user2) can be changed to any string you prefer