Skip to content

Oak ChainKeep Oak. Add Proof.

Your team already knows JCR and Sling. Oak Chain adds signed writes, economic authorization, and validator-backed durability.

Oak Chain
Wallet-authored contentEpoch-aware finalityRaft replicated durabilityOak-compatible runtime

For teams running AEM or Oak in production

Your current stack can publish content, but it cannot natively prove who authorized each critical write.

Oak Chain keeps your Oak mental model and adds signed intent, ETH-backed policy, and validator consensus as a verifiable trust path.

Start With One Proof

If your immediate question is "can this work with our Oak workflows?", run one local validator cluster and validate one signed write end-to-end.

  • Micro-win: Follow Developer Guide until you see leader/follower state and one replicated write.
  • Why this first: You can validate trust and durability behavior before debating migration strategy.

Two Axioms

Axiom 1: Ethereum Is Durable Settlement Infrastructure

Ethereum is no longer a speculative side system. It is an active settlement layer for stablecoins, tokenized assets, and institutional transaction flows.

Major financial and payment operators now use Ethereum-adjacent rails in production, while validators and stakers secure the network with globally distributed economic weight. The result is a settlement substrate that keeps operating under real-world load, with transparent state and predictable execution rules.

For Oak Chain, this is an architectural constant: the base asset is ETH.

Axiom 2: Oak Already Runs Critical Content Workloads

Oak is the repository core behind Adobe Experience Manager (AEM), the platform many enterprises use to run content, assets, and digital experience delivery at scale.

Oak is not universal, but it is deeply embedded where content workflows are expensive to replace. That includes global commerce catalogs, marketing sites, customer portals, regulated content workflows, and high-traffic public properties.

Oak Chain does not replace Oak. It extends Oak's write path with signed writes, payment proofs, and validator consensus.


The Bridge in One View

Oak Chain combines Ethereum's payment/finality model with Oak's content model.

What stays familiar
What is introduced
JCR API
Wallet-scoped namespace ownership
Sling authoring patterns
ETH-backed authorization path
Oak TAR segment model
Raft validator replication
Content and asset semantics
CID-linked binary durability

Why This Matters Now

Institutions moved first

Ethereum rails now support high-value settlement and tokenized assets in production environments.

Content infrastructure stayed centralized

Most content systems still rely on trusted operators and revocable access boundaries.

Oak Chain is the integration layer

The same Oak development model, now combined with signatures, payment proofs, and validator consensus.


Interactive System Graph


Protocol Path

1. Author signs write intent
2. Payment proof is submitted
3. Leader verifies auth + economics
4. Proposal enters epoch queue
5. Validators replicate via consensus
6. State persists in Oak + CID graph

Every accepted write is signed, economically authorized, replicated, and durable.


Choose Your Route

For Builders

Build on Oak Chain

Start with auth, paths, streaming, and API surfaces.

Developer Guide →
For Operators

Operate a Validator

Run nodes, monitor queue/finality signals, and validate economics.

Operator Docs →

Apache 2.0 Licensed