Axelar
Mainnet- Chain
- axelar-dojo-1
- Valoper
- axelarvaloper14emn7k8rk2mjzdk38cyltrk2npds2qfjmptj64
We run validators on Cosmos-SDK networks and build the tooling around them.
Three mainnets, consensus signing on a separate host, and monitoring we wrote because the off-the-shelf kind kept telling us everything was fine.
- Mainnets
- 3
- Consensus signing
- tmkms
- Slashing events
- 0
- Open source
- MIT
Axelar · Lava · CrossFi
Key on a separate host, never on the node
Across all networks
Our Lava scoreboard is public
Active mainnets
Delegate directly from the links below. Addresses are shown in full so you can verify them against a block explorer before signing anything.
Lava Network
Mainnet- Chain
- lava-mainnet-1
- Valoper
- lava@valoper1mxh36wxdzxjhg8zqjwm7949avzzamfkukf2e9j
CrossFi
Mainnet- Chain
- crossfi-mainnet-1
- Valoper
- mxvaloper1exxk8n2ltxy3q44s68q9mgnw2axhzhfvu9j205
How we operate
Nothing here is unusual for a serious operator. It is listed because it is checkable, not because it is clever.
Consensus key off the node
Axelar signs through tmkms on a separate host. The validator machine holds no consensus key, so compromising it does not compromise the key.
Monitoring we had to write
Signing quality is measured from the chain itself — absent votes and nil votes counted separately, ours told apart from network-wide stalls. Off-the-shelf tools conflated them.
Public scoreboard
We publish Polli's official Lava score broken into its components, for every validator including ourselves. We currently rank 70th of 74 and the page says so.