Docs

A settlement layer that only releases what has been verified#

The advertiser deposits the budget into the contract before the campaign starts. The rules that decide payout are hashed on-chain at the same moment and cannot be changed afterwards. When a result is verified, the contract executes the payout; there is no separate approval step for the advertiser.

Why performance-based deals never took hold#

Performance-based deals never took hold in influencer marketing because of enforcement, not measurement. The conditions were measurable; what was missing was a way to force payment to follow them.

A contract only starts working after a dispute has happened, so it does not address any of the three. NARU deposits the funds in advance and pays out with no separate approval once the condition is met.

From deposit to payout#

What actually happens over one campaign. Every step leaves a record on-chain.

1. 01
   Deposit

   The advertiser opens a campaign and moves the full budget into the contract. Without the deposit the campaign does not open.
2. 02
   Publish

   Title, rules and payout terms go on-chain as a signed record (an attestation) from the advertiser's own wallet, so readers can verify them without trusting our server.
3. 03
   Join

   A creator is checked against the eligibility rules and joins. Those rules were fixed at deposit time and cannot change.
4. 04
   Review

   The draft is checked against the rules before it goes up. A draft that passes is not reversed after publication.
5. 05
   Observe

   The server reads the published post itself and re-runs the same rules that are pinned on-chain.
6. 06
   Payout

   The oracle posts the verdict on-chain and the contract computes and sends the amount. The creator pays no gas.

Whose turn it is

How the payout amount is computed#

The contract has no idea what an app install or 500 reposts means. Whether the condition was met is decided outside; the contract only turns that result into an amount.

amount = min(verified units, remaining cap) × unit price

That is why a new campaign type does not require redeploying the contract. Register an attestation schema and it works.

Order of checks on payout

1. 01Campaign validity — not cancelled, within deadline plus grace, term exists
2. 02Verification path
3. 03Eligibility — only when the campaign has joining rules
4. 04Frozen or not
5. 05Clamp units — up to the per-creator remaining cap
6. 06Compute the amount
7. 07Clamp budget — up to the term's remaining budget
8. 08Write state — units claimed, spent, attestation marked used
9. 09Transfer

Step 2 — the verification path forks

Steps 5 and 7 — it is clamped twice

Creating a campaign#

What an advertiser decides when creating a campaign, and which of those cannot change afterwards. The last step takes two signatures; the deposit lands and the payout criteria are fixed at that moment.

Seven steps

1. 01
   Goal

   Pick what you want out of the campaign first. That choice pre-fills the payout items, unit prices and verification paths in the later steps.
2. 02
   Campaign details

   Name, product, run dates, number of seats. The name and description go on-chain so creators can verify them.
3. 03
   Targeting

   Open to everyone, or gated on eligibility rules. This is the only step where those rules can be set.
4. 04
   Settlement token

   Which token pays out. For tokens whose price moves, the amount is locked at the moment of deposit.
5. 05
   Payout items

   What you are buying and at what price. The sum of the item budgets is the amount you deposit.
6. 06
   Brief

   Required lines, banned phrasing, tone, retention obligations. Both the draft review and the payout verdict run against this text.
7. 07
   Review and deposit

   Two signatures — a token approval and the campaign creation. After the second, the full budget sits in the contract.

Fixed at the moment of deposit

The path for an advertiser to rewrite terms after the fact is structurally closed. The originals live off-chain and only the hash goes on-chain, so either party can take the original, recompute the hash and compare.

The claim grace period

The deadline passing does not let the advertiser reclaim immediately. With a 30-day attribution window, results near the deadline are verified late. Without a grace period the advertiser could sweep the unspent budget right after the deadline, leavinga creator who delivered but was not paid. The grace period is therefore set longer than the attribution window (30 days or more recommended).

Verification paths and the trust model#

Bringing an off-chain fact on-chain means somebody has to look and assert it. So the question is not whether trust can be removed but how far it can be reduced per item. NARU is designed so the verification path is swappable per payout item.

Guaranteed by the contract

• A campaign cannot open without the deposit
• Rules cannot change after creation
• The advertiser cannot reclaim before the grace period ends
• The same verdict cannot be spent twice

The verification path is swappable per item

Each payout item names a verifier. If none is named, the default path is used. Swapping the verifier does not require redeploying the contract — it is one field on the item.

How a verdict on the default path can be checked

What still needs trust

Contracts and network#

Source is verified for all of them. You can read them on the explorer.

Verifiable items#

The payout items a campaign can use, and where NARU reads each result from. Items with no verification path yet are marked as planned.