LAUNCHPAD_BUILD_PLAN.md
Launchpad build plan
Creator launch flow, collection setup, mint controls, public discovery, and the acceptance gates that keep unfinished capabilities off the live surface.
Read the current public modelCONFIGURATION REQUIRED Wallet transactions disabled
DOCUMENTATION LIBRARY
Every finalized document, accounted for.
This public index translates the local technical documentation into clear product language. Each item points to the website section where its current user facing model is explained.
Safe public summariesPrivate addresses, credentials, deployment commands, signer procedures, and unfinished beta implementation details are not reproduced here.
PRODUCT
4 documentsMINT_PRODUCT_SCOPE_IMPLEMENTATION_PLAN_2026-08-28.md
Product scope and implementation
The finalized platform map across creation, marketplace, profiles, rankings, analytics, testnet controls, and the public beta boundary.
Read the current public modelPHASE_0_5_TESTNET_READINESS_2026-08-29.md
Roadmap items 0 through 5
A concise readiness record for the completed foundation, product surfaces, data paths, controls, verification, and remaining deployment acceptance work.
Read the current public modelLEGAL_PRODUCT_AND_DOCUMENTATION_STRUCTURE_2026-08-29.md
Legal and product structure
The current economic model, user disclosures, noncustodial boundaries, feature status rules, and separation between code readiness and launch approval.
Read the current public modelSECURITY
6 documentsSECURITY.md
Security model
The platform security boundary, wallet safety model, role separation, validation strategy, and responsible handling of sensitive configuration.
Read the current public modelTHREAT_MODEL.md
Threat model
The principal risks considered across wallets, contracts, APIs, chain data, privileged roles, rewards, and marketplace activity, plus their control families.
Read the current public modelMARKETPLACE_SOLIDITY_SECURITY.md
Marketplace contract security
Marketplace settlement assumptions, authorization boundaries, royalty and fee handling, transaction safety, and contract test coverage.
Read the current public modelFOUNDRY_AND_FORMAL_VERIFICATION.md
Contract verification
The contract testing and verification approach used to validate invariants, permissions, accounting behavior, and failure conditions before deployment.
Read the current public modelBUG_BOUNTY.md
Vulnerability reporting
How security findings should be reported, what information helps investigation, and why suspected vulnerabilities should not be disclosed publicly first.
Read the current public modelSECURITY_OPERATIONS_GATES.md
Security operations gates
The required review, test, configuration, monitoring, and approval checkpoints separating a passing build from an authorized release.
Read the current public modelOPERATIONS
7 documentsDEPLOYMENT.md
Deployment model
How validated releases move through controlled environments while preserving role separation, configuration checks, and rollback readiness.
Read the current public modeldeployment-pipeline.md
Release pipeline
The automated build, test, security, packaging, and deployment stages used to prevent incomplete or mismatched code from reaching users.
Read the current public modelCANARY_AND_ROLLBACK.md
Canary and rollback
The staged release and recovery approach for limiting exposure, observing health, and returning to a known good version when acceptance checks fail.
Read the current public modelINCIDENT_RESPONSE.md
Incident response
The public facing response model for triage, containment, user communication, recovery, and post incident follow through.
Read the current public modelRECOVERY_AND_BACKUPS.md
Recovery and backups
The continuity model for source, configuration, indexed data, and deployment recovery without treating recoverable projections as custody of user assets.
Read the current public modelMAINNET_RELEASE_GATES.md
Mainnet release gates
The explicit technical, security, legal, operational, and ownership checks that must pass before any mainnet activation can be considered.
Read the current public modelMAINNET_BATCH_01.md
Mainnet batch planning
The first proposed release grouping and its dependency on completed acceptance gates. This is planning material, not a statement that mainnet is active.
Read the current public modelDATA
2 documentsindexer.md
Chain data indexer
How finalized chain events become marketplace activity, ownership state, profiles, rankings, and analytics, including expected confirmation delays.
Read the current public modelPRIVACY_AND_RETENTION.md
Privacy and retention
What public chain and application data may be processed, why it is needed, how retention is limited, and where blockchain permanence still applies.
Read the current public modelSTAKING
1 documentsTESTNET_STANDARD_STAKING_RELEASE_RUNBOOK.md
Soft staking testnet release
The safe testnet model for wallet retained NFTs, finalized ownership checks, reward claims, configurable reward sources, cooldowns, and low pool warnings.
Read the current public modelVAULT
3 documentsRWA_STATUS_AND_ROADMAP.md
Vault status and roadmap
The current status of the vault work, its testnet boundary, unresolved dependencies, and the checks required before broader availability.
Read the current public modelRWA_VAULT_ARCHITECTURE.md
Vault architecture
The proposed separation of eligibility, seats, valuation, liquidity, distributions, governance delay, and user facing disclosures.
Read the current public modelVAULT_SEAT_PRODUCT_SPEC.md
Vault seat product specification
The intended user experience and constraints for vault seats, including eligibility, transparency, transfer behavior, and risk presentation.
Read the current public modelA documented feature may still be testnet only, gated, or unavailable. Its linked status page is the source of truth for current availability.