Since 2024 we have run nodes on 26 networks, 10 of them right now. Protocol teams bring us in at testnet and keep us in the set at mainnet: we validate, run the public RPC, API and explorer, turn up for upgrades, and answer in the timezone most of Asia is awake in. Every address, endpoint and incident on this page can be checked on-chain or read live from our own nodes — none of it needs to be taken on trust.
What protocol teams and foundations did after working with us. Each item links to something you can check yourself.
The RPC, API and gateway endpoints here are public and free to use, no key, best effort. Addresses are listed so anyone can pull our signing history straight from the chain. Last verified 19 Sep 2026.
Networks we are validating before their mainnet launch.
Incentivized testnets that closed, mainnet programmes that ended, and testnets we validated from genesis that have since gone to mainnet. Explorer links stay up so the history is checkable, not just claimed.
What we actually did, with dates. Upgrades, incidents, new networks, endpoints going up or coming down.
Most teams meet us at testnet and keep us through mainnet. This is what we take on at each stage.
We join early, usually at genesis, and run the validator plus a public RPC and API so other participants have something to point at. We file the bugs we hit instead of sitting on them, rehearse every upgrade before it reaches mainnet, and tell you where the docs break — we have set up nodes from 26 sets of instructions and can usually say which step people will get stuck on.
Genesis ceremony, key handling, sentry topology, and being online at the hour you pick regardless of timezone. From day one we publish the endpoints other operators and wallets need — public RPC, REST API and an explorer, as on Kiichain above — and add snapshots, state-sync or an addrbook when your validator set needs a faster way in.
Upgrades inside the window, a vote on every governance proposal, monitoring and alerting that pages a phone, and a written note when something goes wrong. If you need IBC relaying, an archive node or a dedicated endpoint for your frontend, that is in scope too.
We usually come in through a foundation delegation or a node-running grant, but we will start on a testnet without one if the project is interesting. Tell us the chain, the stack and the launch date and we will say plainly whether we can do it well.
The parts that decide whether your delegation is safe.
Testnets and light chains run on dedicated-vCPU VPS. Mainnets, and any chain whose state growth or disk I/O calls for it, run on bare metal we rent outright — no shared tenancy, no burst credits. We move a network from one to the other when it graduates to mainnet, or earlier if it starts missing blocks under load. Ask us which tier your network is on and we will tell you; we would rather say "VPS, and here is why that is enough for now" than claim a rack we are not paying for.
Validator keys live on the signer host only, never on the public-facing sentries, and never on a laptop. Consensus keys are backed up offline. Double-sign protection is enforced at the signer, so a failover cannot produce a second signature for the same height.
Each validator sits behind private sentry nodes in a separate region, so the validator's own IP is not exposed to the peer-to-peer network. Public RPC traffic is served by separate machines and never touches the validating node.
Prometheus and Grafana on every host, with alerts on missed blocks, peer count, disk headroom and block-time drift. Alerts page a phone, not an inbox — chain upgrades usually land at night in our timezone and we plan around that.
We track governance proposals and testnet upgrade rehearsals, and use Cosmovisor where the chain supports it. Snapshots are taken before every upgrade so we can roll back inside minutes.
We publish what happened. Downtime, a missed upgrade, a misconfiguration — it goes in the changelog with the cause and the fix. An operator with no incidents on record has either been lucky or is not telling you.
Validators and their sentries never share a region, so losing one datacentre does not take a node offline. Peer latency depends on where your own validator set sits, so we measure it per chain rather than quoting a number here.
Three engineers split between Thailand and Vietnam, running nodes since 2024. It is what we do full time, so an upgrade or an incident gets a person rather than a queue, and between us the working day covers UTC+7 from early morning to late night.
Noddex is operated by GREEN FLASH SOFTWARE COMPANY LIABILITY LIMITED (GreenFlash Co., Ltd), a software company registered in Vietnam — that is the entity you would contract with. We work under the Noddex name rather than individual handles, and one team inbox answers everything, so nothing depends on catching a particular person online.
Telegram · usually within a few hours
We never send the first message. Nobody at Noddex will DM you asking for a seed phrase, a private key, or a transfer to "migrate" your stake. Delegation happens in your own wallet, through the network's own explorer or staking app — the links in the table above are the only ones we use.
Noddex