--- title: MinimaNode url: https://minimanode.com description: Public on-chain intelligence for the Minima mainnet. updated: 2026-10-22 network: Minima mainnet type: read-only analytics and block explorer --- # MinimaNode MinimaNode is a public, read-only intelligence surface for the **Minima mainnet**: blocks, supply, coin age, holder concentration, tokens, NFTs, scripts, and network activity, built from a complete archive and a MegaMMR node. Canonical URL: Operator: MinimaNode is run alongside the Minima More project. The underlying node and analytics engine are open source at . ## What you can do here - Browse the archive by block height, with block hash, parent, timestamp, transaction count, size, and minter. - Inspect the native MINIMA supply, UTXO set, burn total, active addresses, holder count, and token/NFT counts. - View coin-age bands and the long-term/short-term split for MINIMA or an individual asset. - Inspect holder cohorts by balance band and the UTXO value distribution. - Browse the top scripts by unspent value, with known labels where available. - Search by block height, transaction id, address, or script hash. - Read the raw analytics API directly, or use the native History and Live views. Evidence/Rill templates are optional and not required for these pages. ## What this is not - Not a wallet, custodian, exchange, bridge, or signing service. - It never asks for a seed phrase, private key, password, or wallet connection. - Not a price oracle. There are no fiat prices, candles, or trading signals. - Not a guarantee of completeness or finality for the current tip. Always check the reported heights and timestamps. ## Data model The node keeps a block archive from genesis, a MegaMMR coin commitment, and a DuckDB analytics index. The archive is the source of truth for block history. The analytics index stores derived tables and daily/snapshot aggregates. Important distinctions: - `coverage.archive.to` is the archive tip. - `index.last_height` is the last block processed into analytics. - `/api/v1/live/status.tip` is the recent-tree tip, which may be higher than both. - `index.lag_blocks` is how far the index is behind the archive. - `coverage.megammr` describes the loaded MMR; it can be older than the archive. - Token amounts are shown in their on-chain units. Native MINIMA is displayed in whole coins; token decimals are used when metadata provides them. - Minima currently has no fee market. Network "burn" is not a fee metric. - HODL bands are derived from coin age at the latest snapshot. A single page shows the latest available distribution, not a reconstructed multi-day wave. - Token names, descriptions, images, and other metadata are supplied through on-chain token records. Treat them as user-generated content, not claims by MinimaNode. ## API for agents The analytics API is read-only and currently public. The archive-backed API (`/api/v1/blocks`, metrics and historical snapshots) is complemented by the recent-tree API (`/api/v1/live/*`), which can be at a higher height. Start with: - `GET /api/v1/capabilities` — node version, modes, archive coverage, MMR, index readiness, warnings, and limits. - `GET /api/v1/catalog` — metric names, units, granularity, and descriptions. - `GET /api/v1/coverage` — archive, MMR, and live coverage summary. - `GET /api/v1/healthz` — process health only; it does not prove index freshness. Useful reads: - `GET /api/v1/blocks/{height}` - `GET /api/v1/txs/{txpowid}` - `GET /api/v1/addresses/{address}` - `GET /api/v1/tokens` - `GET /api/v1/tokens/{token_id}` - `GET /api/v1/tokens/{token_id}/media` - `GET /api/v1/tokens/{token_id}/media.bin` - `GET /api/v1/hodl-waves` - `GET /api/v1/cohorts/holder` - `GET /api/v1/utxo/distribution` - `GET /api/v1/scripts` - `GET /api/v1/scripts/{script_hash}` - `GET /api/v1/metrics/{metric}` - `GET /api/v1/live/status` — recent-tree tip, hash, timestamp and block count - `GET /api/v1/live/blocks` — recent-tree blocks - `GET /api/v1/live/blocks/{height}` — one recent-tree block - `GET /api/v1/live/txs/{txpowid}` — recent-tree transaction metadata - `GET /market/market.json` — normalized MINIMA/USD daily price and volume series `/api/v1/tokens` is a large snapshot response. Agents should cache it, avoid requesting it on every turn, and prefer the specific token endpoint when the token id is known. The API is single-process today; be considerate and do not use concurrent bulk crawls against it. ## Rules for automated agents 1. Call `/api/v1/capabilities` first and report the index height and archive tip with any answer derived from the API. 2. Cache responses for at least 60 seconds. Do not poll faster than one request per second. 3. Do not attempt to bypass authentication, rate limits, or access controls. The API is public today; that may change. 4. Do not bulk-download token metadata, media, blocks, or transaction tables. Ask for a specific height, id, or token. 5. Do not present the data as financial advice or a price. 6. Do not infer identity from addresses, scripts, or cohorts. A holder cohort is a balance band, not a person or an entity. 7. Report uncertainty: `archive`, `index`, and `MMR` can be at different heights. 8. Preserve attribution and link back to when republishing derived figures. 9. Do not upload seed phrases, private keys, or personal data to this site. 10. If a response is missing or stale, say so; do not fabricate a block, transaction, holder, or token value. ## Citation > MinimaNode, "MinimaNode: public on-chain intelligence for Minima mainnet," > https://minimanode.com, accessed YYYY-MM-DD. For machine-readable node and metric metadata, use `/api/v1/capabilities` and `/api/v1/catalog` rather than scraping this page. ## Privacy and operations MinimaNode does not require an account and does not ask visitors to connect a wallet. Standard web-server and edge logs may record request metadata for security and capacity planning. The analytics API is intended for read-only inspection; it has no wallet access and no signing capability. ## Status and contact This is an independent public service with no uptime SLA. For issues with the node, analytics engine, or source code, use the Minima More project: .