First steps after the Waves Enterprise platform installation

One of the first things you can do after deploying the Waves Enterprise platform is to do the following steps:

Attaching the node address to the client

After the blockchain platform has started, follow these steps:

  1. Open a browser and input http://localhost in the address bar.

  2. Register in the client using any valid email address and log in to it.

  3. Open the Choose address -> Create address page. To open the menu after the first login, you should enter the password that you entered during your account registration.

  4. Choose the Add address from node keystore option and press “Next”.

  5. Fill in the fields below. You can take the values from the file credentials.txt for the first node in the working directory.

    • Address name - specify the name of the node.

    • Node URL - specify the http://localhost/nodeAddress value.

    • Node authorization type - choose the node authorization type (token or api-key).

    • Blockchain address - specify the name of the node.

    • Key pair password - specify the node key pair password.

Now you can send transactions from the web client of the node which has tokens.

Sending transactions

Transactions can be sent from the web client or using the node’s REST API. You can perform the following actions via the client:

  • Operations with tokens. You need to attach the node address to the web client for the token operations.

  • Operations with private groups to exchange confidential data.

  • Operations with Docker contracts.

  • Using the anchoring option.

  • Sending data transactions.

All actions are performed in an intuitive and friendly web interface. Each action is accompanied by sending the corresponding transaction to the blockchain.

You can use the node’s REST API to send any transaction to the blockchain. Follow these steps for sending a transaction via the node’s REST API:

  1. Open the node’s REST API using http://localhost/node-0 address in a browser.

  2. Enter the api-key into the API key authorization form and press Authorize. You can copy the api-key value from the “API key” field of the credentials.txt file.

  3. Choose Transactions methods, then POST ​/transactions​/signAndBroadcast method and press “Try it out”.

  4. Using the transactions table choose a transaction which you want to send to the blockchain.

  5. Make a json request using your parameters and examples from the transactions page for the each kind of transaction. Mainly these parameters are:

    • sender - an address of a node-sender;

    • password - a password of the keystore.dat file;

    • recipient - an address of a node-recipient;

    • various identifiers.

  6. Insert the request in the corresponding body form of the REST API, where you can also find examples of requests for sending transactions to the blockchain.

  7. Press “Execute” and watch the result in the Response body field. The successful response code is 200.

Activating additional options

Two options are enabled in sandbox mode by default - working with Docker contracts and mining. Authorization is set by api-key-hash. The node configuration file already contains the default settings for the local Docker host that you can develop Docker contracts immediately. Mining settings are also set by default in accordance with the recommended values.

Additional options for the Waves Enterprise platform are enabled and configured using the appropriate sections of the node configuration file. Go to the configuration file of the node where you want to enable additional options or configure the ones used, and edit the sections of the selected options.

Node configuration files are stored in individual directories of each node, for example ../working directory/configs/nodes/node-0/node.conf. Depending on the configuration file section the recommended values are either already set in the sample files, or they can be found on the section description page. The section should be uncommented or copied from the documentation from the corresponding description page.

If you have any questions about configuring sections of the node configuration file, contact technical support.