Whitepaper
Omnichain — Whitepaper. Published 2026-10-25 at omnichain.ca. Download this whitepaper (PDF).
Abstract
Omnichain turns everyday spending into verified digital participation. A participant uploads a bill or receipt; the document is read by optical character recognition, checked for fraud signals, hashed with SHA-256, and the hash is anchored on the Avalanche blockchain. The amount scanned allocates token units across the ecosystem’s 39 sector tokens — one token unit per dollar scanned — and the resulting rewards are paid automatically, in batches, from the ecosystem treasury, which also pays the network gas. The tokens are utility instruments: they are earned for verified participation, held to unlock platform features through token gates, and spent on services. Holding is what the gates check — nothing is spent or transferred to pass a gate. This paper describes the platform, the token model, the architecture, the tokenomics, the wider ecosystem a participant moves through, the security and custody model, what is live and verified today, and the risks, which are set out in full on the Investment Risk Disclosure page.
1. Introduction & problem
Every household and business produces a steady stream of documented economic activity: utility bills, fuel receipts, grocery and supply invoices, telecom statements. That documentation proves real participation in the economy, yet it has never been usable as a credential. At the same time, most digital token systems distribute their tokens by sale or by hardware mining — both of which reward capital rather than participation.
Omnichain starts from the document. If a real bill can be read reliably, checked against duplication and fabrication, and tied to a public, tamper-evident record, then the spending it proves can serve as the basis for earning tokens and for unlocking services — without buying tokens first and without specialized hardware. The platform’s job is to make that chain of proof trustworthy: read the document accurately, refuse the fraudulent ones, anchor the evidence publicly, and pay what the rules say, automatically.
2. The platform
Omnichain is a receipt- and bill-mining platform built on WordPress with a dedicated mining plugin, live at omnichain.ca. The mining loop, as it operates today:
- Connect and verify. The participant connects a self-custody wallet (MetaMask) and proves ownership by signing a message. No private key or recovery phrase ever touches the site.
- Upload gate. Uploading requires the connected wallet to hold at least 1 OMC, checked live against the blockchain. The token stays in the wallet; the gate is a hold, not a payment.
- Upload and OCR. The participant uploads a bill or receipt image. The document is processed by optical character recognition (OCR.space) to extract the vendor, the total amount, and the tax paid.
- Fraud review. Each document is scored for fraud signals — exact-duplicate file hashes, repeated vendor/amount patterns, implausible values. Clean documents proceed automatically; flagged documents are held for review and earn nothing until cleared.
- Hashing and vault storage. The stored copy of the document is hashed with SHA-256 and kept in an access-controlled vault on the server. The document itself is never placed on a blockchain.
- Anchoring. The document’s SHA-256 hash is anchored in a transaction on the Avalanche C-Chain, creating a public, timestamped proof that this exact document was processed. Anyone can re-hash the document and compare.
- Allocation. The scanned amount creates allocation records across the 39 sector tokens under the model in Section 3.
- Automatic batched payout. Allocation records are claimed and paid automatically by a payout worker, netted and batched into efficient on-chain transfers from the treasury. The treasury pays all gas; participants need no AVAX to receive rewards. Every payout is a public on-chain transfer.
The participant’s dashboard shows their verified wallet, their token gates with live states, their uploaded documents and scan history, their allocations, and their payouts. One part of the dashboard — the participant’s own stored documents (“memory”) — sits behind the memory gate described in Section 3.
3. Token & utility model
Utility principle. Omnichain tokens are utility instruments. They are earned for verified participation, held for access — token gates are holds, checked continuously, and nothing is spent or transferred to pass one — and spent on services inside the ecosystem. They are not offered as investments, and nothing in this paper is a promise of profit or return.
Utility price. At the treasury, 1 token = 1 AVAX. That fixed utility price is the ecosystem’s pricing convention for access and services. Community (holder-to-holder) markets price independently.
Earning: the allocation model. One dollar scanned allocates one token unit in total:
- One half of the allocation is spread equally across all 39 tokens.
- The other half is weighted toward the sectors the purchase belongs to, based on the document’s classification.
- The tax portion allocates to CIJ at 1 CIJ per $1 of tax paid.
Allocations are created only for documents that pass OCR and fraud review, and are paid automatically under Section 2. There is no per-document cap.
Holding: the gates. Two gates operate on Omnichain today, both enforced continuously — if the balance drops below the requirement, the feature pauses until the hold is restored:
- Upload gate — hold at least 1 OMC to upload documents for mining.
- Memory gate — hold at least 5 OMC to view or download your own stored documents from the dashboard. Files are served only through a checked endpoint that re-verifies the signature session, the document’s ownership, and the live OMC balance at the moment of the request; there are no direct file URLs.
Across the wider ecosystem the same pattern holds: CJV is held to unlock modules on CCJV (Section 6), and each sector platform can set gates in its own token.
4. Architecture
Chain. Everything settles on Avalanche C-Chain (chain ID 43114): document anchors, the 39 token contracts, the XMarkets settlement contract, and all payouts.
Components.
- Web platform — WordPress with the Omnichain mining plugin: wallet verification by signature, the upload pipeline, OCR orchestration, the document vault, the participant dashboard, and the administration command center.
- Off-chain processing, on-chain proof — OCR, parsing, sector classification, and fraud scoring run on the server; only SHA-256 hashes and token transfers go on-chain. No private key material exists in the web platform, its plugins, or the web root: signing happens in a separate server-side component that reads its key from a protected file outside the web root, per invocation.
- Payout engine — allocation records move through a strict lifecycle (queued → processing → paid, with a review state for anything uncertain). A record is claimed atomically before any transfer is sent, so no record can be paid twice; payouts are netted per wallet and token and executed in batches through a dedicated batch-payout contract.
- Anchoring — document hashes are submitted to the anchor contract on Avalanche; an anchor counts as settled only when its transaction is confirmed on-chain.
5. Tokenomics
- 39 tokens, one per economic sector, listed in full at omnichain.ca/tokens. OMC is the ecosystem’s main token; CJV is the core token for the ERP platform; XMA is the market token of XMarkets; FRE is the Free Assembly community token; CIJ receives the tax allocations described in Section 3.
- Supply: 15 trillion per token, issued on Avalanche.
- Distribution is by participation: tokens reach participants through mining allocations and payouts, through the treasury’s published utility-price sales on XMarkets, and through ecosystem programs. There is no yield, no staking return, and no scarcity mechanism; the model is utility, not appreciation.
- Treasury: the ecosystem treasury funds payouts and pays all gas for mining payouts. Its transfers are ordinary public on-chain transactions, and the payout ledger is public by design.
6. Ecosystem & the customer journey
Omnichain is one of three platforms that share the same 39 tokens:
- Omnichain (omnichain.ca) — mining: earn tokens by uploading bills and receipts, as described in this paper.
- XMarkets (xmarkets.ca) — the market: buy tokens directly from the treasury at the 1 AVAX utility price, list and buy community listings (3% market fee), and swap any token for any other at a fixed 1:1 with zero swap fee, paid from the exchange’s inventory. The settlement contract is 0xf89F4b169BcC2472bB3ab9Cd1B21c26b10510eF3 on Avalanche.
- CCJV (ccjv.ca) — the federated ERP core: accounting, CRM, HRM, project management, IoT, and calendar modules, operated centrally for all sector ERPs. Modules unlock by holding CJV with a signature-verified wallet binding; the hold is continuous — drop below the requirement and access pauses until restored. Each sector ERP adds its own sector modules on top of the shared core.
The standard journey ties them together: open a Kraken account and buy AVAX; set up MetaMask and move the AVAX onto Avalanche; on XMarkets buy OMC, XMA, and CJV at the treasury price; mine on Omnichain (the OMC holding passes the upload gate); subscribe to CCJV modules (the CJV holding satisfies the module gates); and return to XMarkets to swap between tokens at 1:1. The step-by-step version is the Guide page on this site.
7. Security & custody
- Self-custody throughout. Participants keep their own wallets and keys. The platform verifies wallet ownership by message signature only; it never sees, asks for, or stores a private key or recovery phrase.
- No keys in the platform. No private-key material exists in the web platform’s code or web root. Server-side signing reads a protected key file outside the web root, in-process, per invocation, and it is never printed, logged, or transmitted.
- Document security. Uploaded documents sit in a deny-all vault directory with randomized file names; the only way to retrieve one is the checked serving endpoint, which re-verifies the session, ownership, and the live memory-gate hold on every request.
- Payment safety. Payout records are claimed atomically before sending and are never automatically retried after an uncertain outcome — they are held for review instead, so a payout cannot be sent twice by the automation. Anchors and payouts are verified against confirmed on-chain state, not local assumptions.
- Public verifiability. Token contracts, the settlement contract, anchors, and payouts are all public on Avalanche and can be checked by anyone on snowtrace.io.
8. Status & roadmap
Live and verified as of 2026-10-25:
- The full mining loop on omnichain.ca: signature-verified wallet connection, the ≥1 OMC upload gate, OCR parsing, fraud review, SHA-256 vault storage, Avalanche anchoring, allocation, and automatic batched payouts with treasury-paid gas. The launch payout ledger is fully settled and public on-chain.
- The participant dashboard with live token-gate states, including the ≥5 OMC memory gate over each participant’s own stored documents, enforced both when the page renders and again when a file is served.
- XMarkets: the settlement contract is deployed and verified; treasury listings sell at the 1 AVAX utility price; community listings and 1:1 zero-fee swaps operate, with exchange inventory of 1,000,000 units per token.
- CCJV: the federated core modules (CRM, HRM, project management, IoT, calendar, accounting) are live on the hub, with hold-gated activation and sector-ERP federation verified end to end.
- The Kraken → MetaMask → XMarkets → Omnichain → CCJV journey is open end to end; the Guide on this site walks it step by step.
Roadmap, stated plainly: the sector ERP dashboards roll out under the same verified pattern — per-user dashboards with live token gates on each sector platform — and the ecosystem’s community platforms continue to connect into the same journey. No dates are promised here; features are announced when they are live and verified, not before.
9. Risks
Participation carries real risks, including market, smart-contract, custody, regulatory, and technology risks. They are set out in full on the Investment Risk Disclosure page — read it before participating. Privacy practices are on the Privacy Statement page.
10. Disclaimer
Omnichain tokens are utility instruments: they are earned through participation, held for access to platform features, and spent on services. They are not investments, securities offerings, or financial products, and nothing in this whitepaper is financial advice, an offer, or a promise of profit or return. The fixed 1 token = 1 AVAX treasury utility price is a pricing convention for access, not a guarantee of market value. This paper describes the platform as it operates on its publication date; features and rules can change, and changes will be reflected in updated publications on this site.