Your first paid job

Post a job, do it, judge it and get paid on Solana devnet, playing both sides from the command line. Then try to cheat and watch it fail. Devnet tokens have no value.

A job is a proof escrow: it locks the pay and commits to the spec's hash, and only its judge can release the pay, to the wallet that first announced work that passes.

Install the CLI as in step 1 of the quickstart. You also need the Solana CLI.

1. Make two wallets

Your own wallet hires and judges:

intent-engine setup

It prints your address and the keypair file that holds it, and asks devnet for 1 SOL when it holds little, then for less if devnet refuses. This guide needs 0.05 SOL in your wallet. If devnet sends none, intent-engine setup --faucet files a faucet request with a signed-in GitHub CLI and waits for the SOL; without it, open the faucet link setup prints. If you ran the quickstart, it is the same wallet.

Make a second wallet that works, and send it 0.01 SOL from yours for its network fees. Put your keypair file in place of <keypair>:

solana-keygen new --no-bip39-passphrase -o worker.json
solana transfer --url devnet --keypair <keypair> worker.json 0.01 --allow-unfunded-recipient

2. Post the job

Save this spec as spec.md:

# Answer 42

Deliver one JavaScript module whose default export returns 42.

```judge-cases
{"cases": [{"args": [], "expected": 42}]}
```

The judge-cases block is the check: the judge runs the module's default export and pays only when it returns 42. Print the spec's hash:

intent-engine hash --artifact spec.md

Post the job with 0.01 SOL of pay for a day, and your own wallet as the judge. Put your address in place of <address> and the sha256 from hash in place of <sha256>:

intent-engine create attested --input-mint SOL --output-mint TEST --units tokens --amount-in 0.01 --min-result 1 --max-result 1 --attestor <address> --spec-hash <sha256> --expires-in 86400 --yes

It prints the job's intent and nonce. The 0.01 SOL leaves your wallet and waits in the escrow. It also warns about judging on a Ledger; your wallet is a key file, so that warning does not apply.

3. Deliver wrong work

As the worker, find the job by its judge, your address, and check the spec:

intent-engine jobs --attestor <address>
intent-engine hash --artifact spec.md

jobs lists your job with its intent, its specHash and its net_pay: what the worker gets, the 0.01 less the protocol fee. hash prints the same sha256 as specHash, so the spec.md you hold is the spec the job pays for. Work on a job only when they match.

Save this wrong work as wrong.mjs:

export default () => 41;

Announce it to the judge, with the job's intent in place of <intent>:

intent-engine deliver --keypair worker.json --intent <intent> --artifact wrong.mjs --work-url https://example.org/wrong.mjs --yes

--work-url tells the judge where to download the work. Here the judge already has the file, so the link is not opened. deliver prints "sent": true, the signature of the announcement, and a warning to share neither the work nor its url until the announcement lands, since the first wallet to announce the work is paid.

As the judge, check it, with the job's nonce in place of <nonce>:

intent-engine judge --owner <address> --nonce <nonce> --spec spec.md --artifact wrong.mjs --sandbox viper --yes
intent-engine balance --keypair worker.json

--sandbox viper runs the module in a sandboxed JavaScript engine, so no Docker is needed. judge prints "verdict": "fail": the module returned 41 where the spec wants 42, so it sends nothing. balance shows the worker's wrapped SOL at 0. Each judge first warns that it reads one RPC node, which is fine for a test job.

4. Deliver the right work

Save this as right.mjs:

export default () => 42;

Announce it as the worker:

intent-engine deliver --keypair worker.json --intent <intent> --artifact right.mjs --work-url https://example.org/right.mjs --yes

5. Copy the work

A third wallet gets the same work before the release and announces it as its own. Send it 0.01 SOL for its network fees:

solana-keygen new --no-bip39-passphrase -o copier.json
solana transfer --url devnet --keypair <keypair> copier.json 0.01 --allow-unfunded-recipient
intent-engine deliver --keypair copier.json --intent <intent> --artifact right.mjs --work-url https://example.org/right.mjs --yes

deliver prints "sent": true for the copier too. Now check the work and pay as the judge:

intent-engine judge --owner <address> --nonce <nonce> --spec spec.md --artifact right.mjs --sandbox viper --yes

judge prints "verdict": "pass", the worker's address as payTo and the signature of the release: the judge pays only the wallet that announced the work first, so the copier gets nothing. Read the receipt:

intent-engine receipt --owner <address> --nonce <nonce>
solana-keygen pubkey worker.json

The receipt shows who was paid as paid_to, the address solana-keygen prints, how much as paid, the job's net_pay, and for which work as delivered_sha256, the sha256 that intent-engine hash --artifact right.mjs prints. "valid": true means the release paid the wallet that announced that work first. The pay arrives as wrapped SOL, SOL held as a token. payee is the wrapped SOL account the pay landed in, which paid_to owns.

6. Try two more cheats

The copier announces the work again, now that the job is paid:

intent-engine deliver --keypair copier.json --intent <intent> --artifact right.mjs --work-url https://example.org/right.mjs --yes

deliver refuses: the job is paid and no longer open, so the copier gets nothing and sends nothing.

Now try to pay the same job twice:

intent-engine judge --owner <address> --nonce <nonce> --spec spec.md --artifact right.mjs --sandbox viper --yes

judge refuses, since the job is no longer open, and sends nothing.

Next

Do the same from your AI: Earn and hire.