See who wants your product, and where, before you build it

• Answers every /knos comment. /knos help lists the commands.
• On /knos fund: asks GitHub to sign one statement that funds this task. Anyone may send it to Solana; it can be used once.
• On a merge that closes a funded issue: reads GitHub's record against the funded terms, and asks GitHub to sign the payment only when every funded check passed and the changed files are in scope.
• Comments, and assigns an issue for /knos take.
• Runs by hand (Actions, knos, Run workflow) to try a payment again.

• Hold or move money. It has no wallet. Money moves only on Solana, after the program has checked GitHub's signature.
• Change your code, branches or settings: it can read, comment and assign.
• Spend a Balance past its limits: only its owner's and listed people's comments count, and no task takes more than its cap.
• Change a task's terms after funding, or take back a payment GitHub has signed for.
• Be changed by a pull request: it runs from the default branch and never uses pull_request_target.
• Vouch for more than its repository can: GitHub signs which workflow ran, at which commit, in which repository, not what it read there.

No secret is needed: Knos's public relay (a server that sends signed statements to Solana) sends them and pays the network fees. Each limit in full, and the optional relay key.

/knos fund

A line of a comment, or of a new issue's description, that starts with it. /knos bounty means the same.

20

The amount, from 5 to 100,000 test USDC, with at most 6 decimals. A version that uses real money would set its own maximum.

checks: test

The checks that must pass on the merged pull request's last commit. If you name none, Knos uses the default branch's required checks, or else the checks that ran on its latest commit. checks: none: your merge alone is the acceptance.

Optional

paths: src/** (the only files a pull request may change), days 30 (when unpaid money goes back: 14 days unless you say, 90 at most), reserve 3 (days /knos take holds the task: 7 unless you say).

Knos: 20.00 test USDC is held for issue #7 until the proof passes. It is paid when a maintainer merges a pull request that closes this issue, if these checks passed at that pull request's last commit: test (the checks you named). The pull request may not change .github/** or .knos/**. If it is not paid by its deadline, the money goes back to where it came from. To earn it: open a pull request whose description says Fixes #7. /knos take reserves the issue for 7 days. For the money to reach you when it is paid, comment /knos address <your Solana address> on your pull request; without an address it waits for you until you bind a wallet (180 days at most).

Who may fund: the repository's owner, or someone the owner's Balance lists.

The terms are fixed: the funding transaction logs them and the task stores their hash. How long a reply takes is measured: see Numbers.

Every /knos comment gets a reply. /knos help lists the commands: /knos take, /knos status, /knos reject, /knos tip.

Payment without a merge is offered only for a black-box check: the submission runs as a separate process and only its output is compared. Of 63 cheating pull requests in the tamper benchmark, plain CI passed 56, in-process acceptance tests passed 7 and the black-box check passed none.

State the task as five or more pairs: an input and the answer it must get. Knos pays the first solution whose command prints every answer; its code runs as a separate process and only what it prints is compared. It sends nothing: you press the last button on each GitHub page yourself.

Of the fee, 0.05 goes to whoever sends the payment to Solana (0.30 on someone's first payment). An order holds from 5 to 100,000 test USDC on devnet; a version that uses real money would set its own maximum.

The program enforces the Acceptance line at release: 0.30% and the floor. Volume rates are a rebate by contract, off chain. Meter is charged from prepaid credits. The Meter line is proposed: the deployed meter program charges 0.05 an evaluation after 10,000 free a month. Control and the Pilot are contract prices that nothing on chain enforces (what the Pilot is). Under a Plan the program only lets the Acceptance rate be lowered, never raised.

One rate applies to the whole amount, and the fee is never under the floor. On an order the funder pays the fee on top; the payee receives the amount in full. On a tip the fee comes out of the amount.

5 test USDC pays the floor, 0.05: 1.00% of it. On devnet the fee is test money: 0 revenue.

What an account was paid, or what its money paid out, one month at a time, with a CSV made in your browser. Each payment is a row of statements/<login>.json. Real and test money are never added together.

The first deployment on devnet: knos-oidc vpWym9azbPU5f2PH2a6n8c4RfmsyUeW2dMuWr1DSHcE and knos-pay 9UzPFbh2A4e4sEPgngKG523FfYLnQ3qPfFVfFTTAdfDi. It finishes the jobs funded on it; new funding goes to the second deployment only. Whether anyone can still change it is read from Solana below.

A verified token is an account owned by knos-oidc. Read it; call nothing. The Rust interface crate depends on nothing else.

docs/reference/OIDC.md says how. An example with its test: examples/oidc_gate. The crate: crates/knos-oidc-interface. IDLs: idl/. A JavaScript client: sdk/settle.

• GitHub's keys are built in. Any other key enters only on a token GitHub signed for the rotate workflow at its fixed commit, waits a day and needs the guardian's approval.
• Every key stops working after 30 days unless that workflow attests it again. Nobody registers a key by hand.
• The guardian can approve a key or revoke one for good. It cannot add a key or change a delay.
• The programs are upgradeable only through a multisig with a public 8-day delay, until an outside review. Which keys are on chain: Numbers.