pods v0.1.3

curl -fsSL https://pods.family/install.sh | sh        # macOS, Linux
irm https://pods.family/install.ps1 | iex             # Windows, in PowerShell

Earnings count up while a job runs. Payment is rate x duration, so you have
genuinely earned a little more every second — but the figure only moved when a
job finished, so it sat still for a minute at a time and looked frozen. It now
accrues live, using the same formula the coordinator pays by, and never ticks
backwards.

The terminal window is called pods. It was showing whatever directory the
binary was launched from.

pods v0.1.2

curl -fsSL https://pods.family/install.sh | sh        # macOS, Linux
irm https://pods.family/install.ps1 | iex             # Windows, in PowerShell

Windows now installs. The documented one-liner needs sh, which Command
Prompt does not have, so there was no way in at all. install.ps1 does the
same work in PowerShell — same checksum verification, same refusal to install
anything it cannot verify.

Machines without an NVIDIA card now earn. They were named
simulated-cpu-device, scored at a floor worth a hundredth of a cent an hour,
and given unpaid work — so a hundred completed jobs showed $0.000000. Your
machine is now named after its actual processor and paid for the time it holds
it open. A GPU is worth far more, and the score says so, but a slower device is
not a fake one.

Export your payout key. e in the dashboard, or pods export, writes it to
a file on your desktop you can import into MetaMask. Shown once in a terminal is
no use to anyone who closed the window.

The benchmark shows its working — throughput and bandwidth against an H100,
your score against its ceiling, and what that pays relative to a 4090.

pods v0.1.1

Rent out an idle GPU, get paid in the real tokenized NVIDIA share on
Robinhood Chain.

curl -fsSL https://pods.family/install.sh | sh

The installer verifies the binary against SHA256SUMS before putting it on
your PATH, and refuses to install if it cannot fetch them. Windows: download
pods-windows-x64.exe directly.

Fixes the v0.1.0 binaries, which defaulted to a coordinator on localhost
and could not reach the network at all. Do not use v0.1.0.

What works today. Install, connect a card, and the coordinator sends it
work and pays for it. Settlement publishes a merkle root on chain roughly
every ten minutes, and you claim to any address you like — the coordinator
never learns it.

What to know before running it. Registration is open, but the pool is
small and payouts are capped per node and network-wide, so this is a pilot
rather than an income. Jobs run in Docker with no network, a read-only root
and no capabilities — a container escape still defeats that, so use a machine
that is not holding your keys. Every trust assumption we have not closed is
in SECURITY.md rather than left to be discovered.