We Just Launched SirVeyor on Cardano Mainnet. Here's Everything.

The opening

A year ago I searched my own name on Spokeo. They had my home address, my phone number, an estimated income range, the names of three relatives, and a list of "associates" that was uncomfortably accurate.

I have never given Spokeo anything.

That moment is what kicked off SirVeyor. Today — Sunday May 17, 2026 — we're live on Cardano mainnet, the SRV token is minted with a 100M fixed supply, the first batch of waitlist invites is going out tomorrow morning, and the public on-chain attestation ledger is open for anyone to audit at sirveyor.app/ledger.

This is the post that explains what we built, why we built it on Cardano specifically, and what's next.

What SirVeyor is

SirVeyor is two things in one platform.

One: A consent-first data marketplace. Consumers create an encrypted profile (data stored off-chain, hashed on-chain), set their data-sharing preferences, and receive access requests from businesses. Each request comes with a SRV token payment locked in escrow. The consumer approves or denies. Approved requests release the SRV to the consumer atomically and produce an on-chain consent record.

Two: A privacy toolkit that works whether or not you care about the marketplace side. Privacy Shield runs automated opt-out submissions to 15+ data brokers (Spokeo, BeenVerified, WhitePages, Radaris, FastPeopleSearch, TruePeopleSearch, Intelius, PeopleFinder, USPhoneBook, Nuwber, MyLife, PeekYou, ZabaSearch, ThatsThem, plus several others) and re-submits every 90 days because that's the median window in which brokers re-add removed records. There's also HaveIBeenPwned breach scanning that surfaces which of your accounts have been exposed and cross-references the breach data against what brokers list publicly for you.

The privacy tools are the wedge. The marketplace is the long-term thesis.

Why a marketplace at all

The entire reason data brokers can profit from your data is that the economic loop is broken: someone creates a record about you, sells it to whoever pays, and you receive nothing. The information you generate by living your life — moving, registering for things, having a phone — gets monetized at every layer of the stack except yours.

Privacy tools that only do opt-outs are playing defense against an industry whose entire business is to keep adding you back. The treadmill metaphor isn't a metaphor. It's literally the design of the broker industry. They have an incentive to keep adding you. You have to keep paying (or paying a service like DeleteMe) to keep removing yourself.

The only way to win that game is to change the economic incentive. Specifically: make it more profitable for businesses to get data directly from consenting consumers (with payment attached) than to buy non-consented data from brokers (with regulatory exposure attached).

That's what the marketplace is. A consent layer for the data economy where the value flow finally includes you.

Why Cardano specifically

A lot of people will ask why we picked Cardano over Ethereum, Solana, or Bitcoin L2s. The honest answer is: this use case fits Cardano better than the alternatives.

Three specific reasons.

Deterministic transaction fees. Escrow needs predictable cost. We can quote a business "this consent transaction will cost 0.17 ADA" with confidence. On Ethereum, the same transaction could cost $2 or $80 depending on the day. That's a structural problem for a marketplace that needs to handle thousands of small consent transactions.

eUTXO model. Each consent record is its own UTxO. The validation logic runs per-spend, not in shared global state. This maps cleanly to per-consent records: the escrow contract is checking properties of one consent at a time, not synchronizing global state across many users. The model fits.

No gas wars. Cardano blocks have predictable space and there's no priority-fee bidding. Our transactions don't get front-run or delayed by some mev bot.

The trade-off is a smaller developer ecosystem. We mitigated by writing the contracts in Aiken (the Plutus alternative that compiles fast, produces small scripts, and has actually-readable error messages). The whole contract suite — escrow + consent registry — is about 300 lines of Aiken.

If you want the deep technical architecture, the whitepaper at sirveyor.app/whitepaper has the full system design including the SRV token mint policy, escrow validator logic, and the on-chain attestation flow.

The on-chain attestation ledger

The piece I'm most personally proud of is the public ledger at sirveyor.app/ledger.

Every time we run an oracle validation against a consumer's submitted data, we compute a SHA-256 hash of the validation details (validation_id, validator pubkey hash, category, confidence score, timestamp) and submit it as transaction metadata to Cardano mainnet via Blockfrost. The transaction ID is stored in our database and surfaced on the public ledger page with a direct Cardanoscan link.

This means: anyone — investor, business partner, journalist, regulator — can verify our validation history without needing platform access. They can see the count, the rate, the categories, and the hash chain integrity. We don't have to be trusted; the chain is the auditor.

This is the credibility layer for the marketplace. Businesses don't have to take our word that the data they're paying for is validated. They can see the receipts.

What's actually working today

• Cardano wallet integration via Lucid Evolution + CIP-30 (works with Nami, Eternl, Lace; Yoroi support is in progress)
• SRV token minted on mainnet, 100M fixed supply
• Aiken-compiled Plutus V3 escrow contract handling consent approval/denial/reclaim
• Aiken-compiled Plutus V3 consent registry with consumer-only revocation
• Privacy Shield: opt-outs to 15 brokers + HIBP breach scanning, all in a 90-second user flow
• Public on-chain attestation ledger at /ledger
• Merch store accepting ADA directly at checkout (no wrapping, no bridges; first Cardano-native ecommerce we're aware of)
• Email + wallet signature auth, JWT-backed sessions
• Public API documentation for businesses

What's not done yet

Building in public means saying what's broken too.

• Consumer beta is invite-only and rolling out from the waitlist. We're at {WAITLIST_TOTAL} of 1,000 invites and aim to hit the cap in the next 30 days.
• Manual oracle validation is the current bottleneck. We have an internal SOP for scoring submitted evidence on a 0.00-1.00 confidence scale across Demographics, Income, Location, Purchase Behavior, and Health. This won't scale beyond a few thousand active users. Chainlink integration is on the roadmap for select categories where there's a clean off-chain truth source.
• The consent registry has a known integrity hole — without a paired minting policy, anyone can publish a fake consent record at the script address. We mitigate by requiring verifiers to cross-reference each record's escrow_tx_hash against the corresponding escrow Approve transaction. Closing the gap with a minting policy is on the v2 list.
• DEX liquidity for SRV is not live yet. Targeting SundaeSwap and Minswap pools in Q3.
• Mobile experience is functional but not polished. Desktop-first.
• US-first. International users can use the privacy tools but the marketplace launches US-only because of the regulatory landscape.

What's next (next 90 days)

• Hit 1,000 waitlist invites and run the airdrop
• Onboard the first 25 businesses for early-access data requests (working with privacy-conscious B2B brands first)
• DEX liquidity announcement and pool seeding
• Chainlink integration scoping for Q4
• Mobile redesign
• Public quarterly numbers post (revenue, on-chain stats, user growth) — first one targeted for August

How to actually try this

Three doors.

You're a privacy-aware consumer. Join the waitlist at sirveyor.app. First 1,000 signups get free SRV at launch (this is a thank-you, not an investment vehicle). When invited, you'll be able to run Privacy Shield (opt-outs + breach scanning) immediately, and when the marketplace beta opens, you'll be in.

You're a business that buys consumer data. Email business@sirveyor.app or join the early-access list at sirveyor.app/business. We'll set you up with API access, walk through the request flow, and explain how consent-verified data reduces your regulatory exposure compared to broker-sourced data.

You're a Cardano dev or interested in the contracts. Whitepaper at sirveyor.app/whitepaper has the architecture. The on-chain ledger at sirveyor.app/ledger has the live attestations. If you want to dig in deeper, my email is in the whitepaper.

A note on what this isn't

SRV is not an investment. It's the unit of consent in a marketplace. Whether it has dollar value depends on whether the marketplace works. We think it will, but we're not promising returns and you shouldn't buy SRV expecting them.

We're not going to be the world's first anything. Several teams have tried versions of this. Most have failed. We think the difference is that we built privacy tools that work even without the marketplace, which gives us a path to user growth that doesn't require the entire crypto thesis to land first.

We're not pitching this as a way to "get rich from your data." Realistic earnings for an active user are likely small dollars per month, not life-changing income. The point isn't that you'll get rich. The point is that the value of your data shouldn't go entirely to companies that never asked your permission.

Closing

Today we shipped the first version of an idea that's been kicking around for a long time but never had the right combination of regulatory pressure, blockchain maturity, and consumer awareness to actually work.

If "consent layer for the data economy" is something you've ever wished existed, the door is open.

→ sirveyor.app

— Jake (founder)