Fractured Paper v1

Canonical Source

This page is the canonical Fractured Paper. It is the authoritative reference for the Built From Fracture ecosystem — its origin, its token mechanics, its interface model, its holder tier structure, and the Ecosystem it powers. A downloadable PDF is available as an optional export of the same content, but the web page is the source of truth and will be kept up to date first.

Contents:

• 01 — Origin & Fracture
• 02 — System & Mechanics
• 03 — Adaptive Interface
• 04 — Holder Tier Model
• 05 — Ecosystem Structure
• 06 — Launch Status

Origin & Fracture

Built From Fracture did not begin as a token. It began as a body on an operating table — seven fractures in a single spine, one surgery, and the slow, deliberate reconstruction that followed. The name is not a slogan. It is a description of the system's first principle: that the most durable structures are the ones that have already been broken and rebuilt with intention.

Most crypto projects start from a thesis about markets. BFF starts from a thesis about resilience. The fracture is the data; the rebuild is the protocol. Every mechanic in this paper — the token model, the tier system, the adaptive interface, the ecosystem — exists to apply that same logic to digital and economic surface area: identify where things break, design the reconstruction so the next load goes through cleanly, and make the repair visible.

The problem BFF was built to answer is not "how do we launch a token." It is "how do we build an ecosystem that doesn't extract from the people who hold it together." That answer requires more than a chart. It requires a story with structural weight, a token whose mechanics serve the ecosystem rather than the other way round, and a set of products that justify the token's existence on their own terms.

The four narrative phases — Break, Fall, Rebuild, Takeover — are not marketing. They are the operating arc of the project itself. Break is the inciting event. Fall is the silent middle where most projects vanish. Rebuild is the discipline that turns a fracture into a frame. Takeover is the point at which the system has enough structural integrity to carry others.

System & Mechanics

$BFF is the utility and coordination token of the ecosystem. It is deployed on Sui and is designed to do three things: settle transactions across the BFF product suite, route fees back into supply pressure, and gate progressive access to the deeper layers of the ecosystem through the holder tier model described in §04.

Supply & emission. The token launches with a fixed, transparent supply. There is no inflationary mint mechanic. New supply cannot be created after launch. All circulating supply is observable on-chain and the contract address is published on the homepage footer and inside the DApp — never behind a gate.

Fee routing. Revenue generated by the BFF ecosystem (payments, SaaS subscriptions, real-world services) is routed through a transparent fee path. A defined share of ecosystem revenue is used to execute scheduled market buys of $BFF, with a portion of those buys directed to a burn address. The net effect is that real product usage translates into verifiable supply reduction, rather than emissions diluting holders.

Transparency rules. Every mechanic in this section is designed to be auditable from a block explorer without needing to trust the team. The contract address is public. Buy and burn transactions are on-chain. The DApp surfaces live price, holder tier, and balance data from the chain directly. No off-chain "internal" balance ever stands in for an on-chain one.

Sustainability logic. The token does not depend on speculation to function. It depends on the ecosystem in §05 generating real revenue from products people use. The mechanics in this section convert that revenue into structural support for holders. If the products work, the token works.

Adaptive Interface

The BFF interface is not a single static site. It is an adaptive surface that recognises who is looking at it and surfaces the next correct layer of the system — without ever hiding what is underneath. Visitors see the story. Holders see balance, tier, and the DApp. Founders see the protocol layer. Each layer is additive; nothing is taken away as you progress.

Progressive disclosure, not gating. The defining principle of the interface is that access reveals itself rather than being demanded. A first-time visitor is not blocked from understanding the system; they are shown the narrative entry. A connected holder is automatically shown their tier, their balance, and the surfaces their tier unlocks. A founder-tier holder sees the additional protocol surfaces without needing to find a secret URL.

Dual canvas hero. The home page hero is rendered as two distinct canvases — a widescreen desktop composition and a 9:16 mobile composition — each with its own coordinate system for interactive hotspots. This is deliberate. A fractured B logo, rendered correctly at one aspect ratio and stretched at another, would itself be a contradiction of the paper's first principle. Two canvases, two hotspot arrays, one identity.

Single hierarchy. The site enforces a strict information hierarchy: Concept → Story → System → Action → Trust. Each function in the UI exists in exactly one location. There is one navigation system (hamburger), one set of secondary actions (the action strip), one footer (the trust layer). Duplication is treated as a structural defect, not a stylistic choice.

Holder Tier Model

The holder tier model is the bridge between the token and the ecosystem. Holding $BFF is not a passive position; it is the credential that opens progressively deeper surfaces of the system. Tiers are determined entirely by on-chain balance, evaluated live by the DApp.

Tier structure. The tier model is layered so that each level unlocks a coherent slice of the ecosystem rather than an arbitrary perk list:

• Entry — connect a wallet, hold any amount of $BFF, and the DApp recognises you as part of the system. Live price, balance, and contract address visible.
• Builder — a holder threshold that unlocks the operational surfaces of the ecosystem: discounted product access, priority on new product drops, and visibility into upcoming releases.
• Architect — a higher threshold that unlocks ecosystem-wide privileges: revenue-share-linked surfaces, early access to integrations, and direct input into product roadmap priorities.
• Founder — the highest tier, mapped to the Founders Access surface. This tier represents the structural backbone of the ecosystem and carries the deepest protocol-level access.

Anti-extraction rules. The tier model is explicitly designed so that higher tiers do not extract value from lower ones. There is no referral pyramid, no upline, no recursive reward structure that pays insiders out of newcomer activity. Every tier benefits from the same underlying mechanic: ecosystem revenue → buy and burn → structural support for all holders.

Live evaluation. Tier status is evaluated on every DApp session against current on-chain balance. There is no manual "claim my tier" step and no off-chain registry. If your balance changes, your tier reflects it on the next session.

Ecosystem Structure

The Ecosystem is the product layer of Built From Fracture. It is a connected suite of real products that generate real revenue, all settled through the same payment rails and all feeding the same token loop described in §02. The point of the ecosystem is to give the token a reason to exist that is not "speculation about itself."

The product suite. Each product is a standalone service with its own utility, designed to be useful to non-holders and additive for holders:

• Diet — structured nutrition and discipline tooling. Built from the same rebuild logic that drives the rest of the system.
• Horoscope — narrative and self-tracking surface. A daily touchpoint that keeps users inside the ecosystem.
• Travel — travel planning and booking utilities with crypto-native settlement.
• Merch — physical goods that carry the brand into the world and route revenue back into the token loop.
• Web Services — SaaS-class tooling for builders inside and outside the ecosystem.

Payment rails. The ecosystem accepts $BFF, SUI, USDC and USDT natively. Where a real-world product requires fiat fulfilment (for example a physical merch shipment or a travel booking), the system uses a hybrid settlement path: crypto-side capture, fiat-side fulfilment, with the crypto leg always routed through the fee path defined in §02. Holders are not penalised for choosing the crypto rail; they are rewarded for it.

How the loop closes. Every product in the Ecosystem sends a defined share of its revenue back through the fee path. That fee path executes scheduled buys of $BFF and burns a portion of them. The more the ecosystem is used, the more structural pressure that places on supply. This is the mechanic that connects everyday product usage — a meal log, a booking, a merch order — to long-term holder alignment.

Roadmap, in narrative form. The roadmap is described as a sequence of structural milestones rather than a list of dates, because the point of the system is durability rather than theatre. Stage one is launch and ecosystem activation — token live, DApp live, first product surfaces online. Stage two is depth — additional product verticals, NFT and staking surfaces, expanded tier utility. Stage three is integration — the full Ecosystem operating as one connected system, with payments, services, and tier-based access stitched together end to end.

Launch Status

Built From Fracture is being released in carefully planned phases. The Day One launch establishes the foundation of the ecosystem, while additional protocol modules are introduced as they are completed, tested, and ready for deployment.

Available at Launch

• $BFF Token
• Core Built From Fracture platform
• Holder recognition and tier framework
• Initial ecosystem products currently released
• Community infrastructure

Coming in Future Phases

• NFT Initiative
• Fracture Miner
• Fracture Vault
• Expanded holder rewards
• Additional ecosystem products
• Governance features and protocol expansion

The ecosystem is intentionally expanding in stages to prioritise security, transparency, and long-term sustainability over rushing features to market. Every future release will be announced through the official Built From Fracture channels.