Admission to the EDMA Launchpad is a structured six-stage process, not a one-click deployment. The team verifies identity to the Attestor Registry, declares the underlying asset, posts the operating-evidence dossier on-chain, secures attestor co-signing, and receives a tier assignment that determines retail access. The application is the dossier; the dossier hash anchors at the moment the presale opens.
6 stagesFrom identity verification to open presale
3 tiersRetail open, qualified, private, set by evidence depth
On-chainDossier anchored before any presale capital moves
Admission is structured, not transactional
Token deployment in the rest of the industry is a one-click action. The barrier between an idea and an open token sale collecting retail capital is measured in minutes and a small gas fee. The EDMA Launchpad inverts this default. Admission is a six-stage process where each stage produces an on-chain artifact that downstream stages depend on. The application is not a form; the application is the operating-evidence dossier that the protocol will validate, attestors will co-sign, and the listing surface will render from.
The structure exists because the data in the death scale and unverified mints shows what happens when the mint moment is treated as a developer convenience. 13.4 million failed tokens since 2021. $17 billion in 2025 crypto scams. The Launchpad treats the mint moment as the protocol's verification chokepoint. Admission is therefore the longest, most evidence-intensive stage; the rest of the listing lifecycle is downstream of what happens here.
SIX STAGES AT A GLANCEFrom identity verification on the Attestor Registry to the moment the dossier hash anchors on-chain and the presale opens. The visual shows the shape; the cards below give the substance.
IDENTITY
S01
Founder identity
Attestor Registry role bindings
ASSET
S02
Asset declared
Drives B3 evidence requirements
EVIDENCE
S03
Dossier prepared
Five-block canonical JSON
ATTESTORS
S04
Co-signatures
2+ attestors, AUDITOR required
TIER
S05
Tier assigned
T1 retail / T2 qualified / T3 private
OPEN
S06
Presale opens
Dossier hash anchors on-chain
Six-stage Launchpad admission flow at a glance. The detailed structural cards immediately below give the substance of each stage; this visual gives the shape.
SIX-STAGE ADMISSION FLOW, INQUIRY TO OPEN PRESALEAdmission is a structured process, not a one-click deployment. Each stage produces an on-chain artifact that downstream stages depend on. Stage 6, the moment the presale opens, is the moment the dossier hash is anchored and capital starts flowing into protocol escrow.
S01IDENTITY
Founders and key roles registered to the Attestor Registryno anonymous launches past this stage
What the team submitsVerifiable identity for each founder and key contributor; role bindings (FOUNDER, OPERATOR, AUDITOR, plus route-specific roles like METER_OP for energy projects or INSPECTOR for RWA); legal entity references where applicable.
What the protocol doesRecords identities under role bindings in the Attestor Registry. Identity remains active for the lifetime of the listing; revocation flows in the Governance framework apply if circumstances change.
S02ASSET
Underlying asset declared with class and referencedrives the evidence requirements at S03
What the team submitsThe asset class the token represents: renewable installation, trade-finance receivable, software product or protocol, treasury position, or other route-specific category. The declaration includes specific identifiers (installation IDs, contract addresses, counterparties) the evidence dossier will substantiate.
What the protocol doesMaps the declared asset class to the route-specific evidence requirements that S03 will need to satisfy. An energy installation triggers METER_OP evidence demands; an RWA pool triggers counterparty and settlement-record demands; a software project triggers repository and audit demands.
S03EVIDENCE
Canonical-JSON evidence dossier preparedfive blocks, hash will anchor at S06
What the team submitsThe full evidence dossier: identity block, asset declaration, operating evidence appropriate to the asset class, vesting and cap-table design with milestone references, audit attestations. See the KPI proof page for the full dossier structure.
What the protocol doesValidates the dossier against the canonical-JSON schema (RFC 8785 inspired). The same facts always produce the same hash. The dossier is held off-chain by the team but its hash will be anchored on-chain at S06; any subsequent change requires re-attestation.
What the team submitsDesignation of which attestors will sign which evidence components. The attestors must be on the Attestor Registry's role-bound allowlist with active credentials. Self-attestation is not permitted; the team cannot sign their own evidence into existence.
What the protocol doesEnforces the standard quorum spec from the PoV gate: minimum 2 total attestations, AUDITOR role required, at least 2 distinct roles total. If the spec fails, S04 does not pass and the team must address the gap before proceeding to S05.
S05TIER
Retail-access tier assigned by evidence depth and asset classretail open, qualified, or private
What the team submitsNothing additional at this stage; tier assignment is computed from S03 evidence depth and S02 asset class. The team can request a higher-tier review if borderline, with the burden of adding evidence to the dossier.
What the protocol doesAssigns one of three tiers (see tier cards below). Higher evidence depth opens broader retail access. Thinner evidence routes to qualified-investor-only or private tiers with stronger protection mechanisms (investor caps, verification requirements, longer mandatory lockups for participants).
S06OPEN
Presale opens with dossier hash anchored on-chaincapital flows into protocol escrow
What the team submitsFinal confirmation. The presale page renders directly from the dossier, not from a separate marketing site; the team cannot publish claims publicly that differ from the on-chain dossier.
What the protocol doesAnchors the dossier hash on the EDMA chain. Opens the presale contract. Capital from participants flows into the project's escrow contract under the One-Claim Ledger. Release is gated by milestones declared at S03 and verified by the same attestor framework; see the Capital release page for the tranche-release mechanism.
Six stages of Launchpad admission. Each stage produces an on-chain artifact that downstream stages depend on. The team cannot skip a stage or perform stages out of order; the protocol enforces sequencing at the contract level.
What each stage requires of the team
Stage 1 and Stage 2 are quick if the team is already operating under a verifiable identity with a clear asset. Identity verification (S01) requires the founders and key contributors to register to the Attestor Registry under role bindings. Asset declaration (S02) requires the team to be specific about what the token represents: a renewable installation with specific IDs, a trade-finance receivable with specific counterparties, a software protocol with specific deployed contracts. The vague memecoin or rebranded narrative cannot route past S02.
Stage 3 (evidence dossier) is the substantive work. The team prepares the five-block canonical-JSON dossier documented at KPI proof. Stage 4 (attestor co-signing) requires the team to designate Attestor Registry parties who will verify the dossier components; the protocol enforces a quorum spec (2 attestors minimum, AUDITOR required, 2 distinct roles minimum) and self-attestation is structurally blocked.
Stage 5 (tier assignment) is computed by the protocol from the dossier depth and asset class declared at earlier stages. The team can request a higher-tier review with the burden of adding evidence to the dossier. Stage 6 (presale open) is the moment the dossier hash anchors on-chain. From this moment forward, the marketing surface renders from the dossier and the team cannot say one thing publicly while a different document is on-chain.
THREE ELIGIBILITY TIERS, RETAIL-ACCESS CALIBRATIONThe tier assignment at S05 calibrates retail access to the depth of operating evidence. Projects with substantial operating substance can take retail capital at scale; projects with thinner evidence route to qualified or private tiers where participants accept higher verification and structural protections.
T1RETAIL OPEN
Open retail access, broadest participationhighest evidence depth required
Evidence thresholdOperating revenue or measurable throughput; audit attestation by AUDITOR-role parties referencing current code or operating record; founder identity verified; no undisclosed material adverse events.
Examples of typical projectsEstablished RWA platforms with settled deal history; renewable installations with operating meter records; protocol projects with deployed product, public usage, and audited contracts.
Participant rulesOpen to retail wallets without additional verification beyond standard KYC requirements applicable in the participant's jurisdiction.
T2QUALIFIED
Qualified investor access with verification at participationmid evidence depth, structural protections
Evidence thresholdFounder identity verified; operating-evidence threshold lower than Retail Open; project must demonstrate path to T1 (operating revenue, throughput growth, or measurable usage); audit reports referenced to deployed code (not generic).
Examples of typical projectsFunded software projects pre-revenue; RWA platforms with limited operating history but verifiable team and asset; renewable projects under commissioning.
Participant rulesParticipants must complete qualified-investor verification (jurisdiction-specific). Per-wallet caps apply. Mandatory lockup periods exceed Retail Open defaults.
Evidence thresholdFounder identity verified; team credentials documented; business plan with measurable milestones; IP and capital plan disclosed. Pre-revenue concepts route here. The protocol still requires verifiable identity and operating intent.
Examples of typical projectsPre-revenue concepts, research-stage protocol projects, early-stage RWA structuring with no settlement history yet.
Participant rulesAccredited-investor verification required (jurisdiction-specific). Closed to public retail. Per-wallet caps and lockup periods most restrictive.
Three eligibility tiers ranked from broadest retail access to most restricted private placement. The protocol enforces tier assignment at the smart-contract level; a team cannot route a T3 dossier to T1 retail by adjusting the marketing surface.
EDMA MASTER PLAN, LAUNCHPAD POSITIONThe Launchpad lands in Phase 4 of the EDMA master plan. The protocol primitives it depends on are mature (shipped through Phase 1 to Phase 3). The Launchpad-specific build covers admission flow, dossier schema, escrow mechanics, and governance. The Presale Builder self-service tool follows in Phase 5.
Presale Builder, the issuer-facing self-service tool for dossier composition and admission, follows here.
EDMA master plan, Launchpad position. The protocol primitives the Launchpad depends on (PoV Gate, Attestor Registry, One-Claim Ledger, Settlement) are mature, shipped through Phases 1 to 3. The Launchpad-specific build is Phase 4; the Presale Builder self-service tool follows in Phase 5.
What is shipped vs what is in progress
The protocol primitives the Launchpad depends on are already live: the PoV Gate produces the deterministic verification chokepoint, the Attestor Registry provides the role-bound identity and signing infrastructure, the One-Claim Ledger enforces asset exclusivity, and the milestone-gated settlement mechanism that the Global Trade Marketplace uses is the primitive the Launchpad reuses for tranche-gated capital release. These are the green nodes on the timeline above.
The Launchpad-specific build work scheduled for Phase 4 covers four areas: the admission flow described on this page, the canonical-JSON dossier schema and front-end documented at KPI proof, the escrow contract and tranche-release mechanics documented at Capital release, and the ongoing governance cadence documented at Governance. The companion Presale Builder tool (Phase 5) will offer self-service tooling for the team to compose a dossier and run the admission flow.
Continue the For Issuers series
This page covered the admission flow at the structural level. The remaining three pages in this section drill into each substantive component:
KPI proof. The five-block canonical-JSON evidence dossier structure and the route-specific evidence requirements by asset class.
Capital release. The escrow-to-tranches mechanism that gates how much capital the team can access after admission, and on what schedule.
Governance. The post-admission cycle of quarterly re-attestation, material-change disclosure, annual audit refresh, and the revocation framework for when obligations are not met.
