Guide

6 sections

Press ? anywhere in the app for the shortcut list.

Guide

How a batch becomes jobs, how a job is checked and paid, and what each tile means

01From batch to settlement

#	Step	What happens	Screen
01	Pick a job type	Pick a job typeThe catalog lists what this network can run and check. Try one on a public batch first, on this device, for free.	Catalog
02	Price the batch	Price the batchThe quote shows the price per job, the share of jobs re-run for checks, and what returns if supply falls short.	Quote
03	Contribute a device	Contribute a deviceCheck what this browser can run, download the model, and set a time cap and a resource cap. You can stop at any time.	Contribute
04	Watch the run	Watch the runJobs are spread across devices. When a device leaves, its unfinished jobs move to another one.	Runs
05	Read the checks	Read the checksEach checked job shows the device's result next to the reference it was compared with.	Results
06	Follow the money	Follow the moneyEvery settlement and every refund is one row in the ledger.	Ledger
07	Reserve capacity	Reserve capacityRepeat buyers lock $OCLO to hold a slot in a period with real supply, and prepay its execution in USDC. Both come back if supply falls short.	Reserve
08	Request a slot	Request a slotA wallet that holds $OCLO requests a slot in a coming period. The server reads the holding from the chain and records the request; no transaction is sent.	Request

02Tile states

Every job is one tile. Its pattern and label tell its state, never color alone.

Glyph	State	Meaning
	Open	An open job. Nobody holds it yet.
	Assigned	The scheduler gave the job to a device. The edge takes that device's color.
	Running	The device is computing. Stripes in the device color, filling from the bottom.
	Submitted	The result is in and waits for the check.
	Verified	The check passed. The vermilion stamp is pressed on the tile.
	Paid	Settled once. The tile takes the result's color and the coin goes to the device.
	Failed check	The check rejected the result. Soot cross-hatch and an X. The device gets nothing and the job goes back to the queue.
	Device left	The device left mid-job. Dashed edge, the progress drains.
	Reassigned	Another device picked the job up. The edge recolors to the new device.
	Refunded	Not delivered. Dashed edge and a return notch: that part goes back to the buyer.

03Costs and permissions

What a contributor gives: Download size, battery and compute time on your device, inside the caps you set. You can stop at any time.
What your wallet signs: Signing in is one message signature. It sends no transaction and costs no fee. Deposits and payments will ask for a separate transaction you can review in your wallet.
What $OCLO does: It is locked, never spent: a lock holds a reserved slot or keeps standing priority for repeat batches, and comes back when released. Jobs are always paid in USDC. Half of every creator fee from $OCLO trading, plus 25% of the service fee income, buys $OCLO on the market and burns it, from launch.
What a buyer pays: A batch is priced per job on a quote, including the share of jobs re-run for checks, and paid from your own USDC deposit held for that batch. Work that is not delivered is refunded. No $OCLO is needed to run a batch.

04Checks and limits

How checks work: In the first release the operator re-runs a share of jobs on a reference device and compares the results. Small numeric differences between devices are expected; the check compares the top label or a similarity tolerance.
Who sees the inputs: Inputs are public or permitted images and they are visible to the device that runs them, so private data does not belong in a batch.
When a job fails: A job that fails its check pays the device nothing and goes back to the queue. Work that is not delivered is refunded to the buyer.
Jobs that are not re-run: Only a share of each batch is re-run. A job outside that sample is paid once the same device's re-run jobs in the batch match; the ledger marks it Not re-run.

05Reservation on chain

Holding, releasing and expiring a slot are instructions of this program. Every address opens on Solscan. Open Reserve

Program

Reservation program: 99QeFfsPKsscVBtu2WtPhqqTY9M9amrhCSU4JdJ7NNJLView on Solscan
Config account: mABAE3ELabR41pg9LEnP9Uux9YRqz5Dwtv59LwsNZWaView on Solscan
$OCLO mint in Config: JmhtXgir6gxhcL8CEVGXWVnKKm4DDazdWYUzACZpumpView on Solscan
USDC mint in Config: EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1vView on Solscan

Instructions

reserve_slot: Locks your $OCLO and prepays USDC for one slot of a period whose supply is confirmed. Your wallet signs and the operator wallet co-signs.
release_slot: Gives the slot back at any time. The $OCLO lock and the unused USDC prepay return to your wallet. Your wallet alone signs.
expire_slot: Once a period's supply fails or the period ends, anyone can send it, and the $OCLO lock and the USDC prepay return to the slot's wallet.

Where the lock and the prepay sit

Slot account: A program address (PDA) with the seeds "slot", the period account, your wallet and the slot number (u16, little-endian). Only the program signs for it.
$OCLO lock vault: The slot account's associated token account for the $OCLO mint (a PDA of the associated token program: slot account, token program, mint).
USDC prepay vault: The slot account's associated token account for the USDC mint, derived the same way.
Period account: A PDA with the seeds "period" and the period number (u32, little-endian). It takes slots only after confirm_supply.
Config account: A PDA with the seed "config". It names the $OCLO mint and the USDC mint every lock and prepay is checked against.

Tokens leave a slot's vaults only through release_slot and expire_slot, back to the slot's wallet, or through open_batch_from_slot, which moves prepaid USDC into a batch that wallet opens.

06Keyboard

/: Focus the screen's search field, or open Go to
CtrlK: Go to any screen
gc: Open a screen: g, then its letter from the left rail (g c opens Catalog)
jk: Next or previous row in the main table
Enter: Open the selected row
?: List of shortcuts