CCJV Whitepaper — The Federated ERP Core

CCJV — the federated ERP core for the Omnichain ecosystem. Version 1.0, October 2025.

Download this whitepaper as a PDF

Abstract

CCJV is the federated enterprise core of the Omnichain ecosystem: a shared set of business modules — customer relationship management (CRM), human resource management (HRM), project management (PMP), Internet of Things (IoT) device and reading management, Calendar, and accounting — operated centrally at ccjv.ca and consumed by every sector ERP in the ecosystem. Access is controlled by utility-token holds, not by payments that move funds: a business binds its own Avalanche wallet to its account by signing a challenge (proving ownership without giving up custody), and module subscriptions activate against the wallet’s verified on-chain balance. Holds are enforced continuously — if the wallet disconnects or its balance falls below a module’s requirement, access to that module pauses until the hold is restored. This paper describes the problem CCJV addresses, the platform, its token and utility model, its architecture on Avalanche C-Chain, its tokenomics, the ecosystem journey it completes, its security and custody model, its current verified status and roadmap, and its risks.

1. Introduction & Problem

Small and mid-sized businesses run on disconnected software: one subscription for customer records, another for staff, another for projects, another for bookkeeping — each with its own login, its own billing, and no shared picture of the business. Sector-specific tools repeat the same core modules again and again, so a business operating in more than one sector pays for the same CRM, HRM and project tooling several times over, and its data stays fragmented across all of them.

At the same time, conventional subscription billing is a poor fit for access control. Payments are collected whether or not the customer still qualifies or still uses the service; access rights live in a vendor’s database and can be changed unilaterally; and there is no public, verifiable record of who is entitled to what.

CCJV takes a different approach: one shared core, operated once and consumed by every sector ERP; access rights expressed as token holds in the customer’s own wallet, verifiable on a public chain by anyone; and activation state shared across the federation, so a business’s entitlements follow it from one sector ERP to the next.

2. The Platform

CCJV operates the core modules centrally. Each module is a working business tool with tenant-scoped records — one business’s data is never visible to another:

  • CRM — contacts and customer records for the tenant business.
  • HRM — employee records for the tenant business.
  • PMP (Project Management) — projects and their tasks, owned by the tenant.
  • IoT — device registry and readings, with a live fleet summary per tenant.
  • Calendar — the tenant’s events and schedule.
  • Accounting — a double-entry-style journal for the tenant’s books.

Alongside the modules, the core provides the facilities every ERP shares: a module launcher, a per-user dashboard, asset records, and a document vault whose records are SHA-256 hashed and queued for anchoring on Avalanche C-Chain (hashes only — the underlying records are never placed on-chain).

Federation. Every sector ERP in the Omnichain ecosystem runs the same CCJV core provider. The core modules come from the hub; a sector ERP contributes only its own sector-specific modules, which it registers with the core. A business that binds its wallet and subscribes on one ERP is recognised across the federation: module activation state is shared between the hub and the sector ERPs, so the same verified hold unlocks the core wherever the business works.

Wallets and subscriptions. A user connects a self-custody Avalanche wallet (for example MetaMask) and binds it to their account by signing a one-time challenge message. The signature proves wallet ownership; the platform never sees, asks for, or stores a private key or recovery phrase. Subscribing to a module then works as follows: the platform verifies the wallet’s live on-chain CJV balance; if the balance meets the module’s requirement, the subscription activates for 30 days. No tokens are transferred, deducted, or escrowed — the tokens stay in the user’s wallet for the entire subscription.

3. Token & Utility Model

The CCJV token is CJV (contract 0x02E7769903c7069A909bc951D297d9D2F504393B on Avalanche C-Chain). CJV is a utility token: it is the access key to the ERP core.

  • Entry gate: holding at least 1 CJV in a signature-verified bound wallet unlocks the ERP.
  • Module subscriptions: each core module requires a hold of 1 CJV for each month of activation. Activation verifies the hold; it never moves the tokens.
  • Continuous enforcement: the hold is the subscription. If the wallet is disconnected or its balance falls below a requirement, the affected access pauses until the hold is restored.
  • Utility price: at the ecosystem treasury, 1 token = 1 AVAX — a fixed pricing convention for access, used across all 39 ecosystem tokens.
  • Earned for participation: ecosystem tokens are earned through verified participation (for example, Omnichain receipt mining) and held for access or spent on services. They are not offered as investments, and nothing in this paper is a promise of profit or return.
  • ERP referrals: CJV is also the ecosystem’s ERP referral token. When a business referred into the ecosystem subscribes to its first module, that first subscription is the referral event recognised by the core.

4. Architecture

CCJV runs on Avalanche C-Chain (chain ID 43114) and is delivered as a WordPress-based hub at ccjv.ca plus the CCJV Unified Core provider, a plugin installed on the hub and on each sector ERP site. The provider supplies:

  • The 39-token registry — the ecosystem’s token contracts, used for balance verification and gate evaluation on every site.
  • Signature-verified wallet binding — a server-issued, single-use challenge (10-minute expiry) that the user signs with their wallet; the platform recovers the signing address from the signature and binds only on an exact match. Verified binding automatically provisions the user’s tenant workspace on that ERP.
  • Hold-verified subscription activation — balances are read live from the chain (the ecosystem’s balance service where present, otherwise a direct read against the public Avalanche RPC), cached briefly, and checked at activation and continuously thereafter.
  • The module and workspace data layer — workspaces, module catalogue, sector-module registrations, subscriptions, wallet bindings, and the journal live in the site’s database, tenant-scoped throughout.
  • The core screens — CRM, HRM, PMP, IoT, Calendar and Accounting screens, the launcher, and the dashboard, rendered by the platform layer. Access enforcement lives in the core, behind the presentation layer: changing a site’s theme never changes its gate behaviour.

Records created in the modules are SHA-256 hashed and queued for anchoring on Avalanche C-Chain, making tenant records auditable and tamper-evident by design.

5. Tokenomics

The ecosystem comprises 39 utility tokens on Avalanche C-Chain — one per sector, plus the core and market tokens (full list: omnichain.ca/tokens). Each token has a supply of 15 trillion. Distribution is by participation: tokens are earned for verified activity in the ecosystem (mining, referrals, and sector participation), acquired at the treasury’s fixed utility price of 1 token = 1 AVAX, or traded between holders on XMarkets. CJV’s role in that set is specific: it is the core/ERP token — the hold that gates the shared business modules on every ERP, and the token in which ERP referrals are recognised.

6. Ecosystem & the Customer Journey

CCJV is one leg of a single journey the three platforms support end to end:

  1. Open a Kraken account through the ecosystem invite link and buy AVAX.
  2. Set up MetaMask and move the AVAX onto the Avalanche network.
  3. On XMarkets, buy XMA, CJV and OMC directly from the treasury at the fixed utility price.
  4. On Omnichain, mine tokens by uploading bills and receipts (holding OMC opens uploads).
  5. On CCJV, bind the wallet and subscribe to the core modules — the CJV bought at step 3 is the hold that unlocks them.
  6. Return to XMarkets to swap between ecosystem tokens at the fixed 1:1 treasury rate.

A step-by-step walkthrough of the full journey is published as the Getting Started guide at ccjv.ca/guide/.

7. Security & Custody

  • Self-custody throughout. Users hold their own keys in their own wallets. CCJV never takes custody of tokens, and module holds never move tokens at all.
  • No private keys on servers. No private-key material exists in the platform’s code, plugins, or web space — ever. Wallet verification is public mathematics only: a signature is checked against the address it claims, and balances are read from the public chain.
  • Binding proves ownership. An address typed into a form proves nothing, so the platform does not accept it: binding requires a valid signature over a fresh, single-use challenge. Unbinding a wallet pauses its access immediately.
  • Tenant isolation. Module records are scoped to the tenant workspace provisioned at binding; one business cannot see another’s data.
  • Hash-only anchoring. Only SHA-256 hashes of records are queued for on-chain anchoring — never the records themselves.

8. Status & Roadmap

Live and verified today (25 October 2026):

  • The CCJV Unified Core provider is live on the hub (ccjv.ca) and on the first sector ERPs, including workersfirst.ca and itercoin.ca, with the full 39-token registry on each.
  • Signature-verified wallet binding, automatic tenant provisioning, hold-verified module activation, and continuous enforcement have been exercised end to end with a real wallet holding CJV: CRM, HRM, IoT and Calendar subscriptions activated against the hold, and tenant-scoped records created in each module.
  • The hub journey leg is proven: a customer arriving at ccjv.ca holding CJV can bind and subscribe with no other token and no extra step.

Underway: federation of the remaining sector ERPs to the hub in paced stages; completion of every core module to full commercial grade, including a purpose-built per-user dashboard showing each holder’s active gates, subscriptions and balances on every ERP; and project participation panels in sector ERPs. This section states only what is live and verified; planned items are labelled as such.

9. Risks

Participation involves real risks — including market, custody, smart-contract, and regulatory risks — which are set out plainly in the Investment Risk Disclosure. Read it before participating.

10. Disclaimer

CJV and the other Omnichain ecosystem tokens are utility instruments: they are earned through participation, held for access to platform features, and spent on services. They are not investments, securities, or financial products, and nothing in this paper or on ccjv.ca is financial advice, an offer, or a promise of profit or return. The fixed 1 token = 1 AVAX treasury price is a pricing convention for access, not a guarantee of market value. This paper describes the platform as it operates today; features described as underway are not yet live.

Privacy Statement · Investment Risk Disclosure