Ads, wallets and languages
0.5 changed who pays. Users pay nothing; advertisers pay for a sponsored placement, and the worker that served the answer is paid for that minute.
Sponsored placements
- The card sits at the end of a completed answer, in the same seat ChatGPT uses. It is clearly labelled Sponsored, names the sponsor and is dismissible.
- One impression is one sponsored minute. The bridge reports the impression only when the card is actually visible and focused for a second.
- Matching happens on the user's machine from the downloaded catalog; the prompt never leaves the device.
- The advertiser's budget is a Solana campaign account. The program can promise no more than the campaign holds, and the owner can withdraw only money that was never promised.
Self-serve advertising
- Open the user plugin, scroll to Advertise on GenKaKu.
- Fill the category, price per impression, budget, copy, image and keywords.
- The ads service fetches, checks and stores the image, then reviews it. A passing review publishes the listing automatically.
- Fund it: the plugin creates and funds a campaign from your own wallet. The service attaches the campaign address after checking the owner and price on chain.
- The operator can block a listing at any time from the admin moderation page; a block survives a later re-review.
Price band: 0.0001–0.1 USDC per impression. Default claim threshold: 0.03 USDC per campaign. A worker below a campaign's threshold keeps the accrual on chain until enough minutes accumulate; the worker panel lists the threshold and says when a claim is below it.
Wallets
- Users: inference is free. A wallet is optional, and only used for direct tips to a worker. No deposit, no spending limit, no session escrow.
- Workers: the wallet holds the worker identity and receives ad earnings and tips. Claim from Ad earnings in the panel; the worker pays the Solana fee and the USDC goes straight to its wallet.
- Advertisers: the campaign wallet is the user's own wallet. The platform never holds the money and takes no cut.
- Export, import and a fresh wallet are in the panel. Treat the private key as the wallet: anyone who has it owns the funds.
Agent access to a wallet
Both plugins have an Agent access block:
| Mode | Meaning |
|---|---|
| Off (default) | agent wallet requests are refused |
| Ask owner | each request waits for the owner in Pending approvals; one use, five minutes |
| Capped | tips and campaign funding under a per-request/per-day cap; claims allowed; over the cap falls back to Ask |
- Key and identity operations (export, import, new wallet, rotation) are owner-only in every mode.
- Freeze wallet stops both owner and agent actions.
- An approval is bound to the action, amount and recipient by a digest, so it cannot be replayed for a different amount.
- Agents call
POST /genkaku/agent/walletwith the token from~/.dsh/genkaku/agent-token(worker:worker-agent-token). They never see a private key.
This is policy, not an OS sandbox: an agent running as the same OS user can still reach owner routes. Large amounts should wait for out-of-band approval.
Languages
Both panels follow DSH's language (Chinese, English, Japanese, Spanish, French, German, Russian, Portuguese) and offer a manual override that also includes Korean. The website ships the same nine languages.