POLICY & PRIVATE-ALPHA TERMS

Discovery. Direct service.

Experimental protocol suite

Operator and contact

Operator-designated name: ZADP. Service inquiries: zadp@zadp.io. Security reports: security@zadp.io.

What zadp.io provides

zadp.io provides a discovery interface and a hosted read-only index of signed service listings. It checks seller domain ownership where supported. It is not an exchange for buying or selling crypto-assets, a wallet custodian, escrow or investment adviser. A service directory can still be described as a marketplace in ordinary language; blockchain storage alone does not determine its legal classification.

Seller and buyer responsibilities

The seller describes and supplies the service and sets its service terms and price. A buyer must review the service, network, recipient, amount, memo, invoice expiry and wallet fee. Service purchase agreements are between buyer and seller; discovery does not guarantee performance, delivery or refunds. A reference seller may share an operator with discovery; separate service origins do not imply separate legal entities.

Only publish lawful services and accurate descriptions you are entitled to provide. Do not publish secrets, private home locations without informed intent, unlawful content, scams or services that abuse other people. Do not attack, overload, scrape abusively or bypass authentication. Automated clients must respect API limits and human payment approvals.

Payments and local publication

Seller endpoints create orders and payment requests. Buyer-controlled wallets validate, approve, sign and broadcast. Service funds go directly from buyer wallet to the seller-designated wallet. zadp.io discovery does not receive buyer service funds, hold spending keys, sign or broadcast buyer payments, forward settlement or charge a buyer service-payment fee.

The local publication bridge is seller-controlled software running on the seller's computer. Seller identity and wallet authority stay local. It validates an exact publication proposal under local policy and preserves explicit human approval for mainnet execution. No hosted wallet route is provided.

Publication pricing uses a configurable USD reference from $0.30 for one day to $1.00 for 90 days, with a default of 30 days. Payment would be in ZEC at a fresh quoted rate, plus the exact wallet-generated network fee. Seller service price is separate. Discovery publication can be paid from your own wallet. The host can accept new seller identities or restrict publication to approved identities under its configured admission policy. No fee is owed merely for viewing an estimate or saving a draft. Review the exact quoted ZEC amount and your wallet fee before authorizing payment. Payment does not guarantee hosted visibility.

Domain proof and availability

Seller domain verified means the signed seller identity is bound to the HTTPS origin. It is not KYC, endorsement, solvency, quality or a guarantee that orders are available. A signed Offer is not a signed invoice. Existing service payment requests still rely on the seller HTTPS connection and validated response; independent seller-signed invoice verification is not yet implemented.

Publication, moderation and blockchain history

Published Offer metadata should be treated as accessible to board readers. Zcash memo encryption does not make a listing private once its board viewing scope is shared or indexed. Demo inventory is synthetic and is not published on Zcash. Never buy demo listings marked as unavailable.

The host can omit, quarantine or hide listings under its policy. Offer expiry and accepted seller-signed revocation remove active discovery availability; neither erases blockchain history. Replicas may retain published metadata. Reorgs and indexing delays can temporarily change availability. Removing a hosted listing does not cancel existing seller orders or refund payments.

Privacy and recovery

Nearby coordinates stay in browser memory and are not sent to discovery. Discovery receives normal connection information and API requests; do not place private input in API search queries. Order input and results are sent to and stored by the seller. The reference seller currently stores these in private plaintext SQLite; automated deletion is not yet implemented. A browser recovery token can retrieve an order result: protect access to your browser and device.

Availability, risks and mandatory rights

This alpha may contain defects, pauses or interruptions. Zcash payments can be irreversible, wallet fees are separate and software cannot promise a refund. Verify requests before authorizing funds. No guarantee of uninterrupted access, indexing speed or seller fulfilment is made. Nothing here excludes liability or consumer rights that cannot lawfully be excluded. Seller-specific complaints go to the seller; platform and security concerns can be reported to ZADP.

Regulatory boundary: MiCA

MiCA is an EU regulation, not a directive. Its crypto-asset service categories include custody, transfer services and operating a crypto-asset trading platform. The intended technical boundary here is service discovery plus seller-domain verification, with buyer-controlled direct payment and no discovery custody. Listings describe services, not a crypto-asset exchange order book.

These facts matter, but no-custody and blockchain storage do not alone establish that MiCA, consumer law or platform duties are inapplicable. zadp.io is an operated, moderated hosted service and must not claim the fully decentralised, no-intermediary exemption merely because the underlying Offer data is on-chain.

Sources: MiCA Regulation (EU) 2023/1114, ESMA decentralisation scope. Applicability is not decided by this page.