SOV-CHAIN active definition

Public blockchain

On-chain data on public decentralized networks, immutable and global.

⛓

// What it means

SOV-CHAIN identifies data whose residency is not a datacenter but a public decentralized blockchain network. On-chain data does not physically reside in a single jurisdiction: it is replicated across thousands of independent nodes distributed globally, and its integrity is guaranteed cryptographically, not contractually. It must however be noted: the extraterritorial nature of the nodes does not automatically remove from EU jurisdiction those who operate components connected to the chain. Front-end interfaces, indexers, custodial wallets, IPFS gateways and any off-chain service offered to EU users fall under MiCAR, GDPR and applicable national regulations.

This category typically covers: document hashes for notarization, tokenized assets (NFT, RWA), verifiable credentials, smart contracts and trustless escrow logic. It is not suitable for personal or confidential data, since on-chain implies immutability and public visibility. For RWA (Real World Assets) and tokenized assets the regulatory framework has tightened significantly in 2025-2026: MiCAR is fully operational, national regulations on stablecoins and regulated assets are underway, and every project must be assessed for the token's qualification, the applicable regime (e-money, ART, utility, security) and the provider's CASP obligations.

When an Omniproject service is marked SOV-CHAIN, we always pair it with a second SOV for the off-chain part (UI, indices, personal data): typically SOV-IT or SOV-EU. The on-chain part is only the proof and settlement layer, while the regulated component and personal data live under a traditional sovereign regime.

// Where the data resides

Where the data physically resides

L1 networks

Ethereum mainnet · Polygon PoS · Base L2

L2 networks

Optimism · Arbitrum · zkSync

On-chain storage

Calldata, EIP-4844 blobs, contract state

Off-chain storage

IPFS · Arweave (in combination)

Indexer

The Graph · self-hosted (configurable SOV-IT/EU)

// When to choose it / when not to

✓ Choose it when

▸ Notarization and timestamping of documents (hash on-chain, file off-chain)
▸ Tokenized assets: NFT, RWA, certificates of ownership, usage rights
▸ Trustless escrow and multi-party settlement without intermediaries
▸ Verifiable credentials (W3C VC) anchored on-chain for cryptographic proofs
▸ Use cases requiring public auditability and guaranteed immutability

✕ Avoid it when

▸ Personal data: on-chain immutability is incompatible with the GDPR right to be forgotten
▸ Confidential data or trade secrets: everything on-chain is publicly readable
▸ High-frequency workloads: gas cost and finality latency make it impractical
▸ Systems requiring frequent modifications or deletion of state

// Compliance and standards

Regulatory references and standards applicable to the SOV-CHAIN sovereignty level.

MiCAR

EU Regulation 2023/1114 · fully operational · applies to services offered to EU users regardless of where the node runs

TFR

Transfer of Funds Regulation · traceability of crypto-asset transfers

GDPR Art. 17

Constraint: no personal data on-chain (incompatible with the right to be forgotten) · only hashes

Regole nazionali su stablecoin e RWA

Evolving 2025-2026 framework · case-by-case assessment of the token's qualification (e-money, ART, utility, security)

eIDAS 2

European wallets and verifiable credentials (W3C VC) anchored on-chain

ERC standards

ERC-721, ERC-1155, ERC-4337 for interoperability

// Specific FAQ

If the data is public, how do I protect sensitive information?

On SOV-CHAIN goes only what can be public: typically cryptographic hashes. The actual content stays in an off-chain SOV (IT/EU) and the on-chain hash proves its integrity and timestamp.

What happens if the blockchain network disappears or forks?

We choose established networks (Ethereum, Polygon, Base) with a robust economy. In the event of a hard fork, we maintain migration and re-anchoring strategies documented from the design phase.

How much does it cost to publish on-chain?

It depends on the network. Ethereum mainnet is expensive (variable gas fees); we mainly use L2s (Base, Polygon) with costs of cents per transaction, while retaining security inherited from Ethereum.

// Other sovereignty levels

SOV-IT IT

Italian sovereignty

Data, infrastructure and operations entirely within Italian territory.

SOV-EU EU

European sovereignty

Data and infrastructure within the European Union, guaranteed GDPR compliance.

SOV-EXTRA WW

Non-EU sovereignty

Data on platforms outside the EU, governed by Standard Contractual Clauses.

CONFIGURABILE ⚙

Chosen by the client

The sovereignty level is chosen during contracting among SOV-IT, SOV-EU or SOV-EXTRA.

Want to understand which sovereignty level is right for your project? Let's talk.

$ Let's talk →