We design, harden and operate the validator and node infrastructure that blockchain networks depend on, built to stay online and secured from the hardware up. Our work draws on years of hands on experience in enterprise systems, network engineering and information security, and launch teams have trusted us as a genesis validator on Shentu, Terra and Stargaze.
Six areas where we put our experience to work, both on the networks we operate and for teams that need a dependable infrastructure partner.
We design, deploy and run validator and full node infrastructure, from hardware sizing and operating system builds through to chain upgrades. Upgrades are rehearsed before they reach production, so planned network events stay uneventful.
Validator signing keys never sit on public facing machines. We keep signing isolated, tightly limit who and what can reach it, and set up failover so a backup node can never sign alongside the primary and cause a double sign.
Minimal operating system builds, closed ports by default, key based access only, and firewalls that allow just what a node needs. Sentry style network layouts keep validators out of direct reach of the public internet.
Every node reports its health, sync status, peers and resource use around the clock. Alerts go straight to an engineer, and each incident ends with a written review so the same failure does not happen twice.
We have taken part in four genesis launches and many testnets. Project teams get an operator who tests early builds, reports bugs clearly, and is ready on launch day when the first blocks are produced.
For teams running their own nodes, we review architecture, access control, key handling and monitoring. You get practical findings ranked by risk, written so your engineers can act on them right away.
A simplified view of the layered setup we build. Each layer narrows what an attacker can touch, so the signing keys at the center stay out of reach.
Peers on the open network only ever see our sentry nodes. Direct connections to the validator are blocked at the firewall.
Sentry nodes relay blocks and transactions and absorb attacks. If one is targeted, it can be replaced quickly without touching the validator.
The validator has no public address and talks only to its own sentries. A standby backup waits, blocked from signing while the primary runs.
Keys live in an isolated signer that the validator asks for signatures. They never sit on a machine that faces the internet, and every request is logged.
Where we have run validator and node infrastructure, from genesis launches to long running mainnets and early testnets.
A security focused chain that applies formal verification to smart contracts through the CertiK Virtual Machine. We joined as a genesis validator at launch.
The relaunched Terra chain, built on the Cosmos SDK and governed by its community. We joined as a genesis validator when the chain went live.
An interoperable Cosmos chain built for NFTs, with its marketplace running fully on chain. We joined as a genesis validator and have operated on it since launch.
A high throughput chain that orders transactions with Proof of History and places heavy demands on hardware and networking. We run validator infrastructure tuned for those demands.
The original Terra chain, now maintained and governed by its community of validators. We run validator infrastructure and take part in its governance.
A research driven chain built on peer reviewed methods and the Ouroboros consensus protocol. We operate a mainnet stakepool, with the block producing node kept behind its own relay nodes, and help other operators harden their setups.
A modular data availability network that lets teams launch their own chains without running full consensus. We ran validator infrastructure through its testnet phase.
A Layer 1 chain written in the Move language by engineers from Meta's Diem project. We ran validator infrastructure during its testnet program.
A Layer 1 chain built around the Move language and parallel transaction execution. We ran validator infrastructure during its testnet program.
A decentralized oracle network that delivers outside data to smart contracts. We ran node infrastructure during its testnet program.
A chain designed for mobile games and the economies inside them. We ran node infrastructure during its testnet program.
A Cosmos chain focused on digital media ownership and new NFT standards. We ran validator infrastructure during its testnet program.
A Cosmos chain for cross chain lending and liquidity, formerly known as Umee. We ran validator infrastructure during its testnet program.
A Cosmos chain for interoperable smart contracts built with CosmWasm. We ran a mainnet validator on it before retiring our node.
An EVM compatible Cosmos chain linking Ethereum applications to the wider interchain. We ran it as a genesis validator before retiring our node.
Listing a network reflects our technical work on it, not an endorsement of its tokens.
The habits that keep our infrastructure safe and online. They come from years of running production systems where downtime and breaches were never an option.
We were chosen as a genesis validator on Shentu, Terra v2, Stargaze and Evmos. Launch teams pick their first validators carefully, and being on those lists reflects trust in how we work.
Cosmos SDK chains, Solana, Cardano and Move based chains like Aptos and Sui. Each fails in its own way, and we know them from hands on operation, through emergency upgrades and chain halts alike.
We run toward a 99.9% uptime target. Validator signing records are public on chain, so anyone can check our history without having to take our word for it.
Changes are planned and documented, incidents follow a clear response process, and every incident gets a review afterward. These habits come straight from ITIL based service management in enterprise IT.
Hundreds of signals from every node feed our monitoring, and alerts page an engineer the moment something looks wrong. Most issues are fixed before they ever affect the network.
Since 2021 we have had no breaches, no key compromises and no unauthorized access to our systems. Security is where every setup begins, not a step added at the end.
We take part in network governance, spread our infrastructure across regions, and support young networks early, when they need reliable operators the most.
No ticket queues, call centers or sales desks. Project teams and partners speak directly with the person responsible for their infrastructure, and during network events we share clear, timely updates.
NITAWA Systems is a blockchain infrastructure and security engineering firm. Since 2021 we have designed, hardened and operated validator and node infrastructure on more than ten blockchain networks, including genesis launches on Shentu, Terra v2, Stargaze and Evmos. Our work draws on long experience in enterprise systems administration, network engineering and information security.
Straight answers about what we do, how we secure validator infrastructure, and what we do not do.
NITAWA Systems is a blockchain infrastructure and security engineering firm. We design, secure and operate validator and node infrastructure for blockchain networks. Our work covers node deployment and upgrades, security hardening, key management, monitoring and incident response, and infrastructure support for teams launching new networks.
A genesis validator is one of the validators included in a blockchain's very first block, chosen by the launch team before the network goes live. It has to be ready, tested and online the moment the chain starts. NITAWA Systems has been a genesis validator on Shentu, Terra v2, Stargaze and Evmos.
We have run validator and node infrastructure on Cosmos SDK chains such as Shentu, Terra v2, Terra Classic, Stargaze, Juno and Evmos, on Solana, and on Cardano, where we operate a mainnet stakepool. We have also taken part in testnets for Celestia, Aptos, Sui, Razor Network, Realis, IDEP and UX Chain.
Signing keys are kept off public facing machines, access is limited and logged, and failover is set up so a backup node can never sign at the same time as the primary. Every node is monitored around the clock, and alerts go straight to an engineer on call.
Double signing happens when a validator signs two different blocks at the same height, usually because a backup node came online while the primary was still running. Networks treat it as a serious fault and penalize it heavily. We prevent it by allowing only one active signer at a time and by designing failover so a backup cannot sign until the primary is confirmed stopped.
In a sentry node architecture, the validator never connects to the public peer to peer network directly. It talks only to a small set of sentry nodes that face the internet on its behalf. If the sentries are attacked or overwhelmed, the validator's address stays hidden and fresh sentries can be brought up quickly.
We look at node architecture, network exposure, access control, key handling, monitoring and alerting, and upgrade and recovery procedures. The result is a written report of findings ranked by risk, with practical steps to fix each one.
No. NITAWA Systems is a technical infrastructure and security provider. We do not sell tokens, hold or manage funds or digital assets for anyone, offer investment products, or promise any financial return. Nothing on this website is financial, investment or legal advice.
Launching a network and need dependable validators from day one? Running your own nodes and want a second set of eyes on their security? Send us a message and tell us what you are building. We are always glad to talk infrastructure.
We usually reply within 24 to 48 hours.