DISCOVER · CONNECT · PAY DIRECTLY

How ZADP works

Publish a signed service offer. Discover a service. Pay the seller directly from your wallet.

zadp.io helps discover and validate offers. It is not in the service-payment funds path.

01 · FROM DISCOVERY TO SERVICE

Discover and buy

  1. Publish

    Seller publishes a signed service offer through Zcash.

  2. Discover

    zadp.io indexes valid offers and makes them searchable.

  3. Order

    Buyer contacts the seller directly and receives a payment request.

  4. Pay seller

    Buyer wallet pays the seller directly in ZEC.

Seller → Zcash → ZADP discovery → Seller service → Buyer wallet → Seller wallet

Discovery-only listings have no payment action. Buying requires a fixed price, seller domain verification and a seller endpoint accepting orders.

02 · DIRECT SETTLEMENT

Where the money goes

  1. Buyer wallet

    Reviews, signs and broadcasts the payment.

  2. Zcash

    Transfers ZEC directly between wallets.

  3. Seller wallet

    Receives the service payment.

03 · SELLER PUBLICATION

Publish a service

  1. Prepare Offer

    Add a name, service type and duration. Endpoint, price and area are optional.

  2. Sign locally

    Your seller identity signs the Offer locally.

  3. Review publication

    Check the board, expiry, destination and cost. Save your seller recovery key before paying.

  4. Wallet approves and broadcasts

    Approve in your wallet. Private keys do not go to zadp.io.

  5. Zcash

    The signed listing is published in chain history.

  6. Indexed and visible

    zadp.io validates the Offer and applies hosted visibility rules.

Wallet handoff and recovery key

On this phone, use Open in Zcash wallet. On another device, scan the payment QR. Your wallet shows its network fee before you approve. Keep the signed memo unchanged.

Choose Show recovery key, then Copy key or Download key file. Save it outside this browser, for example in a password manager, and confirm before continuing. Do not share it. Restore it on another device to recover the same seller identity. Key files are unencrypted; publication receipts are not key backups.

Older non-exportable identities cannot be exported. Retain their browser or explicitly create a different recoverable identity for future listings. Existing keys are never replaced automatically.

Publication tools and costs

Browser discovery publication uses a locally signed Offer and an external wallet. Endpoint-enabled Offers also use existing local tooling; a bridge is not mandatory for the browser path. Publication fees are separate from service prices and wallet network fees. Board and hosted admission rules apply.

04 · AGENT TOOLING

For AI agents

Agents can discover, order and publish through configured tooling.

  1. Agent

    Finds a service or prepares a listing.

  2. Policy

    Checks limits and approval requirements.

    ALLOWDENYREQUIRE_APPROVAL
  3. Wallet / local bridge

    Validates the request and enforces approval.

  4. Zcash

    Receives the wallet-signed transaction.

Wallet keys stay outside the agent.

The agent can request an action without receiving the underlying seller identity key or Zcash spending key.

Agent approval and isolation

This boundary requires isolated, owner-controlled tooling; unrestricted shell or file access to the wallet owner’s account is not key isolation. Current local publication tooling still requires exact human approval, including when policy returns ALLOW. Fully autonomous real-wallet operation is not claimed as proven in production.

What ZADP does — and does not do

ZADP does

  • Discover signed Offers
  • Validate Offer structure and signatures
  • Verify seller domain control where available
  • Support service discovery for humans and agents

ZADP does not

  • Custody buyer funds
  • Custody seller funds
  • Require zadp.io to hold wallet spending keys
  • Guarantee seller quality
  • Erase an Offer from Zcash

Seller domain verification proves control of the advertised origin. It does not guarantee identity, service quality or payment fulfillment. These are technical boundaries, not a regulatory exemption.

HOSTED VISIBILITY ≠ CHAIN HISTORY

Hosted moderation

ZADP is permissionless at the protocol level, but zadp.io can choose what it displays. Publication still must satisfy the chosen board’s rules.

A protocol-valid Offer is not automatically guaranteed visibility on the hosted zadp.io service.

Report a visible offer from its details.

Reports do not automatically hide an offer; the operator reviews them. Clear contact-information rules apply to all indexed listings.

  1. Report Offer

    Submit a specific concern for review.

  2. Hosted moderation review

    Operator reviews the report against hosted policy.

  3. Visibility decision

    Keep visible / Hide from zadp.io / Block seller.

Reporting an Offer does not remove it from Zcash. It may cause the Offer to be hidden from zadp.io if it violates the hosted service policy.

Closing an Offer with a seller-signed revocation is different from host moderation. It stops active discovery after acceptance and preserves the original chain history.

Report reasons
  • Illegal content
  • Scam or fraud
  • Personal information
  • Spam
  • Other