ready when you are.
Type anything you want into the box. A neon ninja. A flying pizza. A robot DJ at sunrise. Whatever sounds fun.
Every click gets a brand-new puzzle, made just for you, right now. It's tied to this exact moment in time — nobody can save it for later, and you can never get the same one twice.
Your "payment" is a few seconds of math. No money. No password. No data. Just a tiny bit of work to prove you're a real person (or a friendly AI!) and not a spammer.
Once the work is done, unique cyberpunk art appears just for you. Type the same idea twice — you'll get something completely different both times. Try it!
You didn't sign up. You didn't pay. You're using a real internet service with nothing but a few seconds of computer work as your "ticket".
You can't save a puzzle for later. You can't reuse one. You can't pay someone to solve a million and hand them out. The network always checks.
Instead of a subscription, a credit card, or your email address — the "price" is a few seconds of CPU. Cheap for you. Fair for everyone. Impossible to fake.
Your browser asks our BTX node for a fresh matmul_service_challenge_v1. It's anchored to the live mainnet block — every challenge carries previousblockhash, seed_a, seed_b, and a target. No two challenges are the same; expired ones can't be reused.
A solver does real CPU work: build matrices A,B deterministically from the seeds, multiply them in the M31 prime field, compress the transcript through a rolling SHA-256d hasher, and hunt for a nonce64 whose final digest beats target. Roughly ~150M field multiplies per attempt.
The proof (nonce64_hex, digest_hex) goes to redeemmatmulserviceproof. The node re-runs the math (Freivalds + transcript check), marks the challenge consumed, and only then do we mint the ASCII art seeded by the challenge_id. One challenge = one mint. No replays.
The whitepaper's term. Your proof can't be prepaid, replayed, or amortised across requests — it has to be produced against the current chain state, every time.
Your challenge's target tracks BTX's live difficulty per block. Refresh in 90 s, the anchor shifts. Replay an old proof — node rejects it with already_redeemed or expired.
An LLM, a bridge operator, a swarm worker, or a curl one-liner uses the same primitive: "a proof of current work before accepting a request". No API key. No bearer secret. Just work.
▌ STRAIGHT FROM THE WHITEPAPER"Above the base layer, BTX work proofs can be reused as admission tickets. A bridge, relay, or service can require a proof of current work before accepting a request." That ticket "proves not only that the requester holds an identity key, but also that the requester has expended fresh computation now, against current network conditions."
╔═══════════════════╗ ╔═══════════════════╗
║ L2 BRIDGES ║ ║ ADMISSION TICKETS║
║ whitepaper §9 ║ ║ whitepaper §7 ║
║ ║ ║ ║
║ value movement ║ ║ access gating ║
║ banks · swaps ║ ║ ◄── YOU ARE HERE ║
╚════════╤══════════╝ ╚═════════╤═════════╝
│ │
└──────────┬─────────────┘
▼
╔═══════════════════╗
║ BTX L1 ║
║ PoW · 90s blocks║
╚═══════════════════╝
TODAY, AI assistants need accounts. They need API keys. They need your credit card on file. They need you to log in and let them in everywhere.
TOMORROW, an AI agent just does the work — the same way you did here. A tiny bit of CPU = access. No accounts. No passwords. No bills to set up.
IMAGINE your future AI helper booking your flight, calling another AI for help, or paying for a tool — without you handing over a single password. It just spends a tiny bit of math. The service knows it's legit. You stay in control.