PoolParty security and privacy
Review the security controls for pools of computers you own or trust. The public marketplace for private requests on strangers’ computers is not open. It requires additional verification and an external security audit.
Security controls implemented for beta
Implemented controls are available in the public beta. Download verification details are listed on the download page.
Signed, notarized macOS installs
GreenThe macOS build is signed and notarized by Apple. The Windows build is not signed, and the download page says so in plain words, including what your machine will warn you and why. Being honest about the unsigned one is the reason the signed one means anything.
Files encrypted before storage
GreenEncrypt, split, scatter. A file is encrypted on the machine that holds it, broken into pieces, and spread across nodes that each keep bytes they cannot read. Any two of three pieces rebuild it, so a machine going away does not cost you the file.
Permissions for each app
GreenEvery application that reaches your pool comes through its own door with its own consent. Granting one tool access is not granting them all, and each grant is revocable on its own.
Limits on resource contribution
GreenContribution is idle-only and plugged-in, the thermal limit cannot be waived, and it stops the instant you touch the keyboard. “Stop everything now” is always on screen. A consent gate is never pre-checked — not at install, not ever.
Rate limits and auto-update
GreenEvery door that faces the network is rate-limited. Updates are signed, delivered over the same verified channel as the installs, and reversible — there is a rollback path and a hold, so a bad update is something you step back out of rather than something you live with.
Opt-in-only diagnostics
GreenNothing about how you use the app is sent anywhere unless you turn diagnostics on for a specific problem. Off is the default and off is the resting state; it does not quietly switch itself back on.
Security requirements for the public marketplace
One is live, two are next. Until all three are green, strangers do not serve strangers — and the product is designed so that opening each one changes no architecture, only a permission.
Attestation
In the betaEvery node proves itself to the hub every five minutes, and one that stops answering is quarantined until it proves itself again. The live rung binds code identity with a software key, stated as such; the hardware rung — Secure Enclave on macOS, TPM on Windows — joins when the platform allows it, and the page will say so.
Sampled verification
NextRe-running a sample of work and checking it against known-good answers, on top of structural verification. This is the gate that money waits on: without it, a machine can bill for work it invented.
No-plaintext serving
NextEnd-to-end encryption from the person asking to an attested machine answering, with billing taken from attested counts. The sealed-storage principle, extended to inference — so a stranger's machine can do the work without reading the question.
An external security audit comes before any stranger-facing gate opens. Not after launch, not once there is revenue — before the first stranger's work runs on somebody else's machine for money.
Features that require further security verification
- The marketplace. Strangers serving strangers — someone else's idle machine answering your question, and yours answering theirs.
- Payouts. Money out, with the identity and tax obligations that come with it. None of that exists today and none of it is promised.
Provenance. The project keeps a dated, hash-committed record of what exists and when — a statement that reveals nothing private and commits to everything claimed. The build log is the readable half of it.
A public cryptographic timestamp of that record is prepared and has not been anchored yet. When it is, the anchor and the date go here, and you will be able to check them without asking us. We would rather say that plainly than let a word like “timestamped” do work it has not earned.
The beta supports private pools on computers you own. The public marketplace and payouts remain gated on additional verification.