Aller au contenu principal

Safety and privacy

0.5 preview

Users pay nothing; sponsored placements and tips pay workers. Escrow/session wording elsewhere describes 0.2 and is being retired. See Ads, wallets and languages.

The short version: the website has no analytics, the plugins have no telemetry, and the only public data is what the protocol needs to work.

This website​

Static files served by Caddy. No account system, no analytics, no advertising pixel. Fonts, scripts and images are served from the same host. The homepage makes one outside request: a getAccountInfo against a public Solana RPC to read two counters in your browser. That provider sees your IP address; we do not proxy or log the request. With JavaScript disabled the numbers render as dashes and nothing is sent.

The server keeps standard access logs for operational security, which include IP addresses. They rotate at 20 MiB with five files kept and are not used for profiling.

One functional cookie, NEXT_LOCALE, records the language you pick. Theme choice lives in localStorage under genkaku_theme and is never sent to a server. Neither is used for tracking, so there is no consent banner.

The plugins​

Neither plugin reports usage. They talk to:

  • a public Solana RPC, to read the directory and move USDC. GENKAKU_RPC_URL overrides it, which is also the way to keep your addresses off a shared endpoint;
  • the seed relay, to discover peers and to carry a session when a direct connection is impossible;
  • the worker you chose, to run inference.

Prompts, filenames and model names are not sent to us. There is no telemetry endpoint in either plugin.

Keys​

Wallets are generated locally. The private key is stored in plain text, mode 0600, at ~/.dsh/genkaku/genkaku.keys.json, because DeepSeek Harness exposes no keyring codec. Anyone who can read that file on your machine can spend the wallet. Back it up, and do not sync that directory to a shared drive.

The user and worker plugins each keep their own key, so selling and buying do not share an identity. A worker's key is also its libp2p PeerId: rotating it changes who it is on the network as well as where it gets paid.

Spending limits​

The user plugin also keeps a spending ceiling in ~/.dsh/genkaku/policy.json (and settled sessions in spend.jsonl), both mode 0600. This is a local file, not an on-chain account: a worker never sees it, and disabling it or lowering the limit cannot be overridden by anyone else — it is your own software refusing to build a transaction. It is not a per-payment prompt either: a session inside the policy still runs without asking you, which is the whole point of a ceiling.

The limit is enforced in the bridge, so an HTTP client that bypasses the panel gets the same answer. The only thing a refusal costs is a 402; no deposit is taken and the wallet signs nothing.

During a session​

Inference runs on the worker you choose. The worker operator can see the prompts and outputs it serves; the marketplace stores neither.

If the session is carried by the seed relay, the relay operator can see connection metadata — peer addresses, timing and volume — but the libp2p stream is encrypted, so it cannot read the prompt or the reply.

A worker's wallet and peer ID are public by design, because that is how the directory works. Locators are optional; by default the worker plugin does not publish your public IP address. Publishing one is explicit and permanent.

Private mode and pairing​

A worker can run privately: no seed announcement, no locator on chain, and an allowlist of wallets. That hides it from discovery, not from the relay — a paired user still reaches it through the seed, whose operator sees circuit metadata like any other relayed session. The chain row also stays, because settlement pays it.

Pairing codes are single-use and expire after 15 minutes. The worker stores only a hash, and redeeming a code authorises the wallet behind the connection, so the code itself is worthless to anyone who intercepts it. Treat it as a sensitive link anyway: whoever redeems it first becomes a paired user until the owner unpairs them.

The user's tick list, sort order and paired-worker list are local to ~/.dsh/genkaku/. They are not published, not linked to the wallet on chain, and not visible to a worker.

A session's deposit, price and settlement are public too: a chain records what was paid, from which address, to which worker. That is a receipt, not a chat log — the prompt and the answer never touch the chain, only their hashes.

What is public and permanent​

Registrations, session opens, settlements, claims and closes are public and permanent. Nothing written to a chain can be edited or deleted by us, including after you stop using the software.

Deleting ~/.dsh/genkaku/ removes the local keys and state. It does not and cannot remove on-chain history. Access logs expire through rotation.

Content​

There is no automatic content filter. The protocol has no hook that inspects a prompt before a worker sees it, and the worker's declared policy is a commitment, not an enforced rule.

What does exist:

  • the worker operator sees each request and can refuse or stop serving,
  • anyone can refuse to run a worker, or to connect to one,
  • the software is open source, so these limits are inspectable rather than promised.

Do not use the network for illegal content. Running a worker does not oblige you to serve requests you do not want to serve.

Threat model in one table​

RiskWho can do itMitigation
Read your promptThe worker you pickedChoose a worker you trust; nothing else can hide it from them
Read your promptNobody else on a direct linklibp2p encryption
See who talks to whomThe relay operator, for relayed sessionsDirect connection; metadata is not content
Spend your walletAnyone who reads genkaku.keys.jsonFile permissions, disk encryption, backups
Spend past your ceilingAn agent loop that keeps opening sessionspolicy.json credit limit; checked before any transaction is built
Be billed past the receiptA malicious workerThe worker can only settle what the client's receipts cover, and only its own signature can move the money
Lose a deposit to an abandoned sessionA worker that goes offlineThe user can close, and after a day of silence anyone can
Recover a lost keyNobodyBack it up; there is no support path

Reporting​

Security issues: security@genkaku.app. Legal notices: legal@genkaku.app.