Aller au contenu principal

Use network models

0.5 preview

Users pay nothing in 0.5. Sponsored placements pay workers, and wallets are used for ads and tips. The escrow/session wording below describes 0.2; see Ads, wallets and languages.

The user plugin adds the GenKaKu network as a model provider inside DeepSeek Harness. From an agent session you pick a peer's model the same way you pick a local one. There is no account, no email and no API key.

Requirements​

  • DeepSeek Harness 0.2.2-rc.1 or newer, and Node 22+.
  • A Solana wallet. The plugin generates one, or you can import an existing one.
  • A little SOL for network fees and USDC to pay for compute.
  • USDC: Circle's SPL USDC on mainnet, a test token on devnet.

Install​

In DeepSeek Harness open Plugins → Add plugin, paste:

@genkaku/dsh-user-plugin

Leave the install source on Default registry (registry.npmjs.org), confirm, and restart DeepSeek Harness. From a shell:

dsh plugin add @genkaku/dsh-user-plugin@0.5.0-rc.8

This preview publishes a prerelease, so the command above names the exact version 0.5.0-rc.8 instead of a dist-tag: a tag does not resolve to this build.

The worker and user plugins can live on the same machine. Each keeps its own wallet and settings.

Wallet​

The panel's wallet section generates an ed25519 keypair on first use, or imports one as base58 — the format Phantom and solana-keygen show you — or as the JSON byte array that solana-keygen writes to a file. It shows:

  • the address,
  • SOL (fees),
  • USDC (spendable balance).

The private key is stored in plain text, mode 0600, at ~/.dsh/genkaku/genkaku.keys.json. We never hold it and cannot recover it.

On devnet the panel can mint test USDC, which has no value. On mainnet there is no mint button: you buy USDC wherever you normally buy it.

Find a worker​

The panel lists what the network offers:

  • Models on the network — each row is one worker + model, with the worker's display name, hourly quote, tier and measured latency.
  • Workers discovered — peers found through the on-chain directory and the seed relay. The count is what discovery can see right now, not a global total.

The list has a search box (model, worker name or wallet) and a sort menu: recommended, lowest price, lowest latency, most sessions served, model name, or worker name. The order is shared with the chat model picker, so the first ten rows are the ten a new install offers.

Ticking a model is what puts it in the chat model picker. The unit is the worker and the model, so the same model from two workers is two tickable rows, and at most ten can be ticked. A tick marks one specific worker: the picker shows worker · model for exactly that reason. The bridge drops a tick whose worker has gone away, and puts it back when that worker returns.

The tier label (agent / light / chat) comes from the worker's Ollama capabilities. Only agent models are meant to drive a tool-calling agent loop; chat models are marked not suitable for agents, but nothing prevents you from using one for plain chat.

If you know a worker's multiaddr, add it under Manual workers; that works on the same LAN and needs no directory entry.

Private workers​

A private worker is deliberately absent from the directory and the seed. Its owner sends you a one-time pairing code (genkaku1.…). Paste it under Private workers and press Pair: the code is exchanged once and bound to your wallet, and it cannot be used by anyone else afterwards. The row then shows whether that worker is online (green), offline, or still being checked.

Paired workers are ordinary rows in the list — same ticks, same price, same session. Forget removes one locally; the worker's own paired-wallet list is managed by its owner.

Run a session​

In a DeepSeek Harness session, open the model picker and choose a GenKaKu model. The plugin:

  1. dials the worker directly, or through the seed relay if a direct connection is impossible,
  2. for a paid model, deposits ten minutes of USDC into the session's escrow before the first token,
  3. streams tokens back as Ollama generates them,
  4. settles when the session ends and closes the session, which returns whatever the deposit did not cover.

Free models (quote 0) skip steps 2 and 4 entirely: no session, no fee, no transaction.

What a session costs​

ItemWho pays
InferenceYou, in USDC, per started minute
Network fee to openYou, a fraction of a cent in SOL
Network fee to settleThe worker
Platform fee1% of the settlement, to the treasury

A paid session therefore costs two chain transactions, one from each side. If the session ends before a single started minute is billable, the whole deposit comes back.

Billing is by started minute: stopping after ten seconds still bills one minute, at the worker's hourly quote divided by 60.

Spending limits​

The wallet is a payment front end, not a vault: the agent is meant to run a session without asking you every time. What it must not do is spend without a ceiling. The Budget card in the panel is that ceiling, and it is modelled on the credit limits you already know from API keys.

FieldWhat it doesDefault
NameThe label that appears in a refusal messageeveryday
Credit limitMost USDC this key may spend in a period10
Resetnever, daily (midnight UTC), weekly (Monday), monthly (the 1st)never
ExpiresA fixed date; after it, paid sessions stopoff
EnabledThe on/off switch for paid sessionson
Per sessionMost USDC one session may prepay2
Max price per hourModels priced above this never reach the pickeroff

Edits commit as you leave a field — there is no Save button to forget. A blank amount means no limit for that field, not zero.

The card also reports what has been spent: total, today, this week and this month, a table per model, and the last twenty sessions with their transaction signature. The four windows are computed from the session log; total is the policy's own lifetime counter, so it never goes down when an old log is trimmed.

What a refusal looks like​

The policy is checked before anything is signed. A paid session that the policy does not allow is refused with HTTP 402 and a JSON body naming the reason:

codeMeaning
budget_exhaustedThis period's credit limit cannot cover the deposit
session_capOne session would prepay more than the per-session cap
price_capThe model's quote is above the per-hour cap
policy_disabledEnabled is off
policy_expiredThe expiry date has passed

A refused session leaves no trace on chain — no deposit, no fee, no transaction — and the wallet's signature count does not move. Models above the price cap are filtered out of the picker so you never pick a model you cannot pay for.

Free models (quote 0) are exempt from the budget, and Enabled only blocks paid sessions: with the switch off, free models keep working.

Where it lives​

The policy is one local file, ~/.dsh/genkaku/policy.json, mode 0600, next to the spend log spend.jsonl. It is not an on-chain account and not something the worker can see: it is your own software refusing to build a transaction. A hand-edited file cannot inject a negative limit, an unknown cadence or a bogus reservation — the parser falls back to the documented defaults.

Two accounting rules are worth knowing:

  • opening a session reserves the deposit immediately, so it counts against the budget while the session runs; settling commits what the worker actually billed and releases the rest;
  • a reservation still open after 30 minutes is treated as spent. A crash between opening and settling can therefore over-count your usage, but the one guess that matters — assuming a deposit came back — is never made.

Delete policy removes policy.json and returns to the defaults above. It does not touch the wallet or its funds. To stop spending without losing your settings, use Enabled instead.

Settings​

  • Payments — with settlement on, each paid session opens a real escrow. Turn it off for free/dev sessions that sign nothing on-chain; turn it back on before using the network against real workers.
  • Manual workers — pin a worker multiaddr by hand.
  • Refresh — re-read the on-chain directory and the seed. The bridge restarts when the scan finishes, and a profile that changed its wallet also needs a restart before it can transact.

The local bridge binds the first free port in 47821–47826 and only answers if it is the user half; a worker status server on the same machine will not be mistaken for it.

Common questions​

Do I need to trust GenKaKu Labs?
You need to trust the program and the code. No server holds your funds or your prompts.

Can I use it without a wallet?
Only for free models with settlement off. Paid sessions and identity are the wallet.

Is this mainnet?
Yes: production settles Circle's USDC on Solana mainnet-beta. The panel shows which cluster the build is on. Staging builds settle a valueless test token on devnet — check before you fund anything.

Who can see my prompts?
The worker that serves them, always. If the session goes through the seed relay, the relay operator sees connection metadata — addresses, timing and volume — but not the encrypted content.

Why did my model disappear from the picker?
The adapter probes the local bridge ports and only accepts a bridge that reports the user role. A stale port owned by another profile is ignored; it comes back on the next refresh.

I was charged for a session that failed.
Settlement only happens when the worker signs it, and it can only bill minutes the client's receipts covered. If the answer never arrived, the client closes the session and the deposit returns. A session that produced tokens for two started minutes is billed for two minutes even if the answer was cut off — that is what "started minute" means.