- Passive listening between an exit and the server.
- A machine acting as another: every request is checked against the grant table.
- A revoked machine coming back: its token stops working at once.
- Credit inflation: the server counts bytes, seconds and memory itself.
- Being paid for work that was never done: a parcel is only paid for output the server actually received, and the challenge that closes it is solved over a hash of exactly those bytes — so an answer found before the container ran closes nothing.
- Claiming an offer nobody ran: the partner confirms it to the server, and a server without a partner pays no offers at all.
- Anything else on the machine reaching the app's interface: it is a Unix socket with mode 0600, not a port.
- A stolen grant is one machine the operator can revoke in a line.
An honest table.
Every claim below is a property of the code in this repository. Where a property is missing, it is listed as missing.
- The server sees node addresses and client packets.
- The exit sees destination addresses. There is no zero-knowledge claim on main.
- The server holds the only record of who each machine is: a grant it minted, revocable in one command.
- Traffic analysis and multi-user isolation are not solved.
- No accounts, quotas, payments or settlement.
Crypto, per primitive
| Use | Primitive |
|---|---|
| Key exchange, every session | ML-KEM-1024 |
| Records | XChaCha20-Poly1305 |
| Hashing / KDF | SHA-256 · HKDF |
| Machine identity | a grant the server minted and can revoke |
Nothing a machine sends is signed, because nothing it sends decides what it is paid. The balance, the clock and the counters live on the server; a node is a sensor and a pair of hands. The one thing a machine does decide is whether it gets paid at all: a parcel is worth its verified output, the challenge is solved over a hash of exactly that output, and a container that exited non-zero is worth nothing however long it ran.
No port on your machine
The app and the command line talk to the node over a Unix domain socket at $XDG_RUNTIME_DIR/imesh.sock (or /tmp/imesh-<uid>.sock), mode 0600, and a named pipe on Windows. There is no listening TCP port: nothing on the machine can reach the interface unless it is the account that runs the node, and there is nothing on the network to find. An earlier version used a loopback port and that was wrong — a loopback port is reachable by every process on the box.
What a parcel is worth
The price of a parcel is what it produced — the bytes of output the server actually received — at the same rate for every machine. Time is counted and shown, but it is not money: a parcel that held the work for a minute and produced nothing is paid nothing. Three gates, and a parcel must pass all three: the challenge must check against a hash of that exact output, the container must have exited cleanly, and the output must be non-empty. There is no fourth state, and no path from “I did not do it” to “I was paid”.
the meter counts; nobody is paid
1 credit per KiB of output
however long it ran, it produced nothing to sell
Exit firewall
Tunnel traffic may reach any global unicast address. RFC1918, loopback, link-local, CGNAT and multicast ranges are dropped on purpose, so a shared exit can never be used as a bridge into someone's own LAN. If a definition of “outside” includes the LAN, that is a policy change, and a deliberate one.