Monitoring stack released

dallas_barr, the operator of validator Stake.House has released a docker-compose stack for monitoring systems running Bluzelle Curium. The stack is made up of prometheus alertmanager alerta grafana The tools are available on GitHub here. Alerts When configured and running the stack will send email alerts if a validator is not signing blocks, running low on disk space, free available RAM and some other important metrics like high CPU utilisation or not enough connected peers.

Public RPC on mainnet

mp20 has opened the RPC port on for the public to interact with. Query To query the node from blzcli append –node to the command dApps Developers are welcome to use sentry-02 for their applications as a fallback/secondary to Further discussion As always, you can find us on Bluzelle’s Community Discord if you have any questions.

Server Environment and Decent Practises

Bluzelle curium will run on any unix like operating system. MP20 has run nodes on Debian, FreeBSD and MacOS, the latter just to see if it works. Debian and Ubuntu seem to be the most popular amongst operators. Dependencies build-essential jq go Recommendations Increase the open files limit for the user running Bluzelle curium. On Debian edit /etc/security/limits.conf with blzd-user hard nofile 1048576 and blzd-user soft nofile 65536 - Do not run Bluzelle Curium as root for all the obvious reasons.

Selecting a Validator

This question gets asked a lot. The short answer is which ever one you want. The long answer is do your research and keep reading. Risks When delegating tokens to a validator you are trusting the validator not to get penalised by the network. If a validator gets jailed for failing to sign the required amount of blocks in a given window, all delegators and the validator’s self delegated stake is slashed by 0.

Bluzelle Staking Guide

If you haven’t done so already, it’s a good idea to read the article on The Bluzelle Network before proceeding. Short explanation of the core aspects of staking and some associated lingo. Staking can also be referred to as delegating, a person who stakes is known as a delegator, the amount of staked tokens is also known as the bonding amount, moving staked tokens from one validator to another is called redelegating, withdrawing your staked tokens from a validator is called unbonding.


Zero Eight was created in 2018 as the first community node on Bluzelle’s swarmDB. swarmDB was Bluzelle’s first functioning mvp for a decentralised database. Fast forward to 2021 and Zero Eight is a validator on mainnet and testnet. Zero Eight was the first validator after Bluzelle on mainnet and has been involved in many testnets leading up to mainnet. A long the way there have been bugs to report and documentation to help out with.

Bluzelle Curium

Bluzelle Curium is the dev name for Bluzelle’s Decentralised Database Service. It’s the database layer for the decentralised web. A commonly seen misconception is people comparing Bluzelle to Filecoin and other storage projects. Bluzelle is not a storage project, it is a database project, more specifically a nosql key-value store database. In simplified terms the Bluzelle application stack is built on the Tendermint consensus engine, the Cosmos SDK and Bluzelle CRUD (Create, Read, Update, Delete - the core functions of the Bluzelle database).