Bluzelle

Bluzelle hardfork

Two weeks ago Bluzelle net-7 was released as a snapshot of net-6 with added features, most notably with nft storage. mp20 participated in the many testnets leading up to the hardfork. We were rewarded with bug bounties during the process. The new mainnet has been running without issues since launch, however there is still very little network activity. Bluzelle has announced a validator rewards program. The details are not clear yet but we believe validators will get monthly airdrops.

Deploying a sentry and validator on bluzelleTestNetPublic-22

This post will explain how to deploy and set up a sentry and validator on Bluzelle’s current testnet. The sentry will act as a proxy for the validator. You’ll need 2 instances of your favorit linux distro, this guide was done using Debian 10. Make adjustments where needed. 1 vCPU, 4 gb ram and 80 gb of storage will get the job done (for now) Install dependencies sudo apt install git build-essential jq nano wget -y

Deploying a sentry and validator on Bluzelle's mainnet

This post will explain how to deploy and set up a sentry and validator on Bluzelle’s mainnet. The sentry will act as a proxy for the validator. You’ll need 2 instances of your favorit linux distro, this guide was done using Debian 10. Make adjustments where needed. 1 vCPU, 4 gb ram and 80 gb of storage will get the job done (for now) Install dependencies sudo apt install git build-essential jq nano wget -y

Bluzelle Curium on FreeBSD

Quick write up of how to get a Bluzelle Curium node up and running on FreeBSD. This post is written the same day FreeBSD celebrates the release of version 13.0. This was done a couple of days ago, so the version used in this example was FreeBSD 12.2-RELEASE-p6 Install dependencies pkg install git gcc gmake wget jq git gcc Install go cd /usr/local wget https://golang.org/dl/go1.16.3.freebsd-amd64.tar.gz tar -C /usr/local/ -xzf go1.16.3.freebsd-amd64.tar.gz

When Stargate comes to Bluzelle Curium

Want to keep a close eye on how the progression of the project is going? Check out the active branches on GitHub and see what the team is working on. With some easy research we can stay one step ahead of the pack and potentially see an update before it hits the official announcement channel. We can see there is a lot of activity on a branch called stargate We can safely assume this an update to the Cosmos SDK, the largest update Cosmos has received to date.

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 sentry-02.mp20.net for the public to interact with. Query To query the node from blzcli append –node http://sentry-02.mp20.net:26657 to the command dApps Developers are welcome to use sentry-02 for their applications as a fallback/secondary to http://sandbox.sentry.net.bluzelle.com:26657 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.