A validator on Luggom joins the CometBFT consensus to secure the chain and can, if it wants, volunteer as a TLSNotary notary. Both roles protect the same thing: the network and the proof that feeds it.
CometBFT consensusVoluntary notarisingTestnet
The role
Two roles, one node.
Being a validator is what keeps the network up. Being a notary is optional. You can do only the first, or take on both on the same server.
Seal the chain
The validator takes part in the CometBFT consensus: it proposes blocks and votes on them. Luggom security rests on this set of nodes.
You can notarise payments
The notary finishes the TLS session outside the browser and signs the receipt. Notaries come from a pool of volunteers among the validators and are paid from 0.5% of the governance reserve, held in a separate module account.
Scale
The gate to the network.
Mainnet only opens with a minimum of 12 validators signing. The cap is 180. Below the minimum, there is no network to open.
Validator cap180
Minimum for mainnet12
Preparation
What you should have ready.
These are guidance, not official numbers. Match the resources to the size of the chain and to your tolerance for risk.
A Linux server
Bare metal or a VPS, with a static IP. It is what keeps the node running around the clock.
Resources with headroom
CPU, RAM and disk with margin for the growth of the chain and its state. Treat this as guidance, not as a published specification.
A proper service
Run the node as a systemd service or inside Docker. It should restart on its own and survive a crash.
Key discipline
Keep the validator key in a keyring or an HSM. Whoever holds the key is who votes.
Monitoring and alerts
Watch whether the node is signing and get a warning when it stops. A validator that is down misses blocks and reputation.
Sentries and seeds
Set up sentry nodes to protect the validator and seed nodes to help new peers join.
Joining the testnet
Seven steps, in order.
01 / install
Install the binary
Install the node binary from the testnet package.
02 / initialise
Initialise with the genesis
Start the chain with the published genesis file.
03 / keys
Set the keys
Set the node key and the validator key.
04 / join
Join through the seeds
Connect to the network through the published seed nodes.
05 / start
Start the service
Start the service and let the node sync up to the network height.
06 / create
Create the validator
Send the create-validator transaction.
07 / verify
Verify signing
Confirm that your validator is signing blocks.
The step by step guide, with every command, ships inside the testnet package.
The package
What ships with it.
You will not assemble this from memory. When the testnet opens, everything you need arrives in a single package, with the commands in plain sight.
Testnet packageready
Binaries
node and tools
Genesis
published file
Scripts
install and service
Seed nodes
published list
Instructions
step by step guide
Everything you need to start a validator on the testnet.
Status
The testnet is live.
The public network runs luggom-test. The operator guide and binaries ship with the testnet package. There is no signup form and no contact address: the package is the door.
Prepare a server
A Linux machine with a static IP, with room and memory waiting for the node.
Read the design
The whitepaper explains the consensus, the TLSNotary proof and the reserve, so you reach the testnet knowing what you are running.
Study key management
Learn how to store keys and harden the server before any vote counts.
Mainnet opens with 12.
If you want to be ready, read the design and see what the download will hold.
