constellation@atheron:/security$
// Security and privacy
Your machine stays yours.
What runs, what never does, and what we see.
The network is built so that a job cannot reach your files, your accounts or our keys. Here is how, in plain words.
What runs on your machine
- Strategy backtests and parameter sweeps
- News and text scoring with our own small open models
- Experimental training of small research nets, labelled experimental
- Synthetic data, simulators and stress scenarios
- Only derived data: no coin names, no dates, no exchanges
What never does
- Live trading and order routing
- Exchange keys, passwords or the vault
- Watching markets from your connection
- Full model weights
- Raw exchange archives
A sandbox for every job
Processor jobs run in a WebAssembly sandbox with no access to your files, no network and no clock beyond a counter. Graphics jobs reach your GPU only through a narrow interface: a job can ask to run a model on some numbers, and nothing more.
The app runs as you, never as an administrator. It opens no port on your machine unless you choose to relay traffic for other nodes.
Only signed work runs
Your node runs a batch only when it is signed by our batch key, and that key is itself signed by a root key the app knows. A batch that anyone else sends around is refused.
Our working keys last a day at a time. If a key is ever withdrawn, the notice spreads through the network and every node stops trusting it.
Every answer is checked
Each piece of work goes to more than one machine, chosen by a fair draw over a list we publish. The answers must match, and the machines that agree must belong to different people.
Some jobs have answers we already know. Some we run again on our own machines. Work from new nodes, or work anyone disagreed with, is re-run before its points are paid.
Signed updates, with a way back
Updates are signed and install between jobs. They roll out in stages and roll back on their own if something goes wrong.
The first Beta builds go to testers. Public builds are code signed for Windows and Mac before the public launch, with published file hashes you can check.
Your account and your key
Each machine's key lives in your system's keychain. A stolen key could only ever earn for its own account, and unlinking the machine withdraws it.
Points are worked out from our benchmark for your machine's class, never from its own power meter, so a machine cannot claim more than it did.
What each report tells us
Sent with each report
- Your device class and benchmark score
- Driver, runtime and app versions, and the operating system family
- How long the job took, and the processor and graphics time
- The highest temperature and any throttling
Never sent
- File names or process lists (the games list is checked on your machine)
- Your computer's name or your username
- Your precise location
- Your internet address, beyond the moment a request arrives
How the map places you
When your machine checks in, we use its internet address to place it at its approximate city on the Constellation map. We never use GPS, we don't keep the address, and the public map shows only city dots and counts, never your name, handle or node.
Found a problem?
If you think you have found a security issue, tell us through the chat or the contact page and a person on our team will reply.