Skip to main content

Numbers Protocol

Numbers Protocol — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).

Numbers Protocol — an Infra / Provenance / Payments project (a provenance/receipts rail) with its own L1 (Numbers Mainnet); token: NUM.

Disclaimer

Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.

TL;DR (for readers who are not into AI)

  • What it is: an onchain registry and a product suite for a verifiable “provenance chain” (capture → certify → check) for digital/physical assets and media.
  • Who it’s for: creators/platforms/businesses, integration developers, verification providers (validators/“witness nodes”).
  • Why onchain/token: onchain records a non‑rewritable history of events/receipts, while NUM is used as a fee/collateral for records and for staking by network participants (payments for content — in stablecoins).

How it works (very briefly)

  1. The user does: captures/registers an asset (a file, an event, a “digital twin”) or performs an access/license transaction.
  2. The system does: generates a proof (including C2PA metadata) and a check/receipt, and appends a new “append‑only” element to the history.
  3. The user gets: a verifiable provenance chain and receipts of usage/payment that a third party can verify.
  4. Where the blockchain is: a “public index”/registry on Numbers Mainnet (ERC‑7053 is also mentioned as the indexing standard), plus staking/slashing of network roles.
  5. Token role (if any): NUM pays for records/“write fees” and is used for staking/validation and governance; content settlements — in stablecoin.

Quick links: AI thesis fit

Project passport

Field Value
Project name Numbers Protocol
Also known as (aliases) Numbers, NUM
Logo (logo) ../assets/167_numbers-protocol_logo.svg
Token symbol (ticker) NUM
Category Infra | Provenance | Payments
Primary chain (chain) Numbers Mainnet
Type Appchain
Network status mainnet
Consensus (consensus) —
Launch date (launch_date) —
Project status (status) active
Token (standard) native
Token contract Ethereum: 0x3496b523e5c00a4b4150d6721320cddb234c3079
Token model (token_type) utility (payments + staking + governance)
Max supply 1,000,000,000 NUM (total supply)
Issuance fixed (per total supply)
Tokenomics (tokenomics, brief) NUM is needed for ERC‑7053 write fees and for validator/witness staking; settlements for assets — in stablecoin
Governance governance via staked NUM (SIPs / voting)
Admins/keys —
Audit yes (a CertiK audit report is mentioned; via IPFS in the docs)
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) provenance rail for AI agents/licensing (not an AI model)
Use‑case (use_case) receipts/provenance (capture → certify → check)
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 1 / 3 / 3 / 3
Last verified 2026-02-11

General project overview

Numbers Protocol positions itself as “provenance infrastructure for humans & AI”: a set of tools and a protocol that make it possible to record the origin and usage history of an asset (a file/content/a physical asset) so that the record is verifiable and appendable (append‑only) rather than “rewritable after the fact”. The focus is on scenarios: “per request” licensing/access (x402, HTTP‑402 micropayments are mentioned) with stablecoin payment and issuance of an onchain receipt, plus integration with C2PA metadata.

Note on networks (passport normalization): the passport lists Numbers Mainnet (mainnet) as the primary chain. Mentions of the testnet (Snow) and of ERC‑20 representations of the token on EVM networks remain in the text/links as context.

Features/modules

  • Capture → Certify → Check: a product “pipeline model” for registering and subsequently enriching an asset’s history.
  • C2PA content credentials: mentioned as a proof/metadata layer in files.
  • Onchain index / receipts: Numbers Mainnet and ERC‑7053 are mentioned as the history indexing standard.
  • Witness nodes / staking: a model of third‑party witnesses with a NUM stake (and slashing risk) for the physical world.
  • Stablecoin settlement: settlements in stablecoin (USDC/USDC.n in the description); the NUM token — for protocol fees and network roles.

Typical scenarios

  • Scenario 1 (content/data): a buyer (a human or an agent) pays in stablecoin “per request” → receives a file/API response with a C2PA proof and an onchain receipt → a third party verifies the history.
  • Scenario 2 (physical asset): a hand‑over/inspection takes place → a witness node records/signs the event and appends a record → a verifiable chain of events emerges for audits/disputes.
  • Scenario 3 (validator/operator): a participant stakes NUM → takes part in maintaining the network/receipts → receives rewards according to the protocol rules.

Getting started (wallet/network)

  • What you need: an EVM wallet for NUM on Ethereum/BNB or access to Numbers Mainnet (depending on the role).
  • Network/chain: Numbers Mainnet (Jade) and/or Ethereum/BNB (for ERC‑20 NUM).
  • Fees: payments for content/access are claimed to be in stablecoin; protocol records (ERC‑7053 write fees) — in NUM.

Architecture/tech (non‑AI)

  • Components: the product platform + Numbers Mainnet (ledger/index) + proof standard(s) (C2PA) + onchain receipts/indexing (ERC‑7053 is mentioned).
  • Participant roles: users/integrators; validators; witness nodes (witnesses) for the physical world.
  • Where logic runs: verification/signing and proof generation may be offchain, while the registry/receipts are onchain (Numbers Mainnet).
  • Dependencies: stablecoin infrastructure (USDC/USDC.n in the description), bridges for NUM between networks (Chainport is mentioned), external standards (C2PA, x402).

Token/economics (expanded, no forecasts)

  • Token utility: NUM is used as a “work token” for ERC‑7053 write fees and for staking by validators/network participants; governance — via staked NUM.
  • Protocol necessity drivers: records in the public index/registry and the security of network roles (staking/slashing) are tied to NUM.
  • Who pays fees: users/integrators — for creating onchain records; participants — for the stake.
  • Where fees go: rewards to active roles/fee pools and the distribution parameters are managed by governance (the whitepaper describes roles/pools; specific contract addresses/fee distribution specs were not found in the reviewed Tier‑1 sources).
  • Issuance/burn: total supply 1,000,000,000 NUM (fixed).
  • Security/incentive mechanisms: staking for validators/witnesses; slashing for misbehaviour/downtime is mentioned.
  • Distribution and token issuance schedule: — (not found explicitly in the studied Tier‑1 pages).
  • Treasury: — (not found explicitly in the studied Tier‑1 pages).

Governance

  • Who makes decisions: token holders via staked NUM (governance is described as a function of NUM).
  • How protocol parameters change: via the governance process (the whitepaper lists the areas: fee schedules, validator SLAs, slashing, treasury allocations, etc.).
  • Where decisions are discussed/made: the process and rules of the Numbers DAO are described in the official documentation; voting results are published on the official blog (see the Tier‑1 sources in Evidence).
  • Keys/multisig: —.

Security and incidents

  • Audits: the docs publish a page with a link to the “NUM Token Audit Report from CERTIK” (via IPFS).
  • Bug bounty: —.
  • Incidents: — (no public Tier‑1 postmortems/incidents were found in the reviewed sources).
  • Threat model: integrity risks of “oracle‑like” claims about the physical world (witness nodes), key/contract management risks, bridge risks for NUM between networks.

Project status and timeline

  • Current status: the documentation describes Numbers Mainnet (Jade) and Numbers Testnet (Snow) and the token contracts on Ethereum/BNB.
  • Key releases/milestones: —.
  • Roadmap: published in the docs (see links_*).

Ecosystem/integrations

  • Integrations: C2PA; micropayment standards/scenarios (x402); bridges for NUM (Chainport is mentioned).
  • Partners: —.
  • Where it’s actually used: the whitepaper provides cases/examples of the pipeline; specific production integrations in the form of a “list of clients/partners” are not recorded in the reviewed Tier‑1 sources.

AI component of the project

  • What is real AI here? The project is primarily about provenance/receipts. “AI” appears as a target consumer (AI agents) and as a data licensing/payment scenario, not as an in‑house ML model.
  • What is truly onchain? The registry/indexing of history (Numbers Mainnet; ERC‑7053 is mentioned), plus staking/slashing of network roles and the issuance of receipts/records.
  • Why is a token needed? NUM is a work token: “gas” for records/indexing and economic collateral for validators/witnesses, as well as governance.
  • Red flags (based on the information found): AI‑washing (if one tries to interpret it as an “AI project”); what to double‑check — the actual implementation of Numbers Mainnet/7053/receipts and the live contracts of network roles; key risks — a shift of focus from provenance to “AI marketing”.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality low 1
Onchain necessity high 3
Token necessity high 3
Evidence Tier‑1 present 3
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 1
  • Claim (one line): the project positions itself as provenance infrastructure for “humans & AI” and for “agentic economy” scenarios.
  • Evidence: Tier‑1 — https://whitepaper.numbersprotocol.io/
  • Why sufficient / why not (one line): this confirms the AI orientation of the scenarios but does not prove the presence of in‑house ML models/training in the product.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): an in‑house AI module/ML model is not described in Tier‑1 sources as part of the product.
  • Evidence: Tier‑1 — https://whitepaper.numbersprotocol.io/
  • Why sufficient / why not (one line): the whitepaper describes provenance/receipts/payments, but not a specific AI function (inference/training) inside the protocol.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): a demo specifically of an AI module is not recorded within the verified Tier‑1 sources.
  • Evidence: Tier‑1 — https://whitepaper.numbersprotocol.io/
  • Why sufficient / why not (one line): the existence of a product/SDK does not equal a demonstration of the AI part.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://whitepaper.numbersprotocol.io/
  • Why sufficient / why not (one line): there are no claimed quality metrics of an AI model, since an AI model as a component is not confirmed.
  • Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

  • AI_4 (decision): 0
  • Claim (one line): the technical description concerns provenance/the registry/payment scenarios, not an AI architecture.
  • Evidence: Tier‑1 — https://whitepaper.numbersprotocol.io/
  • Why sufficient / why not (one line): there is no AI architecture (model/datasets/inference) as a verifiable part of the system.
  • Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

  • OC_1 (decision): 1
  • Chain: Numbers Mainnet (Jade), Ethereum, BNB Chain
  • Addresses/identifiers: ERC‑20 NUM (Ethereum): 0x3496b523e5c00a4b4150d6721320cddb234c3079; ERC‑20 NUM (BNB): 0xeceb87cf00dcbf2d4e2880223743ff087a995ad9
  • Evidence: Tier‑1 — https://docs.numbersprotocol.io/introduction/num-token/ ; https://etherscan.io/token/0x3496b523e5c00a4b4150d6721320cddb234c3079
  • Why sufficient / why not (one line): the docs publish the networks and the token contracts; this is a verifiable onchain anchor.
  • Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

  • OC_2 (decision): 1
  • What useful logic is onchain: onchain receipts/“public index” (ERC‑7053 writes), staking of validators/witnesses, distribution of flows in stablecoin scenarios on Numbers Mainnet.
  • Evidence: Tier‑1 — https://whitepaper.numbersprotocol.io/
  • Why sufficient / why not (one line): onchain is used as a registry and as an economic security layer for network roles, not just as a “token on Ethereum”.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without onchain, the property of a publicly verifiable, immutable (append‑only) history and the independent audit of receipts/events are lost.
  • Evidence: Tier‑1 — https://whitepaper.numbersprotocol.io/
  • Why sufficient / why not (one line): the “receipt rail” and the public index are claimed as the basis of value; a centralized registry breaks trusted verification.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, NUM.
  • Evidence: Tier‑1 — https://docs.numbersprotocol.io/introduction/num-token/
  • Why sufficient / why not (one line): the token is explicitly described as native to the protocol.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): NUM is needed for ERC‑7053 write fees (the protocol fee for records/proofs).
  • Evidence: Tier‑1 — https://whitepaper.numbersprotocol.io/
  • Why sufficient / why not (one line): the whitepaper directly links the recording of provenance/receipts to the consumption of NUM as a fee.
  • Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

  • TK_2 (decision): 1
  • Claim (one line): participants (validators/witness) stake NUM and can be penalized by slashing.
  • Evidence: Tier‑1 — https://whitepaper.numbersprotocol.io/
  • Why sufficient / why not (one line): the whitepaper describes staking as a mechanism of security and discipline for the roles.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): staked NUM grants governance rights (fee parameters, validators, slashing, treasury, etc.).
  • Evidence: Tier‑1 — https://whitepaper.numbersprotocol.io/
  • Why sufficient / why not (one line): governance is described as a utility of NUM.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): per the Tier‑1 description, NUM is built into protocol fees/staking/gov; replacement with “any currency” is not described.
  • Evidence: Tier‑1 — https://whitepaper.numbersprotocol.io/ ; https://docs.numbersprotocol.io/introduction/num-token/
  • Why sufficient / why not (one line): the model is built around a separation: stablecoin for settlements and NUM for “provenance gas” and security.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://whitepaper.numbersprotocol.io/ The Capture → Certify → Check model; the role of onchain (Numbers Mainnet/append‑only index), the role of NUM (fees/staking/gov), stablecoin settlement
Tier‑1 https://docs.numbersprotocol.io/introduction/num-token/ Total supply 1B; NUM networks/contracts (Numbers Mainnet, Ethereum, BNB) and purpose (secure mainnet, incentives)
Tier‑1 https://docs.numbersprotocol.io/introduction/numbersdao/governance-and-voting-rules-v2.0 Rules/process of the Numbers DAO (governance), including the discussion and voting stages
Tier‑1 https://www.numbersprotocol.io/blog/the-5th-numbers-dao-meeting-voting-result An example of publishing Numbers DAO voting results (official blog)
Tier‑1 https://docs.numbersprotocol.io/introduction/num-token/audit-report The presence of a link to the CertiK audit report (via IPFS)
Tier‑1 https://etherscan.io/token/0x3496b523e5c00a4b4150d6721320cddb234c3079 Verification of the NUM ERC‑20 contract on Ethereum and of the max supply on the explorer

No comments to display

Back to top