What is GenKaKu?
GenKaKu is a peer-to-peer network for AI compute, delivered as two plugins for DeepSeek Harness. A worker shares the models already installed on its machine through local Ollama. A user points an ordinary agent session at one of those workers and pays nothing.
There is no central server that matches jobs. The directory is a Solana program and the connection is libp2p. A small, clearly labelled sponsored placement at the end of an answer pays the worker for that minute; an optional tip is a direct transfer from the user. Advertisers fund their own campaign on Solana, and the platform never holds the money.
The two plugins
| Plugin | Package | What it does |
|---|---|---|
| Worker | @genkaku/dsh-worker-plugin@0.5.0-rc.8 | Serves this machine's Ollama models and quotes a price |
| User | @genkaku/dsh-user-plugin@0.5.0-rc.8 | Adds the network as a model provider inside DeepSeek Harness |
Both can be installed on the same machine. Each owns its own settings document and its own wallet, so selling and buying stay separate.
Public or private
A worker chooses who can reach it:
- Public — registered in the directory and announced to the seed, as described above.
- Private — absent from both. Its chain row still exists (settlement pays
that account) but carries no locator, so there is nothing for a stranger to
dial. Access is granted with a one-time pairing code (
genkaku1.…) that binds the wallet of whoever redeems it. A user's wallet key is also its libp2p identity, so every later connection is authorised by the transport handshake itself — no token travels with a request.
Private does not mean free: a private worker sets a price like any other, and
0 still means free.
A worker also publishes a display name — a personal name, an ID or a nickname. Users see it next to the models and can search and sort by it. The name is not on chain: the program only ever stores the wallet, peer id, rate and locator.
On the user side the panel is a real market list: search by model, worker name or wallet, sort by price, latency, sessions served, model or worker name, and tick the models that should appear in the chat model picker — at most ten, counted per worker and model.
The three protocol pieces
| Piece | What it is | Where it lives |
|---|---|---|
| Directory | One account per worker: peer id, rate, address, settle count | Solana |
| libp2p | Connection between user and worker | Between the two peers |
| Escrow | Session deposit, settlement and payout | Solana |
The directory and the escrow are one program, not two. They keep separate configuration accounts with separate owners, so either half can be handed to a different operator later, but there is a single deployment to audit and a single id to publish.
One key, three jobs
A GenKaKu identity is one ed25519 key. That same key is the Solana account, the libp2p PeerId and the signer of every receipt. A libp2p PeerId is just the multihash of the public key, so the wallet address is literally inside the address you dial: a client can prove that the peer it connected to is the party it is paying, without a handshake, a registry lookup or any trust.
What it is not
- No token. No GenKaKu token, no sale, no staking, no treasury token.
- Not a cloud API. Models run on the worker's own hardware, on the worker's own electricity.
- Not a managed service. GenKaKu Labs operates no inference capacity and holds no user funds. The 1% fee goes to a treasury address published in the escrow configuration.
Pricing in one sentence
The worker sets an hourly quote; billing accrues per started minute, so a two-minute job pays two minutes. A quote of 0 means free: the model is listed and served, and no session or transaction is involved.
Networks
| Purpose | Cluster | Money |
|---|---|---|
| Production | Solana mainnet-beta | Circle's USDC (SPL) |
| Development / staging | Solana devnet | a 6-decimal test token minted on devnet |
Both clusters run the same program binary at the same address, so a session that works on devnet exercises exactly the same accounts as production. A receipt carries the cluster it was made on; a devnet session can never settle against mainnet USDC.
Status
Production. The program is deployed, the plugins are published on npm, and both
halves are dual licensed. The software is audited by use, not by a third party —
read the program or ask security@genkaku.app before you put serious money
through it.
Where to go next
- How it works — discovery, connection, inference, settlement
- Run a worker — share your Ollama models
- Use network models — install the user plugin
- Architecture — what runs where
- Safety and privacy — what is visible, and to whom
License
Source is dual licensed: AGPL-3.0-or-later for open-source use, or a commercial license for integrations that cannot accept AGPL's copyleft terms. Commercial licensing: legal@genkaku.app.