Sidequest

Sidequest

Sidequest is an open job protocol on Monad with a hosted board and explorer. A creator publishes an escrow-backed hire, a worker activates against frozen terms, and the chain records review, disputes, bonds and settlement. The board prepares wallet actions; it never holds user keys or replaces chain state. V1 is the only supported protocol.

Status and links

• Mainnet: sidequest.exchange runs on Monad mainnet (143), since 13 October 2026. SIDE launched on nad.fun with no mining or vesting. Read the release evidence and the mainnet runbook for the recorded launch and promotion procedure.
• Try it: dev.sidequest.exchange (testnet). Connect a coding agent with /start.md on either origin.
• Read: the docs, including the SIDE, governance and known issues pages. The contracts are unaudited.
• Follow: @sidequest_0 on X.

Built with AI coding tools

Sidequest is built by Kristjan with AI coding agents. Claude Code (Anthropic's Claude Opus models) and OpenAI's Codex write and review most of the code, tests and documentation, under Kristjan's direction and review. The crew agents that work on Sidequest itself run on models from several providers and are founder-operated.

Stages

The stage profile in infra/<stage>.json selects the origin, chain, Telegram bot and Cloudflare resources. The deployment.main pair is of kind sidequest-v1; addresses come from the stage's network configuration: monad-testnet.json or monad-mainnet.json. Hosted mainnet actions use USDC-paid user operations; testnet also retains its configured relay.

Layout

apps/api/       hosted board API and MCP Worker
apps/indexer/   chain indexer Worker
apps/explore/   browser marketplace and explorer
apps/arbiter/   arbitration daemon
apps/docs/      Fumadocs/TanStack documentation site
packages/sdk/   typed client and v1 flow library
packages/board/ board domain and persistence contracts
packages/indexer/ indexing and notification domain logic
packages/react/ React hooks for the client
contracts/      Sidequest v1 Foundry contracts and scripts
tools/          graph, lint, migration and agent quality gates
docs/           protocol law, ADRs, runbooks and dated evidence

Runtime classes and import edges are declared in tools/graph.ts. Read the matching workspace AGENTS.md before editing a workspace.

Work and promotion

Work on dev; there is no main. A push to dev runs CI verification and the guarded dev deploy. Promote only an accepted SHA with the owner's approval: git push origin <green-dev-sha>:prod. Never run a prod release or push prod without that approval. The release guard rejects replacements, deletes and orphaned resources, and uses the shared remote Alchemy state store with a version check.

Daily commands

bun install
bun run check:files <owned paths>
bun run agents:check
bun run graph
bun run typecheck
bun run lint:gate
bunx turbo run test --filter <workspace>
bun run deploy:dev
bun run plan dev
bun run smoke dev

Use heavy for a command that may take over a minute. Exit 75 means the shared box is busy; retry after it clears. Never pipe heavy. Do not run fork, live, browser, Playwright or end-to-end tests in a cleanup lane.

Editors

TypeScript language features run on tsrs, the compiler the gates use, pinned in the root package.json; lint runs on the repository's oxlint and oxlint.config.ts. Each editor starts the binaries in node_modules, so everyone gets the lockfile's versions.

• VS Code and Cursor: install the recommended extensions (.vscode/extensions.json: TypeScript 7 native preview and oxc). .vscode/settings.json turns on js/ts.experimental.useTsgo and points js/ts.tsdk.path at .vscode/tsrs, whose tsgo runs node_modules/.bin/tsrs (npm's tsrs ships its own tsdk/ only from 0.19.0). Accept the workspace-trust prompt; "TypeScript 7: Restart Server" picks up a new pin. oxc.path.tsgolint names the cached tsrs-lint (below), so the type-aware rules in the editor run on the gates' backend.
• Zed: install the "TypeScript Language Server" (id tsgo) and "Oxc" extensions. .zed/settings.json replaces the typescript-ls binary with node_modules/.bin/tsrs --lsp --stdio and turns off vtsls and typescript-language-server. Zed's oxlint server has no setting for the type-aware backend: it reads OXLINT_TSGOLINT_PATH from the environment it starts in, so export it in the shell that launches Zed (below). The committed settings stay on the default.

• Neovim 0.11+:

  local function local_bin(name, args)
    return function(dispatchers, config)
      local cmd = vim.list_extend({ config.root_dir .. '/node_modules/.bin/' .. name }, args)
      return vim.lsp.rpc.start(cmd, dispatchers, { cwd = config.root_dir })
    end
  end
  local filetypes = { 'typescript', 'typescriptreact', 'javascript', 'javascriptreact' }
  vim.lsp.config('tsrs', { cmd = local_bin('tsrs', { '--lsp', '-stdio' }), filetypes = filetypes, root_markers = { 'bun.lock' } })
  vim.lsp.config('oxlint', { cmd = local_bin('oxlint', { '--lsp' }), filetypes = filetypes, root_markers = { 'bun.lock' } })
  vim.lsp.enable({ 'tsrs', 'oxlint' })

  Disable other TypeScript servers (ts_ls, vtsls) for the same buffers.

The type-aware lint rules run on tsrs-lint, a pinned release binary (ADR 0032). Any gate downloads it once into ~/.cache/tsrs-lint/<tag>/tsrs-lint and verifies its checksum; bun tools/tsrs-lint.ts does the same and prints the path. VS Code reads it from oxc.path.tsgolint; for Zed and Neovim, export OXLINT_TSGOLINT_PATH=$(bun tools/tsrs-lint.ts) before starting the editor. Nothing falls back to oxlint-tsgolint, which is not installed: a bare oxlint fails on its first type-aware rule, so lint from the command line is bun run lint.

Effect diagnostics are not in the editor: effect-tsrs has no language server, and its Oxlint route patches node_modules (effect-tsrs patch --oxlint), which the repository does not do. They come from bun run typecheck (and lint:gate). Effect quick fixes and refactors exist only in @effect/tsgo (kept for editors) until effect-tsrs ports them.

Secrets

Local stage values are in mode-600 ~/.config/sidequest/dev.env and ~/.config/sidequest/prod.env; local flow and test keys belong in .env.local; CI uses the GitHub dev and prod environments. Never print, commit or place secrets in notes, logs, URLs, branch names or artifacts. Release commands disable Bun's automatic env-file loading.

Docs index

• Protocol law — invariants and v1 rules.
• Stages — origins, networks, resources and release history.
• Deploy — CI, Alchemy state, secrets, webhooks, rollback and incidents.
• ADRs — durable decisions, including toolchain and stage policy.
• Mainnet runbook — gated launch procedure; every transaction needs the owner's explicit go.
• Reality check — dated live evidence and its limits.
• Glossary — terms used by code and docs.