Long-term NEAR pool operator
Operating 01node.poolv1.near continuously.
Delegate NEAR to a bare-metal validator running on owned hardware in two Tier III datacenters since 2019. The address below is on-chain verifiable on the listed explorer.
01node.poolv1.nearNEAR Protocol (NEAR) is a sharded Layer-1 with WASM smart contracts and account abstraction. NEAR uses delegated proof-of-stake — token holders delegate to staking pools, which run validators.
Mainnet launched in October 2020. 01node operates the staking pool 01node.poolv1.near.
Operating 01node.poolv1.near continuously.
Among the lowest in the active operator set. Verifiable on NEAR Explorer.
NEAR runs on the same owned hardware as our broader 40+ mainnet footprint.
NEAR's architecture rewards operators who can run sharded consensus reliably.
NEAR's official wallet at wallet.near.org or MyNearWallet for hardware support.
In the staking interface, search the pool name. Click 'Stake' on this page to deep-link to our pool on NEAR Explorer.
Stake activates immediately for reward purposes.
Claim or restake at any epoch boundary.
NEAR locked during unbonding (~36 hours). Significantly faster than Cosmos chains.
Pool misbehaviour can be slashed; pool operators bear delegator stake risk.
Sharded consensus introduces coordination requirements not present in single-shard chains.
Approximately 2-3 epochs (~36 hours). Materially faster than Cosmos chains’ 21-day unbonding.
3% on 01node.poolv1.near. One of the lowest in the active set.
NEAR runs Nightshade — a chain-of-shards consensus where validators are assigned to shards and rotated periodically. Each shard processes a subset of transactions in parallel.
Yes — Ledger via MyNearWallet or NEAR Wallet integration.
No. Our disclosed-incident history across all networks is at /security#disclosed-incidents.
NEAR’s account model lets accounts have human-readable names (like 01node.poolv1.near) and allows function calls between accounts. Different from Ethereum's EOA/contract distinction.
Five years ago a validator was a server. Today it is a cluster of signers, and the math is the entire reason solo operators still slash themselves. A focused walk-through of the 2/3 signing architecture, the slashing-protection check that runs before every block, and the key-sharding property that makes a single compromised node useless.
7 MIN READ→EngineeringIn June 2019 we published our validator architecture on Medium — YubiHSM dual-DC, VPN-only access, sentries per network. Seven years and forty mainnets later, here is what we kept, what we changed, and what we would do differently if we started today.
11 MIN READ→$ 01.ro --network near --verify
CHAIN: NEAR Protocol (NEAR)
VALIDATOR: 01node.poolv1.near
COMMISSION: 3%
ESTIMATED_APR: 8-10%
UNBONDING: ~2-3 epochs (~36 hours)
ECOSYSTEM: NEAR
SLASHING_EVENTS_LIFETIME: 0
VERIFY_AT: https://explorer.mainnet.near.org/accounts/01node.poolv1.nearThe NEAR Protocol validator address above is on-chain verifiable. The Stake button deep-links into the right wallet with everything pre-filled.