SirVeyor

Consumers receive nothing in exchange for their data. Worse, they rarely know their data is being traded. When they do find out and attempt to opt out, the process is fragmented — each of the hundreds of data brokers has a different opt-out procedure, most designed to be difficult to complete.

Businesses purchasing third-party data face quality and consent problems. Data collected without explicit consent carries regulatory risk under GDPR, CCPA, and emerging state privacy laws. Poor data quality leads to wasted ad spend and damaged consumer trust.

Centralized data stores are prime attack targets. In 2023 alone, over 3.5 billion records were exposed in data breaches. Consumers have no visibility into which breaches have affected them or what data is now circulating on the dark web.

SirVeyor deploys two Plutus V3 smart contracts compiled with Aiken on the Cardano mainnet:

Escrow Contract — Locks SRV tokens when a business creates a data request. The contract validates the consumer's verification key hash and releases tokens to the consumer on approval (Approve redeemer) or returns them to the business on denial (Deny redeemer). A deadline mechanism allows businesses to reclaim tokens from expired requests.

Consent Registry — Creates an immutable on-chain record when a consumer approves a data request, referencing the escrow transaction hash, categories consented to, and a POSIX timestamp. This provides cryptographic proof of consent for regulatory compliance.

A Node.js/Express API hosted on Railway handles: authentication (JWT + bcrypt), consumer profile encryption (AES-256-GCM client-side with PBKDF2 key derivation — the server never sees plaintext data), decentralised profile replication to IPFS via Pinata, request matching, trust score computation, data delivery with anonymization, rolling in-memory API metrics, and on-chain attestation submission.

When an admin approves an oracle validation, the backend constructs and submits a Cardano transaction from the platform hot wallet carrying two metadata labels. Label 674 (CIP-20) provides a human-readable message. Label 7391 carries the SirVeyor attestation record: schema version, data category, confidence score (×100 as an integer), a SHA-256 privacy-preserving hash linking the record to the database row without exposing identity, a monotonically increasing sequence number, and a Unix timestamp. The resulting transaction hash is stored in the database and displayed on the public Ledger page. No personally identifiable information is ever included in on-chain metadata.

A Next.js 14 application hosted on Vercel uses Lucid Evolution for browser-side Cardano transaction building. The user's mnemonic is generated in the browser, encrypted client-side, and only the ciphertext is stored on the server. Cardano transactions are signed entirely in the browser — the server never has access to private keys.

Consumer profile data is encrypted using AES-256-GCM with a key derived via PBKDF2 from the user's password. The encryption happens in the browser before any data is transmitted. The server stores only the ciphertext, salt, and IV. Even a full database compromise exposes only encrypted data.

Encrypted consumer profile blobs are replicated to IPFS (InterPlanetary File System) via Pinata, creating a content-addressed, decentralised backup layer alongside the primary PostgreSQL database. Each profile update pins the new encrypted blob and unpins the previous version to manage storage efficiently.

IPFS provides three key properties for SirVeyor: durability — profiles survive database failures or migrations because the encrypted blob exists on the IPFS network independently; verifiability — the CID (Content Identifier) is a cryptographic hash of the data, meaning any retrieval can be verified against the expected content; and decentralisation — no single point of failure controls the storage layer.

The system degrades gracefully: if IPFS is unavailable, the platform operates on PostgreSQL alone with no user-facing impact. Profile retrieval checks Postgres first and falls back to IPFS only when the local copy is missing. Because the data stored on IPFS is AES-256-GCM ciphertext, even direct access to the IPFS blob reveals nothing without the user's encryption key.

As the consumer base grows, SirVeyor plans to integrate Filecoin — the incentivised storage network built on top of IPFS — to provide cryptographically verifiable, long-term persistence guarantees. Filecoin extends IPFS with storage deals: miners are economically incentivized to store data for agreed-upon durations, and the network continuously proves (via Proof-of-Replication and Proof-of-Spacetime) that the data remains intact. This eliminates the reliance on a single pinning provider and gives SirVeyor enterprise-grade durability backed by a global network of storage providers — all while maintaining the same content-addressed, encrypted-at-rest architecture already in place.

Businesses purchase SRV on decentralized exchanges using ADA, then lock tokens directly into the Plutus escrow contract when creating a data request. That locked amount is the consumer's compensation — it is never held by SirVeyor. Tokens are released to the consumer only when they explicitly approve, or returned to the business on denial or expiry. SirVeyor earns revenue through a protocol fee charged on top of each escrow lock, which flows back to the platform treasury. This creates a self-sustaining flywheel: request volume drives fee income, fee income funds liquidity and operations, and deeper liquidity makes SRV easier for businesses to acquire.

A tiered protocol fee is charged on top of the consumer payout and flows to the SirVeyor treasury. Fees are determined by the highest data sensitivity level in the request: 5% for low-sensitivity categories (browsing history, interests, social media), 10% for medium-sensitivity (location, purchase history, demographics), and 15% for high-sensitivity (health, financial). The protocol fee is additive — businesses pay it on top of the consumer payout and consumers always receive the full amount they were promised.

Total supply is fixed at 100,000,000 SRV. The distribution is designed to prioritize consumer rewards — the mechanism at the core of SirVeyor's value proposition — while providing sufficient runway for ecosystem growth, platform operations, and long-term sustainability.

Consumers submit data category validation requests through the platform. Trained SirVeyor administrators review supporting evidence against documented standards (defined in the Oracle Validation SOP, document SRV-SOP-001) and assign a confidence score between 0.00 and 1.00. Categories include Demographics, Income, Location, Purchase Behavior, and Health. Every decision is logged with a full audit trail.

Every approval immediately triggers a Cardano transaction from the SirVeyor platform hot wallet. The transaction carries CIP-20 metadata (label 674) and a custom SirVeyor attestation payload (label 7391) containing the data category, confidence score, sequence number, timestamp, and a SHA-256 hash that cryptographically links the chain record to the database row without exposing any consumer identity. These records are permanently on the Cardano blockchain and can be queried by anyone using Blockfrost or any Cardano explorer.

SirVeyor's current oracle validation pipeline relies on trained platform administrators. As the marketplace scales, manual review becomes a bottleneck. The planned integration with Chainlink — the industry-standard decentralised oracle network — will introduce automated, trustless data validation for select categories.

Chainlink's decentralised oracle nodes can independently verify consumer-reported data points (e.g. confirming location via geolocation APIs, validating purchase history against merchant networks, cross-referencing demographic claims against public records) and submit confidence scores directly on-chain without human intervention. This enables SirVeyor to scale validation throughput by orders of magnitude while maintaining — and in many cases exceeding — the credibility of human review, since Chainlink attestations carry the cryptographic guarantees of a decentralised node network rather than a single platform operator.

The transition will be incremental: categories with reliable external data sources (location, demographics) will migrate to Chainlink automation first, while subjective or sensitive categories (health, financial) retain human review with Chainlink as a supplementary verification layer.

The /ledger page provides a public view of all on-chain attestations — total count, category breakdown, average confidence, and a live table with direct links to each transaction on Cardanoscan. Any investor, business partner, or regulator can independently verify SirVeyor's attestation history without needing access to the platform. This is the foundation of SirVeyor's credibility proposition.

Platform administrators have access to a real-time performance dashboard showing user and consumer growth, data request volume and conversion, rolling API health metrics (request count, response times, error rates), SirVe token statistics from Blockfrost, and live ADA market price from CoinGecko. The dashboard is instrumented via a 1-hour rolling in-memory metrics middleware with per-minute bucketing.

SirVeyor integrates with the HaveIBeenPwned API — the world's largest database of known data breaches, covering 14+ billion compromised records. Users can scan their email address to determine if they've been exposed in any known breach, with detailed information about which data types were compromised and when.

SirVeyor maintains a database of major data brokers and their opt-out mechanisms. With a single click, users can submit opt-out requests to all brokers simultaneously. SirVeyor tracks the status of each request and automatically resubmits opt-outs every 90 days, as data brokers frequently re-add records.

Current broker coverage includes: Spokeo, WhitePages, Intelius, BeenVerified, Radaris, PeopleFinder, MyLife, Acxiom, LexisNexis, Equifax, Epsilon, Oracle Data Cloud, Experian, CoreLogic, and ZoomInfo.

Data broker opt-out rights are established under CCPA (California Consumer Privacy Act), GDPR (General Data Protection Regulation), Virginia CDPA, Colorado CPA, and similar state and national privacy laws. Data brokers are legally required to honor opt-out requests within 30–45 days.

The service worker caches essential app routes and assets, enabling core functionality even with intermittent connectivity. The web app manifest enables installation on iOS (via Safari Add to Home Screen) and Android (via Chrome Install Prompt).

SirVeyor is planned for distribution on the Google Play Store via Trusted Web Activity (TWA) and on the Apple App Store via WKWebView wrapper. Both approaches allow the existing PWA codebase to be distributed through official channels without maintaining separate native codebases. Target release: Q3 2026.

Each business on SirVeyor earns a trust score based on their consumer approval rate (approved requests / total resolved requests). This score determines which data sensitivity tiers they can access:

Consumer data categories that have passed oracle validation carry an on-chain attestation and a confidence score. Businesses querying the data marketplace can filter by validated categories and minimum confidence thresholds, ensuring they only pay for data that meets their accuracy requirements. This directly drives demand for validated data and creates a stronger economic incentive for consumers to maintain accurate profiles.

SirVeyor maintains an admin panel for business verification, oracle validation management, and platform monitoring. Verified businesses receive a trust badge visible to consumers. Admin users follow a formal Standard Operating Procedure (SRV-SOP-001) for all oracle validation decisions.