Sign in

Demo account: [email protected] / correct-horse

What just happened

    Also watch the server terminal and the browser DevTools Network tab.

    Backend solver test (Go worker)

    Tests how far a non-browser backend gets. The Go worker solves ONLY the proof-of-work puzzles, never the instrumentation. Start it first: cd worker && go run . (listens on :5055).

    Worker response

    — click "Send Challenge to Worker" —

    Redeem result

    — solve first, then click "Test Redeem" —

    Full backend solve (PoW + instrumentation, no browser)

    Chains both backend workers: Go solves the proof of work, Node + jsdom solves the browser instrumentation, then we redeem. Start both: cd worker && go run . and cd instr-worker && npm start (:5056). Expect success on default settings, and a block only when the server sets CAP_BLOCK_AUTOMATION=1.

    Pipeline

    — click "Run full backend solve" —

    Solve a pasted challenge

    Paste a challenge JSON (the body returned by POST /cap/challenge: an object with token and challenges). The backend workers solve it and the solved { token, solutions } appears below — nothing is redeemed or sent anywhere else.

    Solved challenge

    — paste a challenge above and click "Solve pasted challenge" —