§ 00 — Documentation

The PeptiDAO docs.

The technical reference for the protocol. Litepaper, primitives, on-chain account namespace, and SDK guidance — in one place.

Versionv1.0
UpdatedApr 2026
ChainSolana
StatusPublic
§ 01Litepaper

The Peptide Protocol — v1.0

PeptiDAO is a vendor-direct, on-chain marketplace for peptides built on Solana. The protocol replaces the trust assumptions of the legacy peptide market — opaque vendors, reversible payments, fake reviews — with three composable primitives that make commerce trustless: a staked vendor registry, escrowed settlement, and on-chain reputation tied to verified purchases.

$PDAO is the protocol’s utility token. It is required for vendor staking, dispute arbitration, and DAO governance. It confers no equity, dividend, or revenue rights. The token launches on pump.fun. Founder keys are scheduled to be burned by Q1 2027.

This document is the canonical technical reference. It supersedes all earlier drafts, threads, and announcements. Section numbers align with the on-chain account namespace where applicable.

§ 02Primitives

Three primitives, one closed loop

Vendor Registry

Each vendor is a registered on-chain identity. Listing requires a $PDAO stake locked for tenure. Misconduct is slashable by DAO vote. Honest operation accrues reputation that is portable across the protocol.

Escrowed Settlement

Buyers fund a program-derived address (PDA) in SOL or USDC. Funds release on confirmed delivery. Disputes route to structured on-chain arbitration. There are no chargebacks and no reversals — the chain is the source of truth.

On-chain Reputation

Every transaction emits a Reputation Event. Reviews are tied to verified purchases — wallets that did not pay cannot post. A vendor’s score is derived from emitted events, not declared in metadata.

§ 03Order lifecycle

From quote to release in seconds

  1. Quote. Buyer requests a price from a vendor listing. The vendor program returns a signed quote with TTL.
  2. Fund. Buyer signs a transaction that transfers quote amount into a per-order escrow PDA.
  3. Fulfill. Vendor marks the order shipped on-chain with tracking metadata (encrypted to buyer).
  4. Confirm. Buyer confirms delivery. Funds release atomically. A Reputation Event is emitted.
  5. Dispute. Either party may open a dispute window. Arbitration is settled by stake-weighted DAO vote.
§ 04On-chain accounts

Account namespace reference

The protocol exposes four primary account types. All are PDAs owned by the PeptiDAO program; none are user-writable.

  • VendorAccount — registered vendor identity, stake, and reputation aggregate.
  • ListingAccount — published product offer; references a VendorAccount.
  • OrderEscrow — per-order escrow PDA; holds funds until release or refund.
  • ReputationEvent — append-only event emitted at order close; the basis for derived scoring.
§ 05SDK

Building on PeptiDAO

The TypeScript SDK ships in Phase 3 (Q4 2026) alongside x402 integration for agentic commerce. It will expose typed clients for quoting, ordering, and reading reputation, plus React hooks for wallet-side flows.

import { PeptiDAO } from "@peptidao/sdk";

const client = new PeptiDAO({ cluster: "mainnet-beta" });
const quote = await client.quote({ listing, qty: 1 });
const order = await client.order(quote).fund(wallet);
await order.awaitRelease();

Until the SDK is published, integrators can build directly against the program IDL. Reach out on Telegram for early access.

§ 06Token

$PDAO mechanics

$PDAO is the protocol’s utility and governance token. Its functions are scoped to protocol operation:

  • Vendor stake. Listing requires locked $PDAO collateral, slashable on misconduct.
  • Arbitration. Stake-weighted voting on disputes.
  • Governance. Treasury operations, vendor approvals, and parameter changes once founder keys are burned.

$PDAO is not a security. It carries no claim on revenue, equity, or assets. PeptiDAO is neutral commerce infrastructure; vendors are independent operators.

§ 07Security

Audits and disclosures

The escrow program is scheduled for third-party audit before Marketplace v1 goes live. The audit report and remediation log will be published here at that time.

Responsible disclosure: report any suspected vulnerability to the team via Telegram with a private channel request, or by signed message from a known contributor wallet. A formal bug bounty opens alongside the audit publication.