Pular para o conteúdo principal

Run a worker

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.

A worker is a DeepSeek Harness plugin that shares the models already installed on this machine, at a price you set. It runs Ollama locally; there is no cloud API key and no metered inference bill.

Requirements​

  • DeepSeek Harness 0.2.2-rc.1 or newer, and Node 22+.
  • Ollama with at least one model pulled (ollama pull qwen3:8b, for example).
  • A Solana wallet with a little SOL for fees. The plugin generates one for you.

There is no GenKaKu token and no staking. You earn USDC; you spend fractions of a cent of SOL on network fees and rent.

Install​

In DeepSeek Harness open Plugins → Add plugin, paste:

@genkaku/dsh-worker-plugin

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

dsh plugin add @genkaku/dsh-worker-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.

A GenKaKu worker entry appears in the sidebar.

First start​

The plugin looks for Ollama at http://127.0.0.1:11434 and starts ollama serve itself if it is installed but not running. The first panel section shows whether Ollama is running and how many models it found.

When the offer board is empty, the plugin lists every local model at defaultPricePerHour, which is 0 by default. That is deliberate: a machine whose owner has not set a price should not put a price on their hardware.

Set a price​

Open Models offered in the panel and give each model an hourly price in USDC, as an integer with 6 decimals of precision (so 250000 is 0.25 USDC/hour). Leave it at 0 to serve the model for free.

  • A paid model deposits USDC into a per-session escrow and settles with a receipt the user keeps and you sign for.
  • A free model is served without touching the chain: no session, no fee, no transaction.

Billing accrues per started minute of a session, so a two-minute job pays two minutes at the hourly rate, not a full hour.

Your listing rate on chain is the most expensive model you publish, quoted per minute. It is a ceiling: every session against you must be priced at or below it. If a client quotes less than the model's own price, your sidecar refuses the session before generating a token, so nobody gets a cheap ride on an expensive model.

Name, visibility and pairing​

Name & access in the panel holds three things:

  • Display name — a personal name, an ID or a nickname. Users see it next to your models, can search for it, and can sort the network list by it. It is not written on chain: the chain only ever holds your wallet, peer ID and locator.
  • Public / private — public is the default: the worker joins the directory and the seed, and anyone can dial it. Private removes it from both. Its chain row still exists because settlement pays that account, but the row carries no address, so there is nothing for a stranger to dial.
  • Pairing codes — the only way into a private worker. Press Generate pairing code, then send the genkaku1.… string to the person you want to allow. A code is single-use, expires after 15 minutes, and is kept only as a hash: losing the file cannot leak a usable code.

Pairing binds the wallet of the person who redeems it, not the string. A user's wallet key is also their libp2p identity, so every later connection is authorised by the transport handshake itself — no token travels with a request, and a stolen code is useless from another machine. Paired wallets lists who is allowed; unpair removes one immediately, and the next connection is refused.

Private does not mean free: set a price as usual, and 0 still means free. A private worker is paid through the same escrow as a public one.

Switching visibility restarts the worker half, because the directory entry and the seed announcement are decided at start.

Publish on-chain (optional)​

This section applies to public workers; a private one is never listed.

The Directory switch writes your peer ID, rate and locator into the program, so users can find you without knowing your address in advance.

It is off by default, and it only turns on when this machine has a globally dialable address. A listing whose address nobody can dial is worse than no listing. Publishing costs one transaction, and a locator is permanent once it is on chain — a hostname or IP written there cannot be withdrawn, only replaced.

Peers on the same LAN can connect without a directory entry, using a manual multiaddr in the user plugin.

With settlement on, the plugin writes your Worker account even when publishing is off: the settlement instruction pays that account, so it has to exist. Such a row carries no address and is invisible to discovery, which is exactly what a LAN-only worker wants.

Wallet and payout​

The Wallet section shows:

  • the worker address,
  • SOL (fees) and USDC (earnings) balances,
  • unclaimed in escrow — settled income that is already yours but still sits inside the session escrow,
  • a Claim button that moves that balance into the wallet.

Each session pays out separately: a settlement credits the session, and ten minutes after the last one, anyone (including you) can claim it. The delay is the window in which the user can still close a session, so you cannot be paid for a minute they were about to cancel. The panel button does the whole queue.

Claiming is a transaction, so the wallet needs a little SOL. USDC is what the worker earns, not what it spends.

The private key is stored in plain text, mode 0600, at ~/.dsh/genkaku/genkaku.keys.json. It is the wallet AND the libp2p identity: back it up before moving the machine to a new disk, and treat anyone who can read that file as the owner of the wallet. Rotating it changes your peer id too.

Model tiers​

The marketplace labels each model from Ollama's reported capabilities and parameter count:

TierMeaning
agentHas tools and at least 9B parameters — suitable for an agent loop
lightHas tools but is small or of unknown size — tool calls may be unreliable
chatNo tools capability — not suitable for agents

The tier is a label, never a filter. Nothing stops you listing a chat model; the user just sees that it cannot drive an agent.

Thinking models run with think: false by default so a single request does not spend its budget on hidden reasoning. Set GENKAKU_OLLAMA_THINK=1 before starting DeepSeek Harness to keep Ollama's default behaviour.

Ports and networking​

  • libp2p listens on /ip4/0.0.0.0/tcp/4001 and /ip6/::/tcp/4002 by default. Open the TCP ports you configure if you want direct connections.
  • The local status server binds the first free port in 47821–47826. Two DSH profiles on one machine each need their own port; if you see "Loading worker status…" forever, another profile probably owns the range.
  • On Windows, allow Node through the firewall when the worker first starts.

Troubleshooting​

Ollama is not detected. Run ollama serve once, or press Start Ollama in the panel. If Ollama lives elsewhere, change ollamaHost in the plugin settings.

The Directory switch is greyed out. The machine has no globally dialable address. Same-LAN peers can still connect by multiaddr; otherwise the session will have to go through the seed relay.

A session was served but the balance did not move. Settlement credits the session, not the wallet, and the payout waits ten minutes. Press Claim; the figure then appears as the wallet's USDC balance.

Claim says nothing is claimable. Either the ten minutes have not passed since the last settlement, or the session is still open (the user has not closed it). Both resolve themselves; the panel button re-reads the chain.

Nothing is listed on npm? Check that you are on registry.npmjs.org, not a mirror that has not synced yet.