惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

MongoDB | Blog
MongoDB | Blog
J
Java Code Geeks
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
D
DataBreaches.Net
腾讯CDC
GbyAI
GbyAI
I
InfoQ
博客园 - Franky
G
Google Developers Blog
Last Week in AI
Last Week in AI
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
V
Visual Studio Blog
Vercel News
Vercel News
博客园_首页
MyScale Blog
MyScale Blog
Martin Fowler
Martin Fowler
N
Netflix TechBlog - Medium
V
V2EX
T
The Blog of Author Tim Ferriss
M
MIT News - Artificial intelligence
雷峰网
雷峰网
H
Hackread – Cybersecurity News, Data Breaches, AI and More
大猫的无限游戏
大猫的无限游戏
The GitHub Blog
The GitHub Blog

Hacker News - Newest: "AI"

AI can't read an investor deck AI as an attorney? Student uses ChatGPT, Gemini to sue UW over alleged racial discrimination Hacking MCP Servers in AI Systems – The Rug Pull: Tool Changes After Approval GitHub - MeepCastana/KubeezCut: Free Web based video editor Can AI judge journalism? A Thiel-backed startup says yes, even if it risks chilling whistleblowers Coming soon: 10 Things That Matter in AI Right Now DARPA built an AI to fact-check enemy weapons claims What explains heterogeneity in AI adoption? When AI Meets Muscle: Context-Aware Electrical Stimulation Promises a New Way to Guide Human Movements - Department of Computer Science AI Changed How We Build. It Did Not Change What Matters. Linux rules on using AI-generated code - Copilot is OK, but humans must take 'full responsibility for the… Meta spins up AI version of Mark Zuckerberg to engage with employees Code Mode: Let Your AI Write Programs, Not Just Call Tools | TanStack Blog GitHub - Delavalom/graft: Go framework for building AI agents. Type-safe tools, multi-provider (OpenAI, Anthropic, Gemini, Bedrock), zero vendor SDKs. India's TCS tops estimates, says new AI models did not dent services demand Gen Z's fading AI hype Strong feeling: we are in a folded AI reality GitHub - machinarii/total-recall-catalog: A reference catalog of latest knowledge retrieval, memory & RAG systems GitHub - mensfeld/code-on-incus: Give each AI agent its own isolated machine with root, Docker, and systemd. Active defense detects and stops threats automatically.. Quantization, LoRA, and the 8% Problem: Benchmarking Local LLMs for Production AI Iran war: We spoke to the man making Lego-style AI videos that experts say are powerful propaganda Powell, Bessent discussed Anthropic's Mythos AI cyber threat with major U.S. banks GitHub - immartian/bellamem: Persistent belief-graph memory for AI agents. Retrieves decisive context by importance — not recency, not RAG, not /compact. recursive-mode: The Repo-Native Operating System for AI Engineering After the attack on Sam Altman's home, will AI CEO's go on the offensive? The biggest advance in AI since the LLM Opus 4.6 vs GPT 5.4 One Prompt Unity World Generation Test “AI polls” are fake polls Client Challenge Can AI be a 'child of God'? Inside Anthropic's meeting with Christian leaders
co/core — an AI cooperative
lisowski · 2026-06-19 · via Hacker News - Newest: "AI"

an experiment in member-owned AI

co/core is a place where people share the compute they already own to run AI for each other, instead of renting from a handful of giant providers. It's an experiment in inference we build, share, and own together — and your existing code works as-is, because we speak the same standard API everything else does. The models are open ones that run on the hardware people already have.

Have compute to share? Get the cocore app — macOS, Apple Silicon

models available

6 / 5 active (7d)

time to first token

415msp50 · last 100 jobs

combined memory

560 GB RAM

combined cores

150 cpu cores

free to start

1M tokens · one-time

live on the network

Real members. Real machines. Real receipts.

A glimpse of the co-op right now — some of the people who've signed up, some of the machines sharing compute, and the latest jobs they've signed off on. Every one of these is a real, public record.

machines sharing compute

wibbly_appleApple M1 · Jack

chadkohsmacApple M4 Max · Chad Kohalyk

Mac-1Apple M1 Pro · Alex McRoberts

jacks-mac-miniApple M2

MacApple M5

silver-cubeApple M4 Max · Bailey Townsend 🦀

recent job receipts

mlx-community/Qwen2.5-0.5B-Instruct-4bitin 38 · out 46 · did:plc:jijw…lqrpec · 0ms

mlx-community/Qwen2.5-0.5B-Instruct-4bitin 38 · out 9 · did:plc:jijw…lqrpec · 0ms

mlx-community/Qwen2.5-0.5B-Instruct-4bitin 38 · out 119 · did:plc:jijw…lqrpec · 1.0s

mlx-community/Qwen2.5-0.5B-Instruct-4bitin 38 · out 82 · did:plc:jijw…lqrpec · 1.0s

mlx-community/Qwen2.5-0.5B-Instruct-4bitin 38 · out 9 · did:plc:jijw…lqrpec · 0ms

01 drop-in

Just change three lines.

Cocore speaks the same API language as everybody else. Point your existing SDK at console.cocore.dev/v1, drop in a cocore-… key, and keep going — streaming, tool calls, and the usual chat/completions shape all work, no code changes. Host from our presets or any MLX model.

client.pybefore

from openai import OpenAI

client = OpenAI(
    base_url="https://api.openai.com/v1",
    api_key="sk-proj-…",
)

resp = client.chat.completions.create(
    model="gpt-4o-mini",
    messages=[{"role": "user",
               "content": "hello"}],
    stream=True,
)

client.pyafter

from openai import OpenAI

client = OpenAI(
    base_url="https://console.cocore.dev/v1",
    api_key="cocore-7f3a2c…",
)

resp = client.chat.completions.create(
    model="mlx-community/Qwen2.5-0.5B",
    messages=[{"role": "user",
               "content": "hello"}],
    stream=True,
)

02 how it works

You send a request. The co-op runs it.

Your request finds a member's available compute, runs the job, and comes back to you. The whole thing is an open spec — every job leaves a signed, public record anyone can verify for themselves, ours included.

1job

You send a job

Your encrypted prompt heads out into the co-op. Run your prompt for a given model anywhere in the open network, or choose to keep your jobs private to only a trusted circle of co-op friends and their machines.

dev.cocore.compute.job

inputCommitment: sha256

priceCeiling: 2,500 tokens

acceptedTrustLevel: hw

2attest + run

A member runs it

Someone picks up your job, runs it, then returns the result after signing with a key locked in the Secure Enclave that never leaves their hardware — proof of exactly who did the work, and that nobody touched it after.

dev.cocore.compute.receipt

tokens: 38 in · 46 out

price: 84 tokens

enclaveSig: ✓ SE-bound

3settle

Receipts, in the open

A receipt closes out the job — credits go to whomever who ran it, minus a small cut to a shared pot. Each month that pot splits back to members by how much they pitched in, so the cut cycles right back to the people running the network.

dev.cocore.compute.settlement

debit: 84 tokens

credit: 79 tokens

fee: 5 tokens → treasury

03 open by default

You don't have to take our word for it.

Every job writes a receipt anyone can verify on their own, without ever calling us. We can't inflate a balance, fake a payout, or quietly change the rules. And if you don't like how we run things, you can run the whole thing yourself — point your own copy at the same data and it lands on exactly the same numbers.

The record lives with the person who made it

We keep a fast index, but the real, signed record of every job lives on the provider's own account — not locked inside our database.

Receipts check out on their own

A receipt plus our public spec plus the signer's identity is all you need to confirm a job happened — offline, with no cocore API in the loop.

dev.cocore.compute.provider

provider

dev.cocore.compute.attestation

provider · SE-signed

dev.cocore.compute.job

requester

dev.cocore.compute.paymentAuthorization

requester

dev.cocore.compute.receipt

provider · SE-signed

dev.cocore.compute.settlement

exchange

dev.cocore.compute.exchangePolicy

exchange

dev.cocore.compute.dispute

exchange

Here's a real receipt and the records it points back to — the job you sent, the machine's attestation, and the public settlement. Follow the chain and check it yourself.

at://did:plc:jijw…lqrpec/dev.cocore.compute.receipt/3molljt5l3p2s

dev.cocore.compute.receiptsigned · did:plc:jijw…lqrpec

modelmlx-community/Qwen2.5-0.5B-Instruct-4bit

tokensin 38 · out 46

price84 tokens

enclaveSig✓ P-256 / SE-bound

└─ strongRef →job

dev.cocore.compute.job@you.bsky.social

inputHashsha256 7a3f…b9c1

priceCeiling2,500 tokens ✓ within

└─ strongRef →attestation

dev.cocore.compute.attestation@kira.bsky

chipApple M3 Max · SIP on

MDA chain✓ → Apple Root

└─ settled by →exchange

dev.cocore.compute.settlement@cocore.dev

charged84 tokens

payoutdid:plc:jijw…lqrpec · 79 tokens

verifier · plain HTTPS to 3 PDSesverifyReceipt → ok

04 an open standard

An open standard. Run your own exchange.

Underneath the co-op is an open standard for two plain things: making an inference request, and recording what happened afterward — a signed, public account of every job. We run one exchange on top of it, with our rules: one unit in, one unit out, a shared pot that goes back to members. But the standard is the real work here. Anyone can stand up a different exchange — their own pricing, their own membership, their own idea of what's fair — reading and writing the very same records. Ours is just the first one. If co/core ever stops being the version you want, you don't have to ask us to change it; you can go build yours.

the records · signed + public

jobfrom requester

receiptsigned by who ran it

settlementfrom an exchange

any exchange reads + writes them

◆ co/coreyour exchangeanother

share your compute

Share your compute. Help run the co-op.

Download the cocore app, sign in, pick a model or two, and your computer joins the network — running jobs for other members while you're not using it. No Terminal, nothing to babysit; it updates itself. Every job it runs adds to your balance, and a share of everything the co-op does comes back to members each month.

download the cocore app→ open · sign in · serve

Your machine, your key

A key born inside the Secure Enclave is your machine's identity — it can't be copied off the machine, and it signs everything your machine does.

One token in, one token out

The same price for everyone, set in the open. Every job moves tokens three ways: the requester spends, your machine keeps 95%, and 5% goes to a shared pot that goes back to members every month.

Run your own jobs free

Serving a job to yourself costs no fee — but it still writes a receipt, so the trail stays complete.