ODINIDODINID@
WalletSupportGovernanceMembersChat
Connect
Navigation
Connect
WalletSupportGovernanceMembersChat

Legal statement

Non-intermediary statement

This document defines the scope boundaries of ODINID@ as shared infrastructure. It is intended to be stable, auditable, and not marketing-driven.

Boundary: ODINID@ prepares deterministic metadata, routes identity-backed portal workflows, and displays evidence. Wallets, members, merchants, PSPs, and banks remain responsible for signing, broadcasting, settlement, payment authorization, and funds control.

Version: v1.2 · Last updated: 2026-05-27 · Governing law: The Netherlands

Trust hubFAQRead the CNO manifestoTerms & Privacy
What ODINID@ is not
  • ODINID@ is not an issuer, custodian, or intermediary.
  • ODINID@ does not provide payment services, payment initiation, or custody services.
  • ODINID@ does not provide crypto-asset custody, transfer, exchange, execution, placing, order transmission, or trading-platform services.
  • ODINID@ does not provide financial, tax, accounting, or legal advice.
Custody boundaries
  • We do not generate private keys for users.
  • We do not store private keys, seed phrases, or signing material.
  • We do not hold user funds or assets.
  • NL_CORE does not operate bridge reserve wallets or bridge execution routes.

Users authenticate and sign with their own VerusID-capable wallet.

Entity scope separation

The Dutch cooperative production scope is NL_CORE: identity, templates, read-only verification, WEV/accounting evidence, and Odoo administration. Any bridge, reserve, mint, redeem, or liquidity experiment is outside this member lane and requires a separate entity scope, separate operator controls, and separate legal review before public use.

What ODINID@ provides
  • Deterministic resolution and routing (identity → endpoints).
  • Cryptographic anchoring and verifiable proofs.
  • Auditable state transitions and monitoring interfaces.
  • Deterministic validation and cryptographic anchoring of B2B transaction evidence.
  • Passive payment references such as EPC-QR prefill data, where the user executes the payment in their own bank application.
  • WEV/accounting evidence based on user-supplied parameters and verified chain readbacks.
Commerce integrations

Where ODINID@ integrates with third-party services (for example an Odoo-based shop payment-reference UI), ODINID@ operates only an administrative routing layer and technical interface. It does not take possession of funds, execute payments, initiate payment orders, or act as merchant-of-record.

WEV and reports

WEV outputs are objective accounting evidence support generated from explicit inputs such as native MCL loop IDs, amounts, maturity, holder pubkey evidence, confirmations, and user-selected assumptions. They are not a price quote, redemption value, buyback promise, investment recommendation, or tax conclusion.

Contact
  • Security: security@odinid.net
  • Privacy: privacy@odinid.net
VerusID vs ODINID@
  • VerusID: Layer 1 identity primitive (your key).
  • ODINID@: Layer 2 cooperative operations layer (your cooperative).

Back to the portal: odinid.net

© 2026 ODINID Cooperative. Sovereign & Non-Custodial.
Official System Identity: ODINID@
PricingFAQTerms & Privacy