Ankr Network

The 2022 Ankr 2.0 whitepaper looks back to 2017, when the team wanted to redirect unused data-centre capacity toward Bitcoin mining, node hosting and Internet-of-Things workloads. It was a broad supply-side bet: aggregate machines first, then find jobs for them.

Blockchain nodes became the durable use. Ankr accumulated bare-metal servers, added hosted nodes and API access, and shifted toward the infrastructure beneath Web3 applications. The company did not abolish central operation during this transition; the whitepaper says the first Ankr Network was launched centrally so it could scale quickly.

A wallet or application needs a node whenever it requests a balance, log, fee estimate or contract result. Public RPC endpoints removed account setup for basic access, while paid tiers sold capacity and developer tools. Current documentation extends that catalogue to Advanced API, dedicated chains and rollups, staking and verifiable RPC.

Ankr 2.0 tried to make node supply less dependent on the company. Independent providers could connect full nodes to the routing network, while developers' requests were assigned through a load balancer. The whitepaper's 2022 payment and revenue splits describe the intended launch economics; they should not be read as a permanent 2026 tariff without a current accounting record.

The canonical ERC-20 arrived on 21 February 2019 with 10 billion units created once. Its verified code is unusually plain: transfers and allowances, with no mint, burn, pause, blacklist, owner or upgrade method. The tokenomics page says 40% was initially available and the other 60% was scheduled across August 2019–August 2022. Roughly 2% was sent to a dead address, but that does not decrement totalSupply.

Delegated staking gives the token another job. Providers self-stake and holders can delegate ANKR behind RPC full nodes to share rewards. That stake does not validate Ethereum, BNB Chain or the other chains whose data those nodes serve. The 2022 design contemplated slashing for independent providers and delegators, but current instructions list only Ankr as a selectable provider and the current FAQ says staking with Ankr has no slashing or other penalties. Governance is also mediated: 5 million ANKR is needed to propose, an administrator screens the submission, and the Ankr team implements an accepted change.

No slashing does not mean immediate access: the current FAQ sets an initial 84–91-day lock, followed by a 7–14-day undelegation period after an unstaking request.

On 1–2 December 2022, an attacker obtained a developer key, altered the aBNBc liquid-staking contract and minted 60 trillion aBNBc. Ankr estimated about $5 million of BNB damage across decentralized-exchange pools. It discontinued aBNBc and aBNBb, introduced ankrBNB and announced purchases and airdrops for affected holders and liquidity providers.

The after-action report later blamed a former team member who had combined social engineering with a malicious software package. That attribution is Ankr's account. The durable technical lesson was narrower: a liquid-staking receipt whose update key is compromised can fail even when the separate ANKR ERC-20 has no mint authority. Ankr said future updates would require multisignature approval and timelocks; the reviewed sources do not independently prove that every current staking contract now uses the announced configuration.

Current product pages still show two layers. Ankr Inc. contracts with customers for hosted access and tooling. The ANKR network design adds token-backed full-node providers and votes, but accepted governance is carried out by the team. Holding ANKR therefore supplies contract transfer rights and eligibility for documented staking and voting; it does not create a service-level agreement by itself.

The family names matter. ankrETH represents value deposited into Ethereum liquid staking; ankrBNB concerns BNB staking; bridged ANKR represents ANKR moved through a bridge. Their administrators, backing and exit paths differ. Even verifiable RPC has a stated boundary: signed HTTP results and a cloud-checked hardware quote are covered, while WebSocket streams, some off-chain reads and fully local attestation are not. The product is becoming easier to verify, but verification still has a perimeter.