3SAT Docs

1. 1Prepare a DIMACS CNF instance.
2. 2Search the database for an existing verified answer.
3. 3If no answer exists, upload the instance directly to R2 and wait for background validation to report ready before creating the bounty.
4. 4Select USDC or $3SAT as the bounty payment asset.
5. 5Review reward, solver bond, verifier reward pool, timing windows, and verifier quorum.
6. 6Approve the selected payment asset and create the bounty with your wallet.
7. 7After finalization, access the winning answer without paying a separate unlock fee.

1. 1Browse the marketplace for open bounties.
2. 2Download a selected instance or run the solver client.
3. 3Generate a valid SAT assignment or UNSAT proof artifact.
4. 4Upload with CLI 0.1.1 or Solver 0.2.0 and wait for ready before preparing a commit; keep upload receipts and pending proof files when resuming.
5. 5Approve the solver bond in the bounty payment asset.
6. 6Commit the solution hash while the bounty is open for solving.
7. 7Reveal the solution before the post-commit reveal deadline.
8. 8Wait for verifier attestations and keeper finalization. Payout uses the bounty payment asset.

1. 1Verification is currently operated by the official 3SAT verifier node.
2. 2Third-party and personal verifier node onboarding is temporarily paused.
3. 3Public verifier client downloads are disabled until verifier onboarding opens.
4. 4Issuer-created bounties use verifier quorum 1 during this official-verifier launch phase.
5. 5The official verifier checks SAT assignments and supported UNSAT proofs, then submits attestations on-chain.

1. 1Search large CNFs by exact file hash; format-normalized and variable-renamed searches have separate small-file/count limits.
2. 2Review the bounty code, payment asset, answer status, and access price.
3. 3If you are the issuer, download the finalized answer bundle without a separate unlock payment.
4. 4If you are a buyer, approve and pay the answer access fee in the bounty payment asset.
5. 5For a supported small non-raw match, download a rebuilt SAT bundle or poll the UNSAT transform job until the target checker accepts the proof.
6. 6For original or large raw-exact answers, use the authorized manifest's direct problem and answer download links; CLI verifies both files and builds the ZIP locally.
7. 7Browser direct links show expected hashes but do not verify downloaded bytes. Verify digests yourself or use CLI.

Standardize CNF before search

For small inputs within the interactive budget, normalize DIMACS formatting and compute normalized fingerprints. Use CLI streaming normalization for large files.

curl -X POST https://3sat.network/api/protocol/sdk/cnf/standardize \
  -H "content-type: application/json" \
  -d '{"text":"p cnf 2 1\n1 -2 0\n"}'

Search the verified answer database

Search exact, format-normalized, and variable-renamed CNF fingerprints to check whether a finalized answer already exists.

curl -X POST https://3sat.network/api/protocol/search \
  -H "content-type: application/json" \
  -d '{"text":"p cnf 2 1\n1 -2 0\n"}'

Resolve a public bounty code

Use the public SAT-... code shown in the marketplace instead of relying on small internal numeric ids.

curl https://3sat.network/api/protocol/sdk/bounties/SAT-XXXX-XXXX-XXXX