OPERATIONAL anchoring on mainnet · 1 anchors this hour (4/1000 all services) last issue 20h 28m ago report a problem

🔗 URL shortener

In plain terms: a link shortener — but instead of trusting bsv.cx to remember what a short link points to, that mapping is written into the Bitcoin SV blockchain itself, so anyone can check it's real without asking us. Short links whose code is derived from the URL and anchored on-chain — so the mapping is verifiable and censorship-resistant, not a row in a database someone can edit or delete.

codefirst 7 base62 chars of sha256("bsv.cx:url:" + url)
on-chainOP_RETURN bsv.cx url1 <code> <url>

Endpoints

POST /s{ "url": "https://…" } → create + anchor
GET /:code302 redirect to the target
GET /:code/viewhuman proof page
GET /:code/infoJSON record
GET /s/:code301 → /:code (permanent legacy alias)
curl -X POST https://bsv.cx/s -H 'content-type: application/json' -d '{"url":"https://example.com"}'

Verify it yourself

Recompute the code from the target URL, then read the OP_RETURN in the anchor transaction — it carries bsv.cx / url1 / <code> / <url>. No trust in bsv.cx required.

And you don't have to trust an explorer for this, either. bsv.cx runs its own block-headers service, syncing the chain's headers directly over the BSV peer-to-peer network. For every anchor it recomputes the transaction's block Merkle root from an SPV proof and confirms it against those headers before publishing the proof on the record. Look for the green "✓ Independently verified against bsv.cx's own block headers" line on any proof page, open it, and recheck the same proof against any header source you trust — no explorer, and no bsv.cx, in the trust path.

New to this? A few quick definitions
on-chain / anchoredwritten permanently into the Bitcoin SV blockchain, where anyone — not just bsv.cx — can check it.
hash / SHA-256a short "fingerprint" generated from data. The same input always produces the same fingerprint, but you can't work backwards from the fingerprint to recover the original data — so sharing a hash never leaks what it came from.
OP_RETURNa small public "note" field built into every Bitcoin transaction. bsv.cx writes fingerprints there — that note is what actually gets checked when you verify a proof.
Merkle rootone fingerprint that stands in for a whole batch of items at once, so thousands of files can be proven with a single blockchain entry instead of thousands of them.
x402 / payment-signaturebsv.cx's pay-per-call system — a tiny BSV payment attached directly to an API request instead of a subscription or an account. See pay-per-call.

← back to bsv.cx