Terms of Service

Effective: 2026-06-13 · Version: v2

cocore is alpha software. Read the entire document before using it.

What cocore is

cocore is an experimental ATProto-native protocol for decentralized compute. Anyone can run the provider agent (a Rust binary you install on your own Mac) to serve work, or use the console / API to dispatch jobs to other people's machines.

What you accept by installing the provider agent

By installing or running the cocore provider agent on any machine you control, you affirmatively accept that:

  1. The software has not been independently security-audited. It was built rapidly with significant assistance from generative AI tooling. The cocore maintainers have not subjected it to third-party review, fuzzing, or formal verification. There may be vulnerabilities — known or unknown — that allow attackers to exfiltrate prompts, modify replies, escape the hardened-runtime sandbox, or otherwise compromise the integrity of work served on your machine.

  2. You assume the risk. You alone are responsible for any damage, data loss, financial loss, downtime, or other harm that results from running the agent. The cocore maintainers, contributors, and operators of the cocore.dev exchange disclaim responsibility for any such harm to the maximum extent permitted by applicable law.

  3. Hardened-runtime is best-effort. The agent applies PT_DENY_ATTACH, blocks debugger attachment, and runs in a process configured to deny memory reads. These mitigations raise the bar against casual snooping by the machine operator — they do not guarantee that the operator cannot read prompts they choose to serve. If you're a requester sending sensitive prompts, treat every provider as semi-trusted.

What you accept by sending work

By submitting a job to any provider through cocore (whether through the in-app console, the OpenAI-compatible API, or any other client), you affirmatively agree that:

  1. You will not attempt to harm other machines. Prompts that instruct the model to write malware, scan networks, exploit the provider's host, exfiltrate data, or attempt privilege escalation are prohibited. Prompts that try to manipulate the provider agent's signed receipts, attestation chain, or cryptographic identity are prohibited.

  2. You take responsibility for the prompts you send. Some providers may log inputs. The cocore-provided console encrypts prompts to the provider's published key before transit, but the provider itself decrypts and processes the plaintext — anything you send is potentially observable to the provider.

  3. Compute is priced in tokens, not dollars. cocore runs a closed-loop token economy. There is no card on file, no fiat settlement, no Stripe in the middle, and no exchange rate between cocore tokens and any outside currency. The active exchange (operated by whoever publishes the dev.cocore.compute.exchangePolicy you accepted) denominates everything in tokens (currency code CC) and publishes every parameter that moves your balance:

    • Onboarding grant. Your DID receives a one-time grant the first time it touches the exchange — the policy's tokenGrant, currently 1,000,000 tokens on cocore.dev. Issued exactly once per DID and recorded as a dev.cocore.account.tokenGrant record on your PDS.
    • Uniform rate. The exchange pins a single tokenRate that applies to every provider and model; cocore.dev settles at one balance token per model token (1:1), so a million-token completion costs a million tokens. Providers settling through the exchange MUST price receipts at this rate — their own dev.cocore.compute.provider.priceList is informational for client display today, not authoritative.
    • The 95/5 split. When a provider publishes a receipt, the exchange debits the receipt's token price from your balance, credits 95% to the provider, and routes the remaining 5% (fee.bps = 500) to the treasury. No tokens are minted or burned — the balance changes sum to zero. The fee sits on the provider's side of the ledger, so you see a single debit equal to the receipt price, never a separate surcharge "on top." Jobs you run on your own machine through the exchange (requester DID == provider DID) have the fee waived.
    • Admission floor. The exchange refuses a new job if it would leave your balance below tokenFloor — currently 100,000 tokens — so an unlucky completion can't push you negative at settlement time. If you're under the floor the job doesn't run; you wait for the next refresh.
    • Refresh + rebate. Active members accrue a small weekly refresh (weeklyRefresh, currently 70,000 tokens, issued lazily on your next balance touch), and once a month the treasury redistributes the bulk of its accumulated fees back to active members as a patronage rebate (patronageDistribution), in proportion to how much they used and supplied the network.

    Every one of these numbers is a field on the active policy record, signed under the exchange's DID, so you can verify the rules offline rather than taking our word for them. You can switch exchanges at any time by editing your job's acceptedExchanges field; a different exchange may publish a different rate, fee, grant, or cadence.

Generative-AI disclosure

A meaningful fraction of cocore's source code, documentation, deployment scripts, and these terms themselves were drafted with the help of large language models, including pair-programming sessions with Anthropic's Claude. Human maintainers reviewed each PR before merge, but the volume of AI-generated content is high relative to typical software at this stage. Treat the implementation accordingly.

No warranty

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES, OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT, OR OTHERWISE, ARISING FROM, OUT OF, OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Acceptance

Your acceptance of these terms is recorded as a dev.cocore.compute.termsAcceptance record on your ATProto PDS. That record is portable: any future cocore-aware client can verify that you accepted version v2 on a specific date, against a specific exchange's policy.

If you don't agree with any of the above, do not click "I agree" and do not run the provider agent.