Provenance Protocol · 0G Network

Every AI
has a lineage.
Every inference
pays its ancestors.

Mekar — to bloom, in Indonesian — is a public ledger of AI parentage. Register an agent, fine-tune it, compose new ones, and royalties flow automatically up the family tree to every contributor below you.

Bloom your first agent ↗Wander the garden

0Agents bloomed

0Lineage edges

ERC-7857INFT Standard

Fig. 01 — A bloom of code,
the genesis seed of the protocol

The Provenance Crisis

Three lawsuits.
One missing ledger.

“We can't prove what we trained on. We can't pay who we owe. And we can't build the next generation without knowing the last.”

'23

NYT v. OpenAI

The Times sued OpenAI and Microsoft for training on millions of copyrighted articles without licensing. The lawsuit hinges on a question with no clean answer: what was in the training data, and what's owed?

'23

Getty v. Stability AI

Getty alleges that Stable Diffusion ingested 12 million of its photographs. Even Getty watermarks appeared in the model's outputs — the lineage was visible, but unprovable on-chain.

'26

EU AI Act takes effect

Article 53 requires general-purpose AI providers to publish a 'sufficiently detailed summary' of training content. Compliance is on the honor system. Verification is on the courts.

The Protocol

From seed to scatter, in four stages.

Mekar borrows the structure of plant life — and the economics of music royalties. Every agent passes through the same four stages, regardless of whether it's a frontier base model or a weekend fine-tune.

Plant a seed

Fork or compose

Anyone can fine-tune your agent or merge it with another. Lineage is recorded, immutably, by the protocol.

III

Bloom in use

Inferences settle on-chain. Your agent earns from every call — the same way a song earns from every play.

Scatter the royalties

A single payment splits across the entire ancestry — parents, grandparents, training-data contributors. Automatic, recursive, public.

A garden, in numbers

Lineages bloom faster
than databases can keep up.

0agents

Bloomed to date

0edges

Lineage links on chain

0genesis

Anchor lineages

0merged

Composed blooms

The Garden

Wander the lineage.
Click any bloom.

Every flower is an INFT — a model whose parentage is engraved on 0G. Genesis blooms anchor the canopy; forks branch; composed agents weave across the tree.

⌕

AllGenesisForksComposed

Built on 0G

Six modules. One garden.

Mekar is the only chain where every primitive — INFT identity, sealed compute, alignment audit, royalty settlement — lives natively in one ecosystem.

ERC-7857INFT semina

Identity

Each agent is an INFT carrying encrypted weights, parents, training data Merkle root, and TEE attestation.

0G Storagespecialis flos

Storage

Weight manifests anchor on the 0G Storage Log layer today; the encrypted Specialized Flow tier — premium permanence — is the next milestone.

0G Computetee securus

Compute

Sealed inference inside hardware enclaves. Every result carries an attestation hash settled on-chain.

0G Chainramus chain

Chain

0G Aristotle mainnet (16661) runs the Mekar contracts: Registry, AgentINFT, RoyaltyVault, TrainingDataRegistry.

Alignmentcustos veritas

Alignment

Alignment Nodes audit lineage health — bias drift, hallucination, training-data forgery.

Data Servingvia mercatus

Settlement

Pay-per-inference auto-billing flows directly into the royalty cascade. No middleman, no middle ledger.

For builders

Get paid when your AI model is used.

Open-source or proprietary — your weights stay yours (encrypt them in Strict mode). Register your model on Mekar and every downstream use — every inference, every fork — routes royalty back to you. Three calls, zero infrastructure.

// 1. Register your model once — it becomes an INFT.
//    Open weights or proprietary: pick the mode at mint.
const agentId = await agentINFT.mintGenesis(
  weightsPointer,   // 0G Storage rootHash (encrypted for Strict mode)
  trainingMerkle,   // Merkle root of your training data
  teeProof,         // TEE attestation hash
  royaltySchema,    // your split: 50/25/15/7/3 by default
  mode,             // Strict (encrypted) · Voluntary (open) · AuditOnly
);

// 2. Anyone — a Discord bot, a dApp, another model —
//    pays to use it through one call:
await royaltyVault.payInference(agentId, { value: fee });

// 3. Royalty cascades to YOU automatically, on-chain,
//    every single inference. Fork it? The forker pays too,
//    and a share flows back up to you as the ancestor.
//    No platform cut. No invoicing. No middleman.

Full integration recipe →ERC-7857 INFT · same contract any project reads

FAQ

Slow questions, careful answers.

How is this different from a generic NFT marketplace?

Mekar's INFTs carry verifiable lineage and trigger an automatic royalty cascade on every inference — not just on resale. The royalty rail is the protocol, not an afterthought.

What happens if an agent has a thousand ancestors?

Distribution is bounded by generation depth (default 10) and gas-aware. Beyond that cap, the unallocated share consolidates into the protocol treasury — the same rail that catches royalty owed to burned addresses. The cascade always settles atomically in a single transaction.

Do I have to expose model weights?

No. Weights upload to 0G Storage; the chain stores only the resulting Merkle root + a TEE attestation hash. The current build anchors files on the log tier as-is — the Specialized Flow tier with owner-held decryption keys, gated by Strict-mode INFTs, is the next milestone.

Can I revoke a fork I disapprove of?

Mekar is provenance, not gating. Forks are public by design. Misaligned descendants are flagged via Alignment Node audits and lose share of inference revenue.

What if my parent agent is offline or burned?

The lineage record is immutable. Royalty owed to a burned address routes to the protocol treasury, which funds alignment audits and security bounties.

The garden grows when you plant.

Bloom your first agent in minutes. Pin its weights to 0G Storage. Watch the cascade flow.