Start Running your BEACON Today
Follow the steps below to set up and run your Blockcast BEACON Docker image:
Last updated
Was this helpful?
Follow the steps below to set up and run your Blockcast BEACON Docker image:
Last updated
Was this helpful?
Make sure you have installed and running in the background
Retrieve the Blockcast Beacon Docker Image
Download the Blockcast BEACON docker compose file from.
Or run git clone https://github.com/Blockcast/beacon-docker-compose.git
Launch and start running Blockcast Beacon
Start running your Blockcast BEACON with command docker compose up
Generate hardware and challenge key
While BEACON client is up, in a separate window
run docker compose exec blockcastd blockcastd init
It would generate an output that contains your device's Hardware ID, Challenge Key and a Registration URL:
Note:
Hardware ID is a unique public identifier for your device.
Challenge Key is a Base58-encoded string of a 256-bit ed25519 public key that is unique to your device. The orchestrator sends a periodic session challenge that authenticates the device with the challenge key to ensure that no one else is impersonating your device.
Backup your private key (in ~${HOME}/certs/gateway.key
)and keep it safe, otherwise you will lose the ability to prove ownership of this device.
Register your docker instance on the web portal
Go to our web portal and log in/register
Copy and paste the Registration URL from the console output with your pre-filled Hardware ID and Challenge Key into your browser, OR
Go to Manage Nodes page, press “Register Node” button, and manually enter your keys in the portal registration flow
You will need to enable location access from your browser
Here is how to enable it on Chrome. If you are using other browser, it might look different.
Confirm your instance is online and healthy
If your node is registered successfully and running, your node should show Healthy
status in a few minutes in the node list table on the /manage-nodes
page.
Clicking on the node entry in the node list table lands you onto the node details page, you should be able to see the uptime, connectivity, rewards info of that particular node. The nodes need to be online for 6 hours in order for the first connectivity test to run. The first batch of rewards does not kick in until 24 hours of being continuously online.