Promises and limits

Trust

What woodls promises, what it never claims, and how you can check.

Promises

Each one something you can check, or a date when you can.

What we promise

Hosts run only woodls’ engine and open models, each model checked against its SHA-256. They never run anyone’s code, files or commands.
Hosts work only while their owners are away, and stop within a second of a touch (47–151 ms in our tests on one Mac).
Hosts aren’t told your account, your IP address or who you are. What you write can still say who you are: secrets, common personal data, home-folder paths and git names and emails are taken out on your machine first, but nothing catches everything.
The Gateway doesn’t keep what you write. A job picked to be run again is held in memory until its check ends, then dropped.
Every seed movement is written to the Rings, which rangers co-sign so it can’t be quietly rewritten.

Never

Because none of these is true.

What we never claim

That your requests are hidden from the computer that answers them. We don’t call the network encrypted.
That every job is proven correct. A share is run again, and a cheat is caught by those checks.
That fake accounts are impossible. We make them costly.
That hosting earns a set amount, or anything that becomes cash.
That seeds are money.
That the Forest is fit for regulated data, such as health or bank records.
That it costs less than the big AI companies.

Run again

On our own machines, and compared.

How jobs are checked

The computer that runs a job signs a receipt for it, with the exact words it produced. Our own machines run a share of jobs again: every job while a host is new, and some after that. A job that fails is checked again on a second machine before anything happens; a confirmed cheat gives back what it was paid; three in 30 days cost the host its unripened seeds and its place.

Job	Paid	Check	Why	Given back	Seeds taken	Host
1	1,006 µseeds	passed
4	1,282 µseeds	caught	impossible tokens	1,090 µseeds
5	700 µseeds	caught	disagreed	595 µseeds
8	850 µseeds	caught	impossible tokens	723 µseeds	856 µseeds	suspended
9	462 µseeds	caught	impossible tokens	393 µseeds		suspended

A host that served cheaper 2-bit weights while claiming the 4-bit file: its five checked jobs, as they happened. Four were caught, for tokens the claimed model could never have chosen, or for too many that disagreed with it. Each payer got back what the host was paid (the root fee isn’t refunded yet); at the third confirmed cheat its unripened seeds went to Commons, and it was suspended.

Read from bench/results/m4-cheater-live-2026-09-26.csv when this page was built. One MacBook Pro (M5 Max), with two hosts and two checkers on it, 26 September 2026.

On a Mac

Built into macOS, and checked on the running engine.

The engine’s sandbox

The engine can’t open your home folder, Documents, external drives, the temporary folders, the keychain or the clipboard, and its only connections are to the woodls service on your own machine. The Linux sandbox isn’t built yet COMING, so Linux hosts wait for it.

No prompts

Ever, in any log.

Logs

Operational logs hold no prompts or answers. They’re kept for 180 days in India, as Indian law asks, once the servers are there with the alpha COMING. The safety check records its decisions and keeps none of the text it read.

Rules

And what happens when they’re broken.

Abuse and the law

The acceptable-use policy says what the Forest won’t carry; every request is checked against it before any host sees it.
Reporting abuse: a report form comes with the alpha COMING.
Requests from the police and courts: a written process, and a yearly report of how many came and what we did COMING.

Limits

The checks catch cheats by chance and cost; they don’t prove every job.
The safety check makes mistakes in both directions.