Documentation

Everything needed to run the network from either side, and enough detail to work out what is wrong without asking anybody.

What is actually sold

Rendered seconds. Not impressions, not views. A Claude Code status-line command receives JSON on stdin, prints, and exits — it is never told when its output left the screen, whether the terminal was focused, or whether the window was even visible.

So the only claim this network can honestly make is that a line was rendered, and for how long. Everything downstream is priced on that, and every inference is biased low: under-counting costs a publisher a fraction of a cent, while over-counting bills an advertiser for delivery that never happened.

How the time is measured

Each render appends one line to a local file. Duration is inferred from the gap to the next render, with three rules:

• An interval is capped at 15 seconds, 1.5× the heartbeat. A closed laptop leaves an unbounded final gap; anything longer than the cap is a missing observation, not a longer view.
• The final render of a session credits nothing. There is no closing observation, so its length is genuinely unknown.
• A backwards clock credits zero, never a negative number.

The activity gate

An interval only counts if the session did real model work across it. Claude Code supplies two monotonic integers — total API duration and total input tokens — and if neither moved, nothing happened and the interval is worth zero.

Practically: leaving a window open earns nothing. Farming requires actually spending money on model calls. This is not proof of a human, and anyone who controls their own machine controls the payload it sends — it raises the floor, it does not close the door.

Which ad gets chosen

Highest bid with budget remaining, first price. Ties break deterministically by campaign id so the result is auditable. When no paid campaign is eligible, house inventory fills the slot — it bids zero, bills nobody and credits nobody, and rotates. Any real bid displaces it immediately.

Install

Register a wallet at sigil.bond/#earn, then:

# write the daemon config and patch Claude Code's settings
node bin/install.mjs pk_yourtoken --server https://sigil.bond

# start the daemon — the only part that touches the network
node bin/daemon.mjs

The status line it installs is three POSIX tools:

{ printf '%s ' "$(date +%s)"; cat; echo; } >> ~/.sigil/ticks 2>/dev/null; cat ~/.sigil/line 2>/dev/null; true

What goes where

Verify it works

Paste your token at sigil.bond/#earn. The status pill tells you which of three states you are in:

Earnings and payouts

• You receive 70% of gross for every second your machine rendered a paid line.
• Payouts are batched direct transfers. There is no claim transaction and no account rent for you to pay.
• The threshold is $1.00 in SOL. Below it, the balance carries forward — nothing is lost.
• A first payout to a wallet that has never held SOL must clear the network's rent-exempt minimum, currently 890,880 lamports. Below that the transfer would fail, so it waits.

Payout assets

Advertisers pay USDC. You choose which asset that debt is settled in — SOL, $PACT, or a split. This is a denomination election, not a liquidity position: nothing is pooled, no fee accrues, and there is no impermanent loss.

curl -X PATCH https://sigil.bond/v1/publishers/me \
  -H "Authorization: Bearer pk_yourtoken" \
  -H 'Content-Type: application/json' \
  -d '{"election":{"SOL":7000,"PACT":3000}}'

• Basis points, and they must sum to exactly 10,000. A split that sums to less would silently discard the remainder.
• Applied at the moment earnings are credited, so changing it never redenominates what you already earned.
• Each asset has its own threshold: $1.00 for SOL, $25.00 for $PACT. A thin market makes a small token payout unrealisable, so the halves clear independently.

Buying placements

No account. Ask for a campaign, get a 402 with payment requirements, pay, retry.

# 1. ask — this returns 402, which is the intended flow, not an error
curl -X POST https://sigil.bond/v1/campaigns \
  -H 'Content-Type: application/json' \
  -d '{"text":"your line, 72 chars max","cprmMicros":"3000000","budgetMicros":"250000000"}'

# 2. the response names the amount, mint, recipient and network
# 3. pay it, then retry with the signed payload
curl -X POST https://sigil.bond/v1/campaigns \
  -H 'Content-Type: application/json' \
  -H 'X-Payment: <base64 x402 payload>' \
  -d '{"text":"your line, 72 chars max","cprmMicros":"3000000","budgetMicros":"250000000"}'

Creative is plain text, 72 characters. Terminal control sequences are refused — the line renders inside somebody else's terminal, and an advertiser must not be able to move their cursor or clear their screen.

Budget and pacing

• You bid CPRM — micro-USD per 1,000 rendered minutes. Minimum $1.00.
• Your deposit is a hard ceiling. Delivery past it is given away, never billed.
• pacing: "asap" spends as fast as delivery allows. "even" releases the budget linearly across windowSeconds, so at any moment you can only have spent budget × elapsed / window.
• A top-up adds to the deposit and never resets what has been spent.

Delivery reporting

GET /v1/campaigns/{id}/delivery returns hourly buckets and a per-publisher breakdown.

HTTP API

Limits and constants

Error codes

Troubleshooting

My status line is blank

Expected on a fresh install — the daemon has not fetched an ad yet. Check ~/.sigil/line exists. If it does not:

• Is the daemon running? It logs to stderr on every cycle.
• Is there inventory? If nothing is live, the daemon deletes line rather than letting a stale ad ride.
• Run the command by hand: echo '{"session_id":"x"}' | sh -c "$(your statusLine command)". It should exit 0 and print nothing.

The status line never changed from what I had before

Claude Code has one slot and something else holds it. Check ~/.claude/settings.json, and remember project settings override user settings — a project's .claude/settings.json wins inside that folder.

Rendered time is climbing but earnings are zero

Three possible reasons, in order of likelihood:

1. House inventory. It renders and bills nobody. Your dashboard shows unsold time separately.
2. The activity gate. Intervals where the agent did no model work are worth zero. An open window is not activity.
3. Below the payout threshold. Earnings exist but are under $1.00. They carry forward.

The dashboard says "waiting" and never changes

The daemon has never successfully uploaded. Its stderr will say why — a failed cycle is logged, and the outbox is retained rather than dropped. Check the token in ~/.sigil/config.json matches the one you pasted.

A ticks.out file has been sitting there

An upload was not acknowledged. It is retained on purpose and re-sent on the next cycle; the server discards anything already settled, so a retry cannot pay twice. It clears itself once a cycle succeeds.

My payout has not arrived

• Below the threshold for that asset — the dashboard says how far.
• A never-funded wallet below the rent-exempt minimum. The transfer would fail, so it waits until the balance clears it.
• Payouts run in batches, not per-earning.

How do I check my earnings later?

Open sigil.bond/#dashboard. Your token is kept in your browser, so it loads straight away — bookmark it. If the browser has forgotten it, or you are on another machine, click I already have a token and paste it.

Do not go through registration again to check a balance. It would work, but it is not what it is for.

I lost my publisher token

Register the same wallet again. Earnings are held against the wallet, not the token, so the new token sees the same balance — including everything earned before it existed. Your old tokens keep working too; a wallet may hold several, one per machine, and issuing one never revokes another.

I lost my manage key

There is no recovery. Only a hash is stored, deliberately — the alternative is an account system with a password reset, which means an email address, a support queue, and a new thing to breach. A campaign without its key runs to the end of its budget and stops.

Creating a campaign returns 402

That is the payment flow working. The body carries the amount, mint, recipient and network. Pay it and retry with the X-Payment header.

Creating a campaign returns 503

payments_not_configured means the exchange has no payment recipient set. It refuses rather than quoting a price it cannot honour — a 402 naming a placeholder would take money nobody could recover.

What leaves your machine

Claude Code hands the status line a rich payload. This is everything we upload from it:

{
  "sessionId": "abc123",     // opaque, from the agent
  "seq":       47,           // ordering
  "at":        1788340193,   // whole seconds
  "adId":      "cmp_9f2a71", // which line was on screen
  "apiMs":     91240,        // monotonic, from the agent
  "inTokens":  155300        // monotonic, from the agent
}

No path, repository, branch, prompt, transcript or code. The status line never parses the payload — it appends bytes and prints a file — so there is no parser in your editor to leak anything, and no network call to leak it over. See Privacy for the policy version.