Blocknative

• Name: Blocknative
• URL: https://www.blocknative.com/
• Category: fee-market data company / gas-estimation operator / residual-service shutdown note
• Tags: bitcoin-ecosystem ethereum-ecosystem
• Summary: Blocknative belongs in companies/ because the practical dependency was never a neutral gas primitive. It was one named operator publishing gas heuristics, deciding which chains and probability bands to support, running the API and docs surface wallets and protocols integrated against, and packaging the offchain agent workflow behind Gas Network’s onchain oracle story. That entity boundary matters even more after the 2026 transition notice: Blocknative says the team joined Deloitte, Blocknative Corporation is ceasing operations, the API services were sunset in June 2026, and Gas Network ceased with them. The useful question is not just what gas product existed? but which operator controlled fee truth, and what happened when that operator shut the service down?
• What it did:
  • Sold real-time gas estimation and probability-based inclusion data to wallets, apps, and chains across Ethereum, Bitcoin, and many L2s
  • Published a docs and API surface that downstream teams could treat as production fee-selection infrastructure rather than as a consumer dashboard
  • Extended the same operator shell into Gas Network, where offchain gas agents generated predictions and onchain oracles published aggregated gas data
  • Ran user-facing gas-estimator and extension surfaces that reinforced Blocknative as a fee-market interpretation layer rather than only a backend vendor
  • Announced in 2026 that the Blocknative team joined Deloitte, that Blocknative Corporation was ceasing operations, that the Blocknative APIs would stop responding after the June 2026 sunset, and that Gas Network would cease on the same schedule because it depended on those APIs
• Key claims:
  • The earlier docs said Blocknative delivered 600+ gas estimates per second, supported dozens of chains, and exposed probability-based fee estimates rather than one static quote, which is why the product mattered as an operator-run fee truth layer for downstream software
  • The Gas Network materials described a dedicated aggregation chain, offchain gas agents, and onchain gas oracles, but the later shutdown notice makes clear that this was still not an independent neutral protocol surface; it depended on Blocknative’s API and operator shell
  • The August 2026 announcement says the Blocknative team joined Deloitte and that Blocknative Corporation is now in the process of ceasing operations, which is the cleanest primary-source statement that the entity boundary itself changed materially
  • The same announcement says the Blocknative API services were winding down and that Gas Network would cease on the same schedule because it depended on those APIs, which is analytically important because it collapses any lingering maybe the network is separate ambiguity
  • The practical lesson is company-shaped: when wallets, apps, or chains imported Blocknative fee guidance, they were importing one operator’s publication cadence, support window, and shutdown risk, not a durable public-good oracle layer
• Whitepaper: No standalone company whitepaper is the point here. The useful primary materials are the earlier product snapshot in ../whitepapers/blocknative-primary-sources-2026-04-26.md plus the later shutdown-and-transition capture in ../whitepapers/blocknative-transition-announcement-2026-08-08.md.
• Sources:
  • https://www.blocknative.com/
  • https://www.blocknative.com/blog/deloitte-announcement
  • ../whitepapers/blocknative-primary-sources-2026-04-26.md
  • ../whitepapers/blocknative-transition-announcement-2026-08-08.md

Internal linkages

• Alias note for legacy project placement: blocknative.
• Best adjacent operator reads: quicknode, bloxroute, and chainstack.
• Closest product-layer contrast: chainlink-data-streams when the question is an actively distributed data product rather than a now-shuttered company-run fee surface.

Protocol / company boundary

• Keep Blocknative in companies/ because the important historical dependency was the named operator that published gas predictions, ran the API, chose supported networks, and packaged the Gas Network agent/oracle workflow.
• The shutdown notice makes the taxonomy point sharper, not weaker: if Gas Network ceases when the Blocknative APIs cease, the durable control surface was the company boundary all along.
• Keep blocknative only as an alias so existing links continue to resolve without pretending Blocknative was a neutral protocol primitive.

Control surface

• Practical leverage sat in gas-model selection, probability-band presentation, chain-support policy, API availability, docs and integration guidance, and the operator-run path from offchain predictions to onchain publication.

• Practical residual risk now sits in deprecation and migration history: teams that treated Blocknative as fee truth inherited one vendor’s shutdown timeline, and Gas Network’s cessation shows how thin the separation between network and company service really was.

• Read Blocknative first as a company-run fee-publication and delivery boundary, and only second as a gas-oracle brand.

• Last reviewed: 2026-08-08 UTC