Verity Protocol, end to end.

Verity Protocol is a public, permissionless registry for real-world assets. Anyone with a wallet can register any real-world thing they own or manage — a plot of land, a rental unit, a herd of livestock, a combine harvester, a copyright, a signed guitar — and get a public, wallet-signed claim record. Optionally, launch a tradable token backed by the asset on the Portal.

Every listing is a signed statement. Verity does not verify or underwrite anything. The value comes from what other wallets do with your listing — endorsements, verifier attestations, disputes, transfers — and from the composable, public nature of the registry itself.

Think of it as WHOIS for real-world assets. Or as GitHub for signed provenance claims. Or as the base layer that other RWA services — insurers, lenders, marketplaces — will eventually read from.

• Durable evidence. A wallet-signed, timestamped, publicly readable record that survives you. Useful in inheritance disputes, resale negotiations, or any conversation where “prior claim” matters.
• Portable reputation. Your wallet accumulates a public track record of registrations, endorsements received, disputes, and holdings. That reputation is portable — anyone building on Verity data can read it.
• Composability. Other applications — insurers, lenders, RWA protocols, marketplaces — can build on the registry. Your listing is already there when they arrive.
• Discovery. Registered assets are searchable by anyone. Farcaster Frames push individual listings into social feeds where buyers and endorsers might find them.

1. Visit /register and connect a wallet. Use the network toggle in the header to pick Base or Robinhood Chain — mainnet or testnet.
2. Pick an asset type: land, real estate, crop, livestock, equipment, commodity, collectible, IP, or other.
3. Fill in name, optional location, description, and optionally attach a documentation URL (deed, invoice, title, photo, valuation report). Everything is public and permanent — don't include anything private.
4. Read and accept the attestation checkbox. This tells Verity your wallet is claiming ownership or management of the asset described.
5. Click Sign & register. The AI does a pre-flight plausibility check on the draft. If it finds obvious issues (placeholder text, empty fields, contradictions), it warns you before you sign.
6. Sign the canonical Verity registration message in your wallet. This is free — just a signature, no gas.
7. Your listing appears on /registry immediately, and its dashboard becomes available at /dashboard/<asset-id>. From the dashboard, you can post updates, invite endorsements, or launch a tradable token on the Portal.

Registry entries are free and signature-only. When you're ready to open a market for an asset, launch a token on the Portal from your dashboard. One signature deploys an ERC-20 backed by the registered asset and seeds a constant-product trading pool paired against the network's native ETH — Base or Robinhood Chain, your pick at launch time.

No bonding curve. The pool is live and tradable the moment your launch transaction confirms. Buyers use the trading page to swap ETH for the asset token; sellers do the reverse. Reserves, price, and trade history update in real time.

AI-moderated. Before your launch broadcasts, an AI reviewer runs a pre-flight check on the asset, your allocation, and the initial liquidity you're contributing. A flagged listing can still launch with an override — the flag is displayed publicly on the trading page. Post-launch, the same model periodically reviews on-chain behavior for anomalies.

Explore active launches at /portal.

Any wallet other than the registrant can publicly endorse a listing. Endorsements are signed on-registry vouches — they don't transfer tokens, don't bind Verity, and can't be revoked once signed.

Endorsements are the primary trust signal on Verity. They accumulate on the asset, not on the holder, so trust built into a listing survives ownership changes. An endorsement can include a short note explaining why the endorser vouches for the claim (“neighbor of the property since 1998”, “verified the herd count on-site”, etc.).

Endorsements from badged verifiers weigh double in reputation and unlock higher evidence tiers.

Wallets can self-declare as professional verifiers — appraisers, surveyors, notaries, inspectors, auditors, lawyers. A verifier profile requires a public proof URL (a state license lookup, a bar profile, a firm bio) that buyers can evaluate independently.

Verity does not vet verifier claims. The declaration is permissionless. But endorsements from a badged verifier carry a visible badge on every listing they touch, weigh double in reputation calculations, and can push a listing from tier L2 to L3.

See the public directory at /verifiers.

Every listing carries an evidence tier — a compact signal of how much on-registry evidence has accumulated. Tiers are monotonic (an asset only advances when every lower-tier condition is met):

• L0Self-attested

  Wallet signed a registration. Nothing else.

• L1Documented

  Registrant attached a public documentation URL — deed, invoice, photo, valuation, license.

• L2Endorsed

  Three or more independent wallets have endorsed the listing.

• L3Verifier-endorsed

  At least one badged professional verifier has endorsed the listing.

• L4Anchored

  Everything above, plus the asset has been tokenized on the Portal or (for transferred assets) the current transfer is anchored on the VerityAnchor contract.

Buyers can filter or sort by tier. A listing at L4 with zero disputes is a much stronger signal than a listing at L0.

Any wallet other than the registrant can dispute a listing. A dispute is a signed message explaining why the listing appears inaccurate, fraudulent, duplicated, or otherwise contested. Verity does not adjudicate — disputes are recorded, made public, and weigh significantly against the registrant's reputation.

Listings with any dispute display a “Contested · N” badge. Disputes require a minimum of 8 characters of explanation to discourage drive-by flags.

A dispute does not remove a listing. The signed record remains public, and the registrant can respond via status updates.

Every wallet has a public reputation score, computed on load from the wallet's registry activity:

• Assets registered (bounded, +4 per, cap 25).
• Plain endorsements received (+6 per).
• Verifier endorsements received (+12 per).
• Endorsements given (+2 per, cap 50).
• Disputes filed (+1 per, cap 20).
• Log-decayed bonus for wallet age.
• +20 base for wallets with a verifier profile.
• −12 per dispute received (unbounded penalty).

Scores map to tiers: Newcomer, Established, Trusted, Reputable, Contested. Hover the badge on any wallet profile for a full breakdown of what contributed.

A permissionless registry has a real risk: two people registering the same asset. Verity checks every listing against every other listing of the same type and flags collisions:

• Identical normalized location strings (case-folded, punctuation stripped).
• Identical normalized names within the same asset type.

Conflicts appear as a prominent panel on each listing's dashboard, with the competing listing linked and its registrant shown. Verity doesn't judge who's right — but the flag makes it impossible for a bad actor to quietly duplicate a listing.

Every registration triggers two AI checks:

• Pre-flight review — runs on the draft before the wallet signature. If the listing has placeholder text, is empty, or contains obvious spam, the registrant is warned. Red verdicts require an explicit override checkbox to proceed.
• Post-registration review — runs automatically after the listing lands. The verdict, summary, and specific flags are attached to the listing's dashboard and displayed as an “AI · Sus” or “AI · Flagged” badge on the registry cards.

The AI does not verify anything. It checks for internal consistency: does the name match the type, are the numbers plausible, is the description substantive. Green, yellow, and red verdicts.

Real-world ownership changes. The registry entry can move between wallets via a two-party signed handoff, and the current-holder pointer updates without any on-chain token movement:

1. Current holder signs a “Verity — transfer claim” message naming the destination wallet.
2. Destination wallet signs a “Verity — accept transfer” message.
3. Server verifies both signatures. The listing's current_holder_wallet updates.
4. A status update is appended to the update log.
5. Optionally, either party can anchor the transfer on-chain — see next section.

The transfer can be cancelled by the outgoing wallet or rejected by the incoming wallet at any time before acceptance. Only one pending transfer per asset is allowed (enforced by a Postgres unique index).

The VerityAnchor contract (deployed to whichever chain the registrant selects — Base or Robinhood) records the hash of accepted transfers so anyone can independently verify the handoff happened, without needing to trust Verity's database.

The hash format:

transferHash = keccak256(concat(outgoingSignature, incomingSignature))

Anyone with both signatures can reproduce the hash and call transferHashes(assetId) on the contract via the chain's block explorer. The contract has no owner, no admin, no fees, and no upgrade path.

Every listing whose current holder differs from the original registrant shows a Provenance Chain block on its dashboard: original registrant → prior holder 1 → prior holder 2 → current holder, with dates and any signed notes at each handoff. Each segment shows whether it's been anchored, with a click-through to the transaction on the network's block explorer.

Buyers reading a listing can walk the entire ownership history in one glance.

Every asset dashboard URL renders as an interactive Farcaster Frame when cast in Warpcast. Two buttons:

• View listing — opens the dashboard.
• Endorse — a Farcaster user with a verified Ethereum address can endorse the listing without leaving their feed. The Frame POST is validated via Neynar; the endorsement is recorded against the user's verified wallet with a note attributing the Farcaster identity.

Wallet profiles also render as Farcaster Frames — cast a /wallet/<address> URL and Warpcast shows the reputation score, holdings, and asset counts.

The agent at /agent is a tool-calling LLM with read-only access to the entire registry. Ask it anything in plain English:

• “How many crop assets are registered?”
• “What has 0xabc…def registered? Who has endorsed those listings?”
• “Give me a full profile of asset 8c0…f3d — what looks credible or anomalous?”

Every factual answer includes the underlying tool call so you can audit exactly what data was fetched. From any asset dashboard, the “Ask agent” button deep-links a pre-seeded question about that specific listing.

The public /activity page is a live stream of every signed event on the registry — registrations, endorsements, disputes, status updates, transfers, anchor recordings — newest first, color-coded by kind. Nothing is fabricated; every row was signed by someone's wallet.

Every wallet address has a public profile page at /wallet/<address>. It shows:

• Reputation score and tier badge
• Verifier badge if declared
• ENS name if resolvable
• Registered assets
• Held assets (received via transfer, not originated)
• Recent endorsements given
• First-seen date

Wallet profiles are the portable-reputation surface — any future service reading Verity data will use these as identity anchors.