Axelar
Mainnet- Chain
- axelar-dojo-1
- Valoper
- axelarvaloper14emn7k8rk2mjzdk38cyltrk2npds2qfjmptj64
We run validators on Cosmos-SDK networks and build the tooling around them.
Three mainnets, Axelar consensus signing on a separate host, and monitoring we wrote because the off-the-shelf kind kept telling us everything was fine.
- Mainnets
- 3
- Axelar consensus signing
- tmkms
- Axelar EVM chains
- 17
- Open source
- MIT
Axelar · Lava · CrossFi
Key on a separate host since Aug 2026
Chain maintainer on all of them
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, and the validator machine holds no copy of that key. We learned this the hard way: in March 2026 our previous Axelar validator was tombstoned after an old server restarted it during a migration.
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. Our own rank sits on the same page as everyone else's.