#storage

Read Tezos's on-chain key-value storage (bigmaps) live from the public TzKT indexer — no key. A bigmap is Tezos's lazily-deserialised on-chain map: the data structure smart contracts use for the big stuff — token ledgers (who owns what), NFT ownership, allowances and metadata. The Tezos contract explorer lists contracts and their interface, but it cannot browse the bigmaps themselves, read a bigmap's typed key/value schema, or page through its live key-value entries. This opens that. Browse and rank the bigmaps by size with their pointer, owning contract, path (e.g. "ledger"), tags and total/active key counts; read one bigmap's detail and its typed key/value schema (what shape each row's key and value take, e.g. an address-to-nat token ledger); and page through a bigmap's live key-value entries — the actual on-chain data, such as the address-to-balance rows of a token ledger or the owner rows of an NFT collection. The storage / data layer for Tezos explorers, indexers, token dashboards and analytics. Distinct from the Tezos on-chain reader (account state), the smart-contract explorer, the FA-token registry and the .tez naming reader. Live from the indexer; short cache only.

api.oanor.com/tezosbigmaps-api

The Arweave permaweb — the pay-once-store-forever blockchain — live from the public Arweave gateway, no key, nothing cached. On Arweave you pay a single up-front fee and your data is stored permanently; this is the first Arweave reader in the marketplace. Quote the permanent storage cost for any data size — in winston, AR and US dollars — so apps can show "store this forever for $X" for anything from a 1 KB record to a 1 TB archive (AR/USD priced live). Read the live network info: the weave height, total block count, the number of connected peers and the running node version. And look up any block by height for its independent hash, previous block, timestamp, transaction count and the miner reward pool (in AR). The storage-and-network layer for Arweave wallets, permaweb apps, archivers and analytics. Live from arweave.net.

api.oanor.com/arweave-api

Read any smart contract's raw EVM storage live via the chain's public JSON-RPC, decode each 32-byte word as an address, uint or bool, and resolve proxy implementation pointers across every common proxy standard — EIP-1967, EIP-1822/UUPS and the legacy OpenZeppelin/zeppelinos slot, plus beacon proxies. This is how you find out what a proxy actually points to, who its admin is, or what a contract is storing — even for unverified contracts where source and ABI are unavailable. Give it a chain and an address: read one slot, scan the first N slots to peek at the state layout, or auto-resolve the proxy implementation. The on-chain state-inspection layer for auditors, upgrade monitors and security tooling, across Ethereum, Base, Arbitrum, Optimism, BNB, Polygon and more. Live, short cache only.

api.oanor.com/storageslot-api

Live on-chain data from the Filecoin network (FIL), the decentralized storage blockchain where miners are storage providers that pledge real disk capacity: an address's FIL balance, actor type and message count — and, for a storage provider, its raw and quality-adjusted storage power and sector size; storage providers ranked by power with each one's capacity, blocks mined and rewards; a tipset (Filecoin's block) with its height, time, block count and messages; and the chain height, total network storage power and number of active storage providers.

api.oanor.com/filecoin-api

Cigar-humidor maths as an API, computed locally and deterministically — the numbers behind storing cigars right, so you buy the correct humidor and keep it at the perfect humidity. The capacity endpoint works out how many cigars an interior holds: interior volume × a packing efficiency ÷ one cigar's volume, where a cigar is a cylinder of its ring gauge (in 64ths of an inch) and length — a 9 × 7 × 3 inch interior holds about 40 Toros (ring 50, 6 inch) at a realistic 0.62 packing, leaving room for air and a humidification device. The media endpoint sizes the humidification: about one 60 g two-way pack per 25 cigars, replaced roughly every two months, so a 40-cigar humidor wants two packs. The seasoning endpoint covers a brand-new humidor — its Spanish cedar must absorb moisture for about two weeks at 84 % RH (one seasoning pack per 25-cigar capacity, or the distilled-water wipe-down) before any cigars go in, or the dry wood will rob them. Everything is computed locally and deterministically, so it is instant and private. Ideal for cigar-shop and tobacconist apps, humidor-maker product pages, cigar-aficionado and collection-tracker sites, and buying guides. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. For room humidity or dew point use a psychrometric API.

api.oanor.com/humidor-api

Grain-bin storage maths as an API, computed locally and deterministically — the bushel and weight numbers a farmer or elevator sizes storage by. The bushels endpoint measures a round bin: floor area × grain depth gives the cubic feet, and a cubic foot holds about 0.8036 bushels, so an 18-foot bin filled 20 feet level holds roughly 4,090 bushels — and grain heaped to a peak adds a cone of (1/3) × floor area × peak height, so a 4-foot peak adds about 270 more. The weight endpoint converts bushels to weight by the crop’s standard test weight — corn and sorghum at 56 pounds a bushel, wheat and soybeans 60, oats 32, barley 48 — so those 4,090 bushels of corn weigh 229,040 pounds, about 114.5 US tons or 104 tonnes; pass a measured test weight for light or heavy grain. Everything is computed locally and deterministically, so it is instant and private. Ideal for agriculture, grain-elevator, farm-management and ag-tech app developers, storage-capacity and inventory tools, and harvest software. Pure local computation — no key, no third-party service, instant. US units (feet, bushels, pounds). Live, nothing stored. 2 compute endpoints.

api.oanor.com/grainbin-api

RAID storage-array maths as an API, computed locally and deterministically. The capacity endpoint computes the usable and raw capacity, the storage efficiency and the fault tolerance of a RAID level — RAID 0 stripes for n×disk with no redundancy, RAID 1 mirrors to one disk and tolerates n−1 failures, RAID 5 gives (n−1)×disk with one-disk tolerance, RAID 6 gives (n−2)×disk with two-disk tolerance, and RAID 10 gives (n/2)×disk — and reports the minimum disks each level needs. The compare endpoint lays the levels side by side for the same disks and disk size so you can weigh capacity against redundancy. The rebuild endpoint estimates how long it takes to rebuild a single disk at a given rebuild speed, the window during which a second failure would lose data in RAID 5/6. Everything is computed locally and deterministically, so it is instant and private. Ideal for storage, NAS, server and IT-admin app developers, capacity-planning and procurement tools, and homelab calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is RAID array sizing; for data-transfer time use a transfer API.

api.oanor.com/raid-api