Portable identity → public proof → durable evidence → fixed launch rules → provable participation → fail-closed execution.
BermLaunch is built on Berm Protocol, the public verification layer for portable identity. Current X method: berm.external_account_binding.x/2. Read the Berm Protocol docs →
Communities recruit under a campaign constitution before any token exists.
Only bounded, purpose-specific evidence requests; this page never signs.
Accepted evidence and campaign positions are portable records.
Missing or conflicting evidence fails closed.
Inspect the campaign, evidence and public verification surface.
A BRM session establishes a portable npub identity.
Identity-specific acts remain domain separated.
Only accepted identity evidence is retained.
Session mismatch and invalid evidence are rejected.
Compare the accepted binding to the displayed npub.
A public X proof is checked against an npub binding.
The binding claim has a fixed external-account purpose.
Raw capture and accepted evidence references are retained.
Unbound transport or mismatched proof is unavailable or rejected.
Review the accepted binding and its evidence chain.
R3 enrollment precedes a verified X publication and accepted campaign position.
Enrollment and proof acts are separated by purpose.
The unique campaignId/npub position and receipt are retained.
Replay, rebind, corruption and conflicting positions fail closed.
Inspect the reconstructed portable receipt.
Recruiting precedes creation, curve activity, and any graduated market.
No market action is implied by lifecycle display.
Authoritative lifecycle evidence controls public stage.
Absent asset/provider evidence leaves market unavailable.
Read the bound provider and lifecycle facts.
Founders, Graduators and Boosters are public aliases for canonical cohorts.
Participation does not rewrite constitution economics.
Canonical cohort IDs, capacities and BPS ranges remain fixed.
Closed, filled and unknown stages have no false join CTA.
Compare displayed shares to canonical BPS ranges.
Provider-specific evidence is normalized behind a provider-neutral product read.
Provider selection is not a user signing request on this page.
Bound launch/provider identities are evidence-backed.
Unproved provider facts remain unavailable.
Inspect provider evidence and Trust & Verify.
Post-launch fee presentation uses canonical accounting evidence, not volume.
No fee claim is signed from this public surface.
Canonical asset accounting and eligible allocation evidence persist.
Missing accounting is unavailable, never zero.
Compare canonical asset amounts to provider accounting evidence.
It explains what evidence supports a product claim.
Verification does not create a signature.
Only independently verified evidence can support a positive state.
Missing roots, receipts or provider facts fail closed.
Use the dedicated Trust & Verify route.
Raw artifacts are preserved with semantic verification.
Evidence signatures retain their bounded domain.
Hashes, receipts and references make reconstruction possible.
Byte, hash or schema mismatch is rejected.
Run the supplied offline verifiers over exact bytes.
Private keys stay with the user and signing remains explicit.
Only clearly scoped requests should be approved.
Public evidence, not private key material, is retained.
Unexpected origins, wrong identities and ambiguous outcomes stop.
Check origin, request fields and accepted evidence before approval.
Browser, server and provider seams expose typed fail-closed reads.
Production signer scope is intentionally narrow.
Versioned artifacts and complete history bind implementation.
Schema, transport, projection and identity mismatches stop processing.
Use exact manifests, source bundles and behavioral tests.