Skip to content
BranchesTags

Latest commit

 

History

1,184 Commits

Folders and files

NameName
Last commit message
Last commit date
.githooks
.githooks
 
 
.github/workflows
.github/workflows
 
 
apps
apps
 
 
brand
brand
 
 
contracts
contracts
 
 
demo
demo
 
 
docs
docs
 
 
infra/0g-kv
infra/0g-kv
 
 
ivaronix-verifier-rs
ivaronix-verifier-rs
 
 
packages
packages
 
 
screenshots/readme
screenshots/readme
 
 
scripts
scripts
 
 
seed-skills
seed-skills
 
 
skills
skills
 
 
subgraph
subgraph
 
 
test-targets/dd-batch
test-targets/dd-batch
 
 
tests/fixtures
tests/fixtures
 
 
x-post-assets
x-post-assets
 
 
.editorconfig
.editorconfig
 
 
.env.example
.env.example
 
 
.gitattributes
.gitattributes
 
 
.gitignore
.gitignore
 
 
.npmrc
.npmrc
 
 
.nvmrc
.nvmrc
 
 
.prettierignore
.prettierignore
 
 
.prettierrc.json
.prettierrc.json
 
 
BRAND.md
BRAND.md
 
 
CHANGELOG.md
CHANGELOG.md
 
 
CONTRIBUTING.md
CONTRIBUTING.md
 
 
Ivaronix_Pitch_Deck.pdf
Ivaronix_Pitch_Deck.pdf
 
 
Ivaronix_Whitepaper.pdf
Ivaronix_Whitepaper.pdf
 
 
LICENSE
LICENSE
 
 
README.md
README.md
 
 
RECEIPTS_SPEC.md
RECEIPTS_SPEC.md
 
 
SECURITY.md
SECURITY.md
 
 
da.env.example
da.env.example
 
 
docker-compose.yml
docker-compose.yml
 
 
package.json
package.json
 
 
pnpm-lock.yaml
pnpm-lock.yaml
 
 
pnpm-workspace.yaml
pnpm-workspace.yaml
 
 
tsconfig.base.json
tsconfig.base.json
 
 
turbo.json
turbo.json
 
 

Repository files navigation

Ivaronix

Private AI work. Public proof.

Every AI review leaves a signed, chain-anchored receipt — independently re-verifiable by anyone, on any machine, in 10 seconds, without an account.

Aristotle Mainnet Galileo Testnet Foundry Receipts Mainnet receipts License: MIT

Live site · Reviewer replay · Whitepaper (PDF) · Pitch deck (PDF)

What it is

Ivaronix is a cognitive infrastructure layer on 0G. It runs specialist AI reviews — contract analysis, NDA triage, legal-citation verification, term-sheet risk scanning — inside TEE-attested 0G Compute, and emits a receipt for every action that a third party can verify on a clean machine, in any of three languages, without trusting Ivaronix at all.

The receipt is the product. The model is interchangeable. The chain is the source of truth.

flowchart LR
  D["Document<br/>or task"] --> C["0G Compute<br/>TEE-attested"]
  C --> S["Signed receipt<br/>RFC-8785 + EIP-712"]
  S --> A["0G Chain anchor<br/>ReceiptRegistryV3"]
  A --> P["Public proof URL"]
  P --> V["Anyone re-verifies<br/>schema + hash + sig + chain + TEE"]
  classDef green fill:#dcfce7,stroke:#16a34a,color:#14532d
  classDef ink fill:#0a0a0a,stroke:#000,color:#fafaf7
  class D,P green
  class C,S,A,V ink
Loading

See it on chain

Home · live mainnet Receipt #14 proof page
Ivaronix home page Receipt #14 fully verified
Skill marketplace Onboarding flow
Verified skill economy 60-second onboarding

Captured live from https://www.ivaronix.xyz. Refresh with pnpm exec tsx scripts/diag/capture-readme-prod.ts.

Quick start

Three shell commands, two minutes, no wallet, no account.

# 1 · Clone and install
git clone https://github.com/Pratiikpy/ivaronix.git && cd ivaronix
pnpm install

# 2 · Verify a real mainnet receipt against the live chain — no account required
pnpm ivaronix receipt verify 66 --network mainnet
# →  ANCHORED ✓   (schema · hash · signature · chain anchor)
#    Receipt bodies for ids 66, 68, 70, 124, 126, 129, 130, 131, 134, 135 are
#    bundled in apps/cli/src/data/fixtures/receipts/ so this works on a fresh
#    clone without 0G Storage credentials.

# 3 · Add full TEE re-attestation against the live 0G Compute provider
#    (this step needs a free testnet wallet — the 0G Compute broker
#    authenticates every processResponse call against a signer key)
export IVARONIX_SIGNER_KEY=0x...   # any wallet works; faucet at https://faucet.0g.ai
pnpm ivaronix receipt verify 135 --network mainnet --tee-independent
# →  FULLY VERIFIED ✓   (5 of 5: schema · hash · signature · chain · 5 TEE attestations)
#    Receipt 135 is the most-recently anchored high-stakes 5-role bundle;
#    older receipts (66, 68, 70) may report 'broker session expired' because
#    the 0G Compute broker recycles session state. Chain-anchored proof
#    persists forever; TEE re-attestation is real-time best-effort.

That is the load-bearing claim of the product — a stranger, on a different machine, can independently re-run the chain-side checks (steps 2 above, no credentials) and (with a free testnet wallet for broker auth) the full TEE attestation (step 3).

Reviewer replay path

Every artifact below is a real on-chain record at submission time. No mocks.

Want to see Open this
Chain-side verifier on a bundled mainnet receipt (no credentials) pnpm ivaronix receipt verify 66 --network mainnet
Full 5-check verifier with TEE re-attestation (TEE-warm — anchored 2026-05-17) pnpm ivaronix receipt verify 135 --network mainnet --tee-independent
6-role audit-tier verifier (6 independent TEE attestations · older, may show broker-expired) pnpm ivaronix receipt verify 70 --network mainnet --tee-independent
Cryptographic-commitment proof (tamper detection) edit one byte in apps/cli/src/data/fixtures/receipts/rcpt_01KRV2M9...json then re-verify · expect FAIL on hash
Live product surface https://www.ivaronix.xyz
Technical whitepaper (PDF) Ivaronix_Whitepaper.pdf
Pitch deck (PDF) Ivaronix_Pitch_Deck.pdf
Receipt registry on chainscan 0xCE35aF8D75ffB24BC1671Ca9F0CF293D82737297

Faucet (testnet): https://faucet.0g.ai · roughly 0.5 OG covers an afternoon of demo runs. Cost per receipt on Aristotle mainnet: ~0.0006 OG anchor (140k gas @ 4 Gwei) plus ~0.006 OG if 0G Storage upload runs (1.6M gas, storage-backed receipts only). Pure CLI verify of an existing receipt costs nothing for the verifier.

Why this exists

Professional AI adoption is moving fast. Roughly a quarter of legal organisations now use generative AI in their day-to-day work, up from one in seven the year before (Thomson Reuters, 2025). The EU AI Act's record-keeping mandate (Article 12) enters full application on 2 August 2026 for high-risk systems (artificialintelligenceact.eu).

The default consumer AI surface gives a user no cryptographic record of which model ran, what data was touched, or whether the answer was edited afterward. The audit log, when it exists at all, is controlled by the same vendor being audited.

Ivaronix makes the audit log a public good. The receipt is signed by an on-chain identity, anchored on a public registry, and re-verifiable end-to-end with one command. The vendor cannot retroactively change what was said.

Target user. The deal lawyer scanning a contract before signing. The founder reviewing a vendor agreement. The analyst sweeping a private data room. Anyone whose work demands an AI second opinion and an audit trail other people can verify.

System architecture

flowchart TB
  subgraph Surface["Surface"]
    UI["Studio · Next.js 15"]
    CLI["CLI · ivaronix"]
    MCP["MCP server"]
  end

  subgraph Runtime["Ivaronix runtime"]
    O["Skill manifest loader"]
    K["Consensus orchestrator<br/>4 tiers · 6 roles"]
    B["Receipt builder<br/>RFC-8785 + Zod"]
  end

  subgraph OG["0G primitives"]
    R["0G Router<br/>key rotation · billing"]
    Cp["0G Compute<br/>TEE-attested inference"]
    St["0G Storage<br/>evidence + ciphertext"]
  end

  subgraph Chain["0G Chain · 8 contracts"]
    RR["ReceiptRegistryV3"]
    AP["AgentPassportINFTV2<br/>ERC-7857"]
    CR["CapabilityRegistryV2"]
    MA["MemoryAccessLogV2"]
    SR["SkillRegistryV2"]
    SP["SkillPricing"]
    SRP["SkillRunPayment"]
    SE["SubscriptionEscrowV2"]
  end

  Proof["Public proof page"]

  UI --> O
  CLI --> O
  MCP --> O
  O --> K
  K --> B
  K --> R
  R --> Cp
  B --> St
  B --> RR
  RR --> Proof
  AP --> Proof
  CR --> Proof
  MA --> Proof
  SR --> Proof
  SP --> Proof
  SRP --> Proof
  SE --> Proof
Loading

The five-step verification chain — schema → hash → signature → chain anchor → TEE re-attest — is the load-bearing claim of the whole product. Step 5 (broker.processResponse against the live 0G Compute provider) is what makes the receipt verifiable to a third party weeks after the original inference.

Canonical-hash spec in docs/HASH_FUNCTION.md. Receipt schema reference in docs/RECEIPT_SCHEMA.md.

0G primitives in use

Five live today, one on the roadmap. We do not claim integration we have not shipped.

Primitive Where Ivaronix uses it User-visible value Source
0G Chain EIP-712 typed-data anchoring on ReceiptRegistryV3 with per-agent monotonic nonces. Anchors passport mints, capability grants, memory access logs, skill registrations, subscription escrow. A verification two years from now produces the same answer as a verification ten seconds after the run. @ivaronix/og-chain
0G Compute The specialist model runs inside a TEE on 0G Compute. After the run, broker.processResponse is re-invoked from any machine to confirm attestation against the live network. verificationMethod: 'compute_sdk_process_response' is an honest claim any stranger can re-check. The load-bearing step. @ivaronix/og-router
0G Storage Encrypted blob (Burn Mode) and signed receipt JSON live on 0G Storage. Storage root recorded inside the receipt; anyone can fetch the ciphertext and confirm it matches. Evidence is content-addressed on infrastructure no single party controls — what EU AI Act Article 12 expects from a non-operator-controlled record. @ivaronix/og-storage
0G Router Routes inference to 0G Compute providers with multi-credential rotation and a three-mode failure taxonomy ('402' permanent · 'auth' permanent · '429' transient). A reviewer can read the receipt body and see exactly how the work was billed, by which provider, with which model. @ivaronix/og-router/keyring
0G Agent ID (ERC-7857) AgentPassportINFTV2 mints a soulbound INFT per agent — trust score, receipt count, violation history. Every receipt is bound to a passport tokenId. Buyers can inspect an agent's on-chain track record before purchasing a skill run. Receipt signer is recovered and matched against the passport owner on chain. AgentPassportINFTV2.sol
0G DA (roadmap) Receipt-batch dispersal once 0G ships a public DA endpoint. Schema slot og.da.batched reserved (default false); v1.1 wires it without breaking byte-equality of current receipts. High-volume archival without per-receipt anchor cost. docs/0G_DA_INTEGRATION.md

By the numbers

Refreshed against the live chain via pnpm numbers:refresh · source of truth: docs/numbers.json.

Metric Value Where to look
Receipts anchored 1737+ testnet · 148 mainnet live nextId() on V1+V2+V3
Receipt types 13 packages/core/src/types.ts
Contracts deployed 15 testnet · 10 mainnet deployed contracts
Foundry tests 227 passing cd contracts && forge test
Workspace typecheck-clean 21 packages pnpm -r typecheck
Skills (first-party + catalog) 10 + 150 = 160 seed-skills/
0G primitives integrated 5 (Chain · Compute · Storage · Router · Agent ID) per-module table above
Polyglot canonical hash 3 languages, byte-equal TS + Python + Rust, 29 vectors on every PR
Networks Galileo testnet · Aristotle mainnet chainIds 16602 + 16661

Reproduction

Tested on a clean macOS or Linux machine. Around five minutes including pnpm install.

Prerequisites

node --version    # v20.x or v22.x
pnpm --version    # 9.x or 10.x
# Foundry (optional, for the 227-test contract suite)

Replay an existing anchored receipt

git clone https://github.com/Pratiikpy/ivaronix.git && cd ivaronix
pnpm install

# Schema · hash · signature · chain anchor (no TEE)
pnpm ivaronix receipt verify 1644
#  →  ANCHORED ✓

# Add TEE re-attestation against the live 0G Compute provider
pnpm ivaronix receipt verify 74 --tee-independent
#  →  FULLY VERIFIED ✓

When the live Compute provider's TEE channel is unreachable or the broker session has rotated, the CLI prints ANCHORED ✓ · TEE-independent unavailable with an amber banner and exits 0 (the receipt is genuinely anchored on chain — only the live re-attestation channel is down). If the broker returns a real signature mismatch — a tamper signal — the CLI prints ANCHORED · TEE-independent FAILED and exits 1. No fake green.

Anchor a fresh receipt of your own

cp .env.example .env
# Fill: IVARONIX_ROUTER_KEY, IVARONIX_SIGNER_KEY
# Testnet faucet: https://faucet.0g.ai

pnpm ivaronix demo
#  →  anchors one real receipt on Galileo testnet
#  →  prints /r/<id>, chainscan tx link, and the verify command

Higher tiers run additional roles:

pnpm ivaronix demo --tier standard      # 3 roles · analyst + critic + judge
pnpm ivaronix demo --tier high-stakes   # 5 roles
pnpm ivaronix demo --tier audit         # 6 roles, includes red-team-critic

For sensitive input, encrypt it before the run:

pnpm ivaronix doc ask contract.pdf "find risky clauses" \
  --skill private-doc-review --burn
#  →  AES-256-GCM session-key encryption, key destroyed post-anchor,
#     keyFingerprint captured in the receipt body

Open the Studio surface

pnpm --filter @ivaronix/studio dev
#  →  http://localhost:3300

Run the contract test suite

cd contracts && forge test
#  →  227 tests passing across 15 contracts

Reviewer notes

Network reference

Galileo testnet Aristotle mainnet
Chain ID 16602 16661
RPC https://evmrpc-testnet.0g.ai https://evmrpc.0g.ai
Explorer https://chainscan-galileo.0g.ai https://chainscan.0g.ai
Faucet https://faucet.0g.ai (free, no auth) source from a CEX or 0G bridge
Live contracts 15 10 (deployed 2026-05-15)

Test account

The deployer wallet 0xaa954c33810029a3eFb0bf755FEF17863E8677Ce is funded on both networks. Reviewers can either reuse it (inherits passport history — testnet tokenId 1, mainnet tokenId 2) or generate a fresh wallet (cast wallet new), fund via the faucet, and mint a new passport with pnpm ivaronix passport mint.

For mainnet TEE re-verification, the deployer's first call on a fresh shell needs a one-time Compute provider acknowledgement plus a small ledger deposit (≈0.001 OG). Helper scripts under scripts/mainnet/ handle this: discover-compute-providers.ts lists registered TEE providers (the sovereign 0GM-1.0-35B-A3B provider at 0x4870CbC4… is canonical); deposit-compute-ledger.ts deposits the broker ledger fee. Without these, the first --tee-independent call returns ANCHORED with an amber banner instead of FULLY VERIFIED — the verifier degrades honestly rather than failing silently.

Canonical demo receipts

Receipt Network Type Replay command
1644 Galileo doc_ask · TIER 1 TEE pnpm ivaronix receipt verify 1644
74 Galileo doc_ask · TIER 1 TEE pnpm ivaronix receipt verify 74 --tee-independent
21 Aristotle doc_ask · TIER 1 TEE — signed by the sovereign 0GM-1.0-35B-A3B provider pnpm ivaronix receipt verify 21 --network mainnet --tee-independent

If the TEE channel is unreachable at the moment a reviewer runs --tee-independent, the first four checks still pass and the CLI prints ANCHORED ✓ · TEE-independent unavailable with an amber banner and exits 0. A real broker-side mismatch (tamper signal) prints ANCHORED · TEE-independent FAILED and exits 1 — the two outcomes are kept distinct so a CI gate doesn't trip on a transient broker.

Rate-limit caveats

  • 0G Router caps requests at roughly 30 per minute per credential. The Keyring rotates across multiple credentials when configured.
  • Public Studio proof pages (/r/<id>) are read-only and have no rate limit.
  • broker.processResponse for TEE re-verify works against fresh receipts whose broker sessions are still active (the 0G Compute provider rotates session keys over time). Archival receipts return ANCHORED ✓ · TEE-independent unavailable with exit 0 — the four authenticity checks (schema · hash · signature · chain anchor) still verify deterministically, only the live TEE re-attestation channel needs an in-window session.

Tier 1 vs Tier 2 — honest disclosure

Every Ivaronix receipt is one of:

Tier Compute Storage proof Chain anchor Re-verify CLI
TIER 1 · TEE (green) TEE-attested 0G Compute evidenceRoot on 0G Storage yes --tee-independent returns FULLY VERIFIED ✓
TIER 2 · EXTERNAL (amber) NVIDIA NIM / Gemini / OpenAI / Ollama optional yes returns ANCHORED (not FULLY VERIFIED)

The /r/<id> proof page never claims compute integrity it cannot back. A TIER 2 receipt renders an explicit "verifies storage integrity ✓ · verifies compute integrity ⚠ external provider" line. Storage-integrity and compute-integrity are separate claims; the page labels each one.

Shipped today vs queued for v1.1

Shipped on both networks

  • 13-type receipt schema with RFC-8785 canonical hash (TS / Python / Rust, byte-equal across all three, checked on every PR)
  • ReceiptRegistryV3 EIP-712 typed-data anchoring with per-agent monotonic nonces
  • Independent TEE re-verification via broker.processResponse
  • AgentPassportINFTV2 (ERC-7857) — trust score, receipt count, violation history
  • Consensus mode — 6 roles, 4 tiers (quick · standard · high-stakes · audit), Jaccard + cosine convergence scoring
  • Burn mode — AES-256-GCM session-key encryption, key destroyed post-anchor, keyFingerprint captured before zeroing
  • SkillRegistryV2 marketplace primitive with og.creator.fee_split recorded on every receipt body
  • 10 first-party skills + 150 ported skills (160 total)
  • Studio (Next.js 15, SIWE session auth, mobile + desktop), CLI (ivaronix(1)), MCP server, IETF AAT export

Queued for v1.1

  • Live OG fee settlement. SkillRunPayment is deployed and exercised end-to-end in CLI flow; wiring it into the Studio run path so OG transfers at 90/10 split happen atomically inside every marketplace purchase is the v1.1 headline. Today, the declared fee split is recorded on every receipt body and is enforceable off-chain against the receipt; live settlement adds the on-chain transfer.
  • 0G DA integration. Schema slot og.da.batched reserved; integration lands when 0G ships a public DA disperser endpoint.
  • Multi-agent receipt chains. Single receipt spanning a chain of delegations, each leg signed by its own passport.
  • ZK receipt compression. SNARK proving receipt validity without revealing content — privacy-preserving compliance reporting.

Polyglot canonical hash — RFC-8785

Three reference implementations of the receipt hash, byte-equal across all three on every PR:

CI runs .github/workflows/jcs-roundtrip.yml on every push: each language hashes the same 29 vectors; scripts/verifier-py/cross_check.py asserts byte-equality across all three. The merge is blocked on any divergence.

"Re-verify on any machine, in any language" is only true if the canonical hash is language-independent. RFC-8785 (JSON Canonicalisation Scheme) is the spec; docs/HASH_FUNCTION.md is the design doc, including the schemaVersion migration plan so v1 and v2 receipts coexist forever.

Deployed contracts

Aristotle mainnet · chainId 16661

10 contracts deployed on **2026-05-15**. 148 receipts anchored on `ReceiptRegistryV3` + `ReceiptRegistryV2`, spanning all 13 receipt-type slots. Deployer wallet `0xaa954c33810029a3eFb0bf755FEF17863E8677Ce`.
Contract Address
AgentPassportINFTV2 0x5D724659A7d4B0B0917F5DAe9579423D2c85a6Ad
CapabilityRegistryV2 0x41fEad4b86DE042845D25Be71aae857E19a8089E
Erc7857Verifier 0x97376C6f0BE0Ee08AA34C4cAcdbDeC2183e7743c
MemoryAccessLogV2 0xA2c3420242aE2BdD7e0970B1DfB28b3055DC4E65
ReceiptRegistryV2 0x27a54F64F3A8578B39fE1E61dF7014813F325adf
ReceiptRegistryV3 0xCE35aF8D75ffB24BC1671Ca9F0CF293D82737297
SkillPricing 0x08d25653638c3ed40C3b82840fA20CAe9c94563E
SkillRegistryV2 0x080f87A9E93e9bd0a9e0eB94F97123bf333b1Dde
SkillRunPayment 0xf8085B43a08e957Fea157394dbB0d3EB76A1cD6A
SubscriptionEscrowV2 0x937cfE76dEdB25CCf6c7C56fF16F53270794311e

Sample anchor transactions any reviewer can replay without auth:

Galileo testnet · chainId 16602

15 contracts live, feeding Studio + CLI + MCP. V1 contracts remain live so historical receipts stay verifiable; V2/V3 are canonical for new writes.
Contract Address
AgentPassportINFT 0x08d25653638c3ed40C3b82840fA20CAe9c94563E — stays live for 4 minted passports (tokenIds 1-4)
AgentPassportINFTV2 0x85e9dD63155836a9BF31F579BFC3a8eb2B46494d — authorizedRecorders-only with ReceiptRegistryV2 cross-check and a ±100 trustS…
CapabilityRegistry 0x3783f3c4834fCCBD553860e15c64C7E052646a8D — stays live for any existing grants
CapabilityRegistryV2 0x1351CD87360f0366D0A0068164e606B3c320F3E1 — Private reverse indexes close a social-graph leak; authorizedRelayers gate on…
Erc7857Verifier 0xEAd66Cb90B681720f3aab52d86c289E21106d938 — V1 verifier reused by AgentPassportINFTV2
MemoryAccessLog 0xEe1aDFe76785377C4430B1325d86E58A6eC92119 — stays live for any existing log entries (chain history immutable)
MemoryAccessLogV2 0xCbfE1f526483283Bba80c2Bed3622a56904bF96d — logAccess enforces msg
ReceiptRegistry 0x97376C6f0BE0Ee08AA34C4cAcdbDeC2183e7743c — stays live for the existing anchored receipts (chain history immutable; curre…
ReceiptRegistryV2 0xf675d4183b34fe8d1981FA9c117065aAcff690ab — EIP-712 anchor signature recovery; agentAddress is the recovered signer, not msg
ReceiptRegistryV3 0x7396D536594e2BE833070c7EB441A10906046257 — Admits receipt-type slots 10 (doc_room_create), 11 (doc_room_read), 12 (memor…
SkillPricing 0xc3369C9BD74D81E9c7226e5fc9427D19c12B718F — Mutable per-skill pricing (priceWei + creator/treasury bps) gated by SkillReg…
SkillRegistry 0xf8894Ce4FFc7C594976d5Eaca38d8FE6DB4820a1 — stays live for existing skill registrations (chain history immutable)
SkillRegistryV2 0xF05113E83146160024326ff30979c57f5adc2193 — Constructor pre-reserves 6 first-party skill IDs (private-doc-review, github-…
SkillRunPayment 0x9eA5FDba913AC94dA8833Fee21F2832827950A5C — Per-skill creator/treasury bps fee-split with pull-pattern withdrawals, lifet…
SubscriptionEscrowV2 0x74235b707194c4cc3DDb717B6D95595e8A82B7F5 — cancelGraceSeconds window between agent-initiated cancel and EXPIRED status c…

What makes it different

  • Receipts are independently re-verifiable on a clean machine. One command runs all five checks — schema, hash, signature, chain anchor, live TEE re-attestation — against the public 0G chain. No account. No wallet. No Ivaronix server.
  • The honesty layer is structural. TIER 1 and TIER 2 are separately labelled on every receipt page. The CLI never returns FULLY VERIFIED unless the live TEE step actually succeeded. Storage-integrity and compute-integrity are tracked as distinct claims.
  • Polyglot canonical hash. A reviewer can verify in TypeScript today, in Python or Rust tomorrow, and get byte-equal results across all three. CI blocks merge on divergence across 29 cross-language vectors.
  • Bound to identity. Every signer is an AgentPassportINFTV2 (ERC-7857) on-chain identity with public trust accrual. Buyers can see an agent's history before spending OG on a skill run.
  • Built for compliance. EU AI Act Article 12 expects non-operator-controlled audit logs by August 2026. Ivaronix produces them today.

CLI surface

ivaronix(1) is the canonical Ivaronix interface. Twenty-plus commands across receipts, skills, memory, passport, marketplace, demo, and admin. Source under apps/cli/src/commands/.

Most-used commands:

ivaronix doc ask <file> "<question>" --skill <id>   # one-shot AI review
ivaronix demo --tier audit                          # 6-role consensus
ivaronix receipt show <id>                          # full receipt body
ivaronix receipt verify <id> --tee-independent      # five-step re-verify
ivaronix passport mint                              # mint ERC-7857 INFT
ivaronix skill publish <id>                         # anchor manifest on chain
ivaronix memory remember "<text>" --tags work,legal # encrypted hybrid memory
ivaronix memory grant <addr> --scope memory:work    # CapabilityRegistryV2

Receipt anchors are idempotent at the storage and chain layers; a stalled inference call can be re-run without duplicating state.

Memory engine

MemoryEngine is an encrypted hybrid memory layer — vector similarity plus FTS keyword search, AES-256-GCM at rest with a fresh per-call nonce. Wired to CapabilityRegistryV2 for on-chain grants and MemoryAccessLogV2 for the on-chain access trail. Portable across machines via memory stream-id — a deterministic 0G KV stream identifier derived from any wallet.

ivaronix memory remember "Vendor X has a 90-day notice asymmetry" --tags work,legal
ivaronix memory recall   "asymmetric notice clauses" --top-k 5
ivaronix memory grant    0xPartner --scope memory:work --expires 1735689600
ivaronix memory log      --agent $IVARONIX_WALLET_ADDRESS --limit 10

Every memory write anchors a memory_access receipt. A memory write isn't just stored — it's attested. The same applies to reads and grants.

Ten sub-commands total: remember · recall · forget · grant · revoke · list · log · log-emit · stream-id · snapshot. Studio /memory mirrors the surface with SIWE-gated grant management and a real-time event feed from MemoryAccessLogV2.

Documentation

Doc Purpose
Ivaronix_Whitepaper.pdf Technical whitepaper
Ivaronix_Pitch_Deck.pdf Pitch deck
docs/HASH_FUNCTION.md RFC-8785 canonical hash specification
docs/RECEIPT_SCHEMA.md Receipt field-level reference
docs/MAINNET_READINESS.md Mainnet readiness checklist
docs/CRYPTO_NOTES.md Threat models for every primitive
docs/PRIVACY_NOTES.md Operator-as-proxy threat model
docs/SOLIDITY_CHOICES.md Contract design choices and trade-offs
docs/AAT_MAPPING.md IETF Agent Audit Trail draft mapping
docs/MARKETPLACE_DESIGN.md Skill marketplace design
docs/SKILL_PUBLISHING.md How to publish a skill
docs/0G_DA_INTEGRATION.md 0G Data Availability integration roadmap
SECURITY.md Security policy and disclosure
CONTRIBUTING.md How to contribute
BRAND.md Brand-asset license (separate from MIT code grant)
CHANGELOG.md Release notes

License & contact

Code: MIT. Brand assets: see BRAND.md — separate grant for fork and widget-embedding.

Open source at https://github.com/Pratiikpy/ivaronix. Security reports via SECURITY.md. Partnership inquiries welcome.

Ivaronix mark

About

ivaronix.xyz

Resources

Readme
License

Contributing

Contributing

Security policy

Security policy
Activity

Stars

0 stars

Watchers

0 watching

Forks

0 forks
Report repository

Releases

Packages

Contributors

Languages