MIBDOG Docs
Platform Paper
The system paper behind MIBDOG: product thesis, launch architecture, operating model and trust boundaries.
This paper defines MIBDOG as a product system: its launch architecture, visibility layers, operating model and trust boundaries. It is product documentation, not financial guidance.
Self-custodied
Creator actions stay signed by the end-user wallet.
Profile-linked
Launches can be tied to profiles, identity and discussion surfaces.
Policy-shaped
Utilities, visibility and access are shaped by product rules.
1. What MIBDOG is
MIBDOG is a coordinated launch network that combines launch rails, social identity, utility surfaces and operating controls in one product. It is designed to make launches more legible, inspectable and operationally structured in public.
2. Why MIBDOG exists
Early-stage launches need speed and low friction, but they also need context. MIBDOG exists to reduce the gap between launching a token and building visible public accountability around it.
3. System thesis
MIBDOG is not only a token launch surface. It is a coordination layer that connects onchain creation, creator identity, profile history, discussion surfaces and policy-controlled utilities in the same system.
4. Launch architecture
MIBDOG uses Meteora Dynamic Bonding Curve rails for launch execution. Stellar Seed supports a faster-path creation flow, while Black Hole enables stricter launch posture, deeper configuration and stronger operational control around the launch.
5. Custody, signing and execution
Creator actions are signed by the creator wallet. Platform-controlled wallets may exist for fee collection, utilities and service operations, but they do not replace creator signing or take custody of creator intent.
6. Identity and public accountability
Launches can be linked to creator profiles, posts, discussion threads, MIB-S activity, X-linked identity and reserved handles. The goal is to make launches visible as part of a broader public network surface, not as isolated token pages.
7. Operating layer
Admin controls, invite policy, moderation, sponsor placement, verification, ranking and terminal surfaces together form the operating layer of MIBDOG. These are product surfaces inside the same system, not separate brands or detached modules.
Boundaries & reading limits
These are the two sections that define how the paper should be interpreted and where the product stops.
8. Trust boundaries
MIBDOG provides orchestration, visibility, product rules and operational interfaces around launches. It does not replace user custody, eliminate market risk or convert product documentation into financial guidance.
9. What this paper is not
This paper describes the product, its system behavior and its trust boundaries. It should not be read as a valuation document, investment thesis, guarantee of future governance, or promise of token outcome.