Creation UX with clear consent boundaries.
This route is intentionally polished but non-transactional. It helps founders validate copy, category fit, and disclosure logic without simulating a live mint, signature request, or custody flow.
Lead with disclosure rules first, then shape the category and proof posture around what the member is knowingly opting into.
creation composer
Mint configuration
Choose the founder lane you want to preview.
Set the disclosure logic before any future mint logic exists.
Preview how the page should react when proof is public, protected, or hybrid.
Ideal for selective disclosure: show the contribution happened without exposing the whole payload.
Best when the member shares one precise fact or artifact and keeps the rest out of scope.
Use a visible badge or receipt while the supporting files remain encrypted or permissioned offchain.
Proof of Contribution is framed as the active lane, which means acknowledgement that a member delivered a useful action, artifact, introduction, or proof point.
Selective disclosure posture keeps the explanatory copy honest: Best when the member shares one precise fact or artifact and keeps the rest out of scope.
Hybrid proof state tells the member what future viewers could see while protecting what stays offchain.
live copy reaction
Hybrid proof state
Narrow, consent-led releaseAcknowledgement that a member delivered a useful action, artifact, introduction, or proof point.
future handling
What the interface should explain
Ideal for selective disclosure: show the contribution happened without exposing the whole payload.Use a visible badge or receipt while the supporting files remain encrypted or permissioned offchain.
transaction boundary
No live mint action
Front-end preview onlyThis surface reacts to choices, but it does not connect a wallet, request a signature, or create an NFT.
Category library
Use these lanes to preview intent before building policy, storage, and mint logic for production.
Art
Collector-facing drops, premium human-centered visuals, and weekly cultural releases rooted in real participation.
Private Submission
Scoped intake for sensitive materials that should be reviewed privately before any recognition is issued.
Coin / USDC
Receipt-style proofs, treasury acknowledgements, or campaign-specific stablecoin participation records.
General Token
Token-linked badges, governance-era artifacts, and broad network participation signals.
News
Media drops, network updates, launch confirmations, and event-linked information passes.
Legal Docs
Diligence acknowledgements for documents that must never be posted openly or implied to live fully onchain.
Identity
Proof-of-person, role, or routing identity markers where the member intentionally discloses a narrow fact.
Partner Diligence
Founder-to-partner review lanes for vetted materials, relationship signals, and coordination readiness.
Research
Proof-of-research artifacts, insight memos, and intelligence snapshots that earn contribution status.
Community
Participation badges, seasonal rituals, and “showed up for the network” recognition moments.
Access Pass
Tiered entry, early access, campaign rooms, and gated operator circles with explicit scope.
Proof of Contribution
Acknowledgement that a member delivered a useful action, artifact, introduction, or proof point.
Other
Reserved for tightly defined founder experiments that still honor clear consent and bounded access.
consent lane
Permission and disclosure states
preview sequence
What this configuration implies
Choose the mint lane — Start with the contribution type, the proof you actually need, and whether the result is for public culture, private review, or both.
Set access posture — Define what would be visible as proof, what stays protected offchain, and who is allowed to open the protected layer.
Get explicit consent — Before any future live mint exists, the member must understand the ask, the disclosure scope, and the reward they are choosing to unlock.
Current response: Use a visible badge or receipt while the supporting files remain encrypted or permissioned offchain.
Consent state: Waiting on acknowledgement before any future live flow would continue.
onchain / offchain split
What belongs where
No wallet signature or mint transaction is triggered in this preview.
Any future onchain state should hold only the proof layer, issuance metadata, or claim reference when implemented.
Sensitive documents, identity data, or diligence materials should remain protected offchain.
Members need clear acknowledgement before any live reward or mint flow can proceed.
founder reminder
Premium preview, not fake execution.
The interface responds to category, access, state, and consent choices — but it deliberately stops short of any wallet prompt, mint orchestration, or transaction theatre.
Choose the mint lane
Start with the contribution type, the proof you actually need, and whether the result is for public culture, private review, or both.
Set access posture
Define what would be visible as proof, what stays protected offchain, and who is allowed to open the protected layer.
Get explicit consent
Before any future live mint exists, the member must understand the ask, the disclosure scope, and the reward they are choosing to unlock.