SPRAWL THE WHITEPAPER / NOVEMBER 2026
A PROTOCOL FOR WHAT COMES NEXT

Launch somewhere.Sprawl everywhere.

Native token launches.
One supply. A world of markets.

Explore the whitepaper
SPRAWL PROTOCOLNOVEMBER 2026A launch is only the beginning.
01 / THE THESISFROM A SINGLE LAUNCH TO A CONNECTED ASSET
READING THIS EDITION

Protocol design. Public testnet evidence. A mainnet path. This edition separates demonstrated testnet functionality, development work and production decisions. The four-network vision is not a claim of a completed four-chain mainnet product. Figures are dated November 2026 and measured on public testnets. They are not live counters or guarantees.

Your community
has no borders.
Why should
your token?

Launching creates a token.
What happens next creates its future.

A token can begin on one chain while its community lives across many. Reaching another network means coordinating transport, new liquidity and another market. A successful launch does not solve that by itself.

SPRAWL brings those steps into one launch. A creator picks a HOME network and the networks the token should reach. One Genesis on HOME funds them all, and every selected market opens with permanent liquidity at the same moment and the same price.

The asset expands.
The supply does not.

See how supply is preserved
01

Create

Set the identity, HOME
and the selected networks.

02

Launch

Genesis sells on
one curve on HOME.

03

Fund

The raise funds
every selected market.

04

Sprawl

Every selected market
opens at one shared time.

A creator selects two, three or four networks before Genesis. Each needs its local pair asset, transport and checks in place. Opening times are measured, not guaranteed.

The thesis in one minute.

SPRAWL is infrastructure for the life of a token after creation. It connects native issuance, one coordinated multichain graduation, permanent liquidity on every selected network, one canonical cross-chain supply and configurable project rewards in a single protocol lifecycle.

The central design choice is to make reach part of the asset’s original plan. A project commits its HOME, its selected networks, its pairing and its reward policy at creation. When Genesis completes, the raise funds every selected market and they open together. Each network’s contracts check their own funding, price and timing before a market opens. SPRAWL’s signers set the shared opening time within on-chain limits; they cannot set prices, move funds or add a network the creator did not select.

For creators, this reduces the coordination required to reach another ecosystem. For traders, it means local markets for a recognisable global asset. For builders, it provides a foundation for launch experiences, analytics and community tools. The value proposition is the integration of these mechanisms, not an unsupported claim that cross-chain tokens or launchpads have never existed.

HOW TO READ THE CLAIMS

Proof has a scope.

Each capability belongs to an environment and a release. The labels below say how far each one has been shown. None of them is a promise of production availability.

Demonstrated
A recorded deployed journey, limited to the named testnets and release.
Testnet only
Worthless test assets, scaled settings or trust assumptions that are not approved for production.
In development
Code, tests or rehearsals exist; the complete hosted journey is not yet demonstrated.
Planned
A product or infrastructure direction, with availability still to be delivered.
Open decision
Architecture or economics requiring an explicit decision and evidence before mainnet.
02 / THE OPPORTUNITYSPRAWL / WHITEPAPER

One market.
Many front doors.

The opportunity begins with a practical mismatch: communities cross networks more easily than a newly launched token can.

ESTIMATED ACTIVE CRYPTO USERS40–70M

a16z crypto’s 2025 estimate of people using crypto actively.

a16z crypto · October 2025 [1]
STABLECOIN MARKET CAPITALISATION$311B

At year-end 2025, up 48.9% over the year in CoinGecko’s report.

CoinGecko · 2025 annual report [2]

Historical market context, not SPRAWL’s addressable revenue, user base or projected market share. People, wallets, addresses and capital are different measures.

Fragmentation is work.

A launch on one network does not automatically produce a market on another. Teams need a token representation, transport, quote-asset liquidity, local infrastructure and a way to explain what is authentic. Separately issued copies create supply and identity problems. A bridge alone moves an asset; it does not necessarily fund and initialise its next market.

SPRAWL’s proposed advantage is to coordinate those dependencies around a shared asset identity and a funded execution plan. Its market is the intersection of token creation, multichain distribution and community participation. Industry-wide numbers show the surrounding activity; they do not establish demand for this particular product.

THE COORDINATION PROBLEM

A launch.
Then another project.

Arrange a representation. Find quote liquidity. Integrate another venue. Coordinate the next deployment.

THE SPRAWL APPROACH

A launch.
With a lifecycle.

Select the networks once. Complete one Genesis. Open every selected market together under protocol checks.

A product for three participants.

Creators need an understandable launch path, predictable protocol rules and a way for trading activity to support their community. Traders need authentic local markets, clear supply accounting and visibility into liquidity and execution costs. Developers need reusable interfaces and state transitions rather than another isolated launch page.

Adoption must be earned through reliable launches and useful markets. The measures that matter after mainnet are successful journeys, retained creators and traders, usable liquidity, execution reliability and sustainable activity. Repository size and testnet activity are development evidence, not substitutes for those outcomes.

03 / NATIVE LAUNCHESSPRAWL / WHITEPAPER

The first market.
A lasting foundation.

Native launches begin with one fixed supply, a HOME network and the networks the token will reach. Graduation opens a permanent market on every selected network at once.

NATIVE PROJECT TOKEN / ALLOCATION BY SELECTED NETWORKS1 billion fixed units
Genesis sale

645.6 million units

HOME pool

104.3 million units

Other selected pools

250.2 million units, 83.4 million each

Graduation target about $100,000 market value. The curve raises about $35,500, all of it paired with these pool tokens at one opening price. Current model, subject to final validation.

From Genesis to graduation.

Every V1 network can be HOME: Base, Robinhood Chain, BNB Chain and Solana. The creator selects HOME and one to three other networks; all four are selected by default. On testnet, each network has served as HOME for a Genesis and a coordinated graduation onto all four networks, run through contract calls and SPRAWL’s own tooling. The hosted Create flow does not use this path yet.

Genesis is a linear bonding curve that starts at a $10,000 market value and ends at a graduation target fixed before trading begins: about $60,000, $75,000 or $100,000 for two, three or four networks. Anyone can buy or sell on the curve at its current price, with no anti-sniping rules. The target cannot move with trading volume or fees. The buy that reaches it freezes the curve, and every selected market opens at the curve’s final price, so the transition is price-continuous everywhere.

Tokens not sold in Genesis form the token side of the initial pools; HOME receives 1.25 times the share of each other selected network. The raise forms the paired side. There is no separate inventory vault and no later minting: these are allocations of the original issuance, and graduation never increases the canonical economic supply.

Liquidity can only grow.

Genesis trades build a separate 0.6% liquidity fund that is used only after graduation. Together with 0.20% of every later trade, it is designed to buy tokens gradually, never on a predictable schedule, and add them with paired assets to the same official pools, weakest first. Every protocol-funded addition is permanently locked with its fee rights kept. This programme is in development.

Pool sizes follow from the fixed target and the number of selected networks. This is the current model, subject to final validation before mainnet. Testnet amounts use test dollars, and this edition does not present a testnet liquidity amount or graduation valuation as a final mainnet promise.

What is fixed, and what is versioned?

The fixed one-billion supply is a protocol rule. The split between the Genesis sale and the initial pools follows from the graduation target and the number of selected networks, both fixed before Genesis begins. Acceptable paired assets and execution parameters depend on the approved release and configuration. Testnet settings exist to exercise the lifecycle and must not be mistaken for production economics.

SPRAWL does not charge a separate creation fee under the current model; creators pay network gas. Genesis trades carry a 1.2% fee; trades after graduation carry the 1% canonical trading fee. Imported assets and external launch providers are separate capability tracks, not implied by native creation being enabled.

The allocation diagram describes a token launched by a creator through a native launch. Tokens launched on SPRAWL are their creators’ own assets, not $SPRAWL, and the diagram is not an allocation for the future $SPRAWL token: its allocation and tokenomics are not finalised (chapter 14).

04 / ONE SUPPLYTHE PRINCIPLE THAT HOLDS IT TOGETHER

Cross chains.
Keep the asset.

More networks should mean more places to participate, not another independently issued token on every chain.

FIXED CANONICAL SUPPLY
1,000,000,000TOKENS
INTERACTIVE EXPLANATION
HOME-ORIGIN EXAMPLE
HOME1,000MOutside transport custody
IN TRANSIT0Awaiting destination issuance
DESTINATION0Authenticated representation
HOME TRANSPORT BACKING 0 Total economic supply conserved
One issuance. One home.

The token begins with a fixed canonical supply. This simplified view groups all home-chain units before a cross-chain transfer.

Backing is not
counted twice.

Tokens moving outward from HOME are locked there. An authenticated destination issues the corresponding representation. Returning tokens are burned at the destination before their backing is released at home. An EVM HOME holds the backing in a lockbox; a Solana HOME holds it in an OFT adapter escrow. The model is the same.

SPRAWL uses LayerZero V2 as its single cross-chain transport, with OFT representations on every network other than HOME. Message verification, minting caps and reconciliation are essential parts of the model.

The supply invariant

H + D + I = SHome units outside transport custody + normalised destination units + units in transit = fixed canonical supply.

L = D + ILocked home backing supports represented and in-flight units. It is not added to economic supply a second time.

Locked home backing accounts for destination representations and transfers in flight. This example moves 100 million whole normalised units, omits protocol allocation details and has no rounding dust. The general reconciliation also accounts for rounding dust where a transport permits it. SPRAWL’s transport, described below, instead rejects amounts that are not exactly representable. All outstanding transfers still need reconciliation. “At home” does not mean all those units are publicly circulating.

Supply conservation does not guarantee equal market prices, instant delivery or transport availability.

Identity survives the transfer.

A canonical asset is identified across its home and registered destinations. A destination representation is accepted because its transport, pool and asset binding are authenticated, not because it displays the same ticker or logo. Arbitrary lookalike tokens are outside that identity.

Accounting uses normalised units. Tokens on the EVM networks use 18 decimals and tokens on Solana use six; transfers move in six shared decimals. Scaling, unrepresentable dust and the return path must reconcile without increasing economic supply. Per-network minting caps limit what a single transport failure could issue, and no network can ever hold more than the global supply.

This illustration is the lock / mint model used for every HOME network, EVM and Solana alike. Transport still depends on the approved pathway, the destination’s security model and its operational availability. LayerZero OFT standard [3]

TECHNICAL EXHIBIT / PRECISION

Different decimals.
The same quantity.

One token has 1018 atomic units on its EVM home and 106 on the six-decimal Solana representation. The lane must preserve the value, not the raw integer.

TRANSFER AMOUNT1.000000tokens
HOME / 18 DECIMALS1,000,000,000,000,000,000atomic units
DESTINATION / 6 DECIMALS1,000,000atomic units
Exactly representable

The home amount is divisible by 10¹². The conversion produces one million destination atomic units, representing exactly one token.

Implementation example: SPRAWL’s OFT transport. On testnet, holders’ tokens have moved in both directions between Base, Robinhood Chain, BNB Chain and Solana, with locked HOME backing equal to the supply elsewhere after every transfer. Conceptual examples of its integer-precision guard, not transaction quotes.

Move between networks.

Once every selected market has opened and confirmed its opening to HOME, holders can move their tokens between networks. Tokens locked on HOME always equal the supply on the other networks, so a transfer changes where a token is held, never how many exist.

Token mobility is demonstrated on testnet. Its long-term role is under evaluation alongside planned cross-chain swaps through Relay, which would let a holder trade into another network’s market without moving the token first.

05 / COORDINATED GRADUATIONSPRAWL / WHITEPAPER

One Genesis.
Every selected market.

The buy that completes Genesis starts graduation. Every selected market opens at one shared time, once each network is funded and ready.

ILLUSTRATIVE GRADUATION / NOT A LIVE ASSETNetworks selected at creation · one opening time
  1. 01 / HOMEBaseHosts Genesis, then opens with the others
  2. 02 / SELECTEDRobinhoodOpens at the same time
  3. 03 / SELECTEDBNB ChainOpens at the same time
  4. 04 / SELECTEDSolanaSubmitted first, opens at the same time

Selected, not sequenced.

Any of the four networks can be HOME. The creator picks HOME and one to three other networks; all four are selected by default. The selection is fixed before Genesis begins and cannot later be changed by a creator, controller or administrator.

Every selected network opens at the same moment and at the same price. A network without an approved paired asset or usable transport cannot be selected, and no rule requires every launch to include all four networks.

01

Freeze

The buy that reaches the target freezes the curve. Nothing extra is asked of the buyer.

02

Fund

HOME graduates and funds each selected network’s paired asset through Relay, from the raise.

03

Sign

SPRAWL’s coordinator reads every network directly. Two of three signers approve one opening time.

04

Open

Solana’s opening is submitted first, then the EVM networks’. Every market opens at that time.

MEASURED ON TESTNET27–48s

From the final Genesis buy to a first trade on every selected network: about 29 s with Base as HOME, 30–34 s with Robinhood Chain, 27.5 s with BNB Chain and 48 s with Solana.

OBJECTIVE<100s

The normal-operation objective for every selected network, met with every HOME on testnet. A target, not a guarantee: measured times depend on each network’s inclusion and confirmation.

Two assets. One opening.

A new pool needs both the project token and its paired asset. Pool tokens, plans and closed pools are staged on each selected network during Genesis, with tokens moved over LayerZero. After the freeze, the paired asset arrives through Relay from the raise; SPRAWL holds no prefunded capital for it. A market opens only when both sides are in place, so no network opens with partial funding.

Raydium’s opening time cannot change once a Solana pool exists, so the Solana opening is submitted first; only after it is confirmed are the EVM openings released. If Solana misses its deadline, nothing else has been touched and a new time is signed. SPRAWL’s keeper and coordinator submit these steps, but neither can waive any network’s funding, price or timing checks.

Timing, late networks and unsuccessful launches

The opening time is set from measured inclusion times on each network, never from a fixed countdown. If a token’s markets can open safely in 20 seconds, they open in 20 seconds. A countdown shown to users displays the committed time; it does not control it.

A selected network that is not ready before the opening time does not open early or at a wrong price. It opens later at a fresh market price and is counted as a failure of simultaneous opening. If HOME itself misses the opening, it opens only at a price derived from the other markets’ recent trading, and stays closed when no defensible price exists. This HOME recovery is in development.

If a Genesis never completes, holders can always sell back to the curve, and its 0.6% liquidity fund must not be stranded: a recovery rule with public notice is being designed. Holders’ tokens and the curve reserve are never confiscated.

TECHNICAL EXHIBIT / OPENING CHECKS

Signed is necessary.
It is not sufficient.

Every network checks the signed opening against its own state, in the same transaction that creates and locks its pool. A signature cannot override missing funds, a wrong plan or a closed window.

OPENSS ∧ F ∧ P ∧ W ∧ ¬H
S Signed
Two of three SPRAWL signers approved one opening instruction for this asset.
F Funded
The paired asset delivered after graduation covers the plan, and the token side is in custody.
P Prepared
This network’s prepared plan is part of the signed list of selected networks.
W Window
The opening time lies inside this network’s lead limits and the graduation window.
¬H Not held
No guardian hold, and no opening accepted before: one opening per asset per network, ever.

A simplified reading of the opening checks in the graduation contracts and the Solana program. The pool opens at the curve’s final price, with its liquidity permanently locked.

Graduation states and partial delivery
PREPAREARMED

Plans, pool tokens and closed pools staged during Genesis.

GRADUATEFUNDING

The curve is frozen; paired assets are on their way.

GOOPEN

The signed opening is accepted; trading starts at the shared time.

These are implementation states, distinct from the friendlier progress labels used in a product interface. A token arrival is not a complete pool; the paired asset must also arrive before a network can accept its opening.

Before opening, a plan can be cancelled under its rules and returned funds are booked back. After every market has opened and confirmed its opening to HOME, token mobility between the networks is enabled.

Source: the states and checks of the graduation contracts and the Solana program. This summary deliberately omits configurable timing values rather than presenting testnet settings as production constants.

Trading across networks.

Relay is SPRAWL’s intended route for cross-chain trading. Auto Buy compares executable routes across every live market and chooses the one that delivers the most tokens after fees, gas, slippage and price impact; Auto Sell maximises net proceeds from the networks where a holder’s tokens actually are. Manual network choice stays available.

Auto Buy and Auto Sell are planned and not yet in the product. Executable quotes, not displayed prices, decide every route.

CURRENT MODEL / SUBJECT TO FINAL VALIDATION

Opening a pool.
Sustaining useful depth.

These are different problems. Arbitrage can help align prices; it does not by itself add permanent liquidity or prevent large price impact in a shallow pool.

Starting liquidity, four selected networks
ScopeStarting paired assetWhat it establishes
Current modelHOME ≈ $10,400
each other network ≈ $8,300		The whole Genesis raise funds the initial pools, less transport and pool-opening costs. Every pool opens at the curve’s final price; HOME receives 1.25 times each other network’s share.
TestnetTest dollars
same ratios, scaled amounts		Exercises the mechanism on public testnets. Test amounts are not real dollars.
Production modelFinal validationGraduation targets, pool depth and the liquidity-strengthening programme are confirmed before mainnet.

Two or three selected networks give fewer, larger pools from a smaller raise. Execution costs come out of the raise before pool funding. Liquidity strengthening is in development, not an implemented feature.

06 / PROTOCOL ARCHITECTURESPRAWL / WHITEPAPER

Separate responsibilities.
Connected by proof.

A shared lifecycle coordinates specialised contracts and services. Read interfaces describe state; authenticated on-chain rules authorise value movement.

EXPERIENCE
Launch interfacesTrading & analyticsBuilder applications
OBSERVATION & EXECUTION
Typed API + indexersKeeper + graduation coordinator2-of-3 opening signers
PROTOCOL
Asset & network registriesGenesis + graduation plansCanonical markets + locked LP
CROSS-CHAIN
LayerZero transportRelay fundingLanding + reconciliation

One pairing, local representations.

A project selects an immutable economic pairing, called a Pair Family in the protocol. Each destination uses an explicitly approved local representation of that family. The same economic unit may be represented by different issued tokens on different networks; symbols alone never establish compatibility.

This abstraction separates what a project is paired with from how that asset is represented or transported. An approved route is needed in each directed chain pair. Approval does not mean two representations are risk-free, exactly equal in price or interchangeable under every condition.

Native assets, stablecoins and other assets are categories the architecture can describe. A tokenised stock would also need an appropriate issuer, availability and legal product decision. SPRAWL does not manufacture an unofficial wrapped stock to bypass missing support. The production pairing and transport matrix remains a mainnet prerequisite.

A global view, honest local prices.

The Global Reference Price normalises canonical local markets into the paired family’s economic unit, uses time-weighted observations and combines eligible markets through a liquidity-weighted median. Stale, thin, insufficient-history and outlier observations are excluded under the configured policy. With one healthy market, that market supplies the reference.

The reference supports a coherent asset view. A fresh reference of the same kind, a median of recent time-weighted prices, decides the price at which a late network opens, never the stale launch price. It does not set every live market’s trading price or guarantee a fill. Local pools move independently, and their available depth determines execution. Market capitalisation must use one global supply basis rather than summing separately valued copies of the same backed units.

Trust boundaries for implementers

Registries establish approved assets, market identities, counterparties and releases. Transport authenticates a source and message; landing logic still checks that its content belongs to an authorised plan. Amounts, replay protection, destination bindings and completion receipts all matter.

An API response or indexed event is useful evidence for a client, not permission to move protocol custody. Clients must validate the selected network and release and obtain user signatures for user actions. Keepers provide liveness by calling contracts; their availability is a dependency, while contract constraints remain the authority. The graduation coordinator and its signers add timing: they choose an opening time inside on-chain limits, and cannot move funds or set prices.

FOUR-NETWORK V1 / RELEASE BOUNDARIES

One lifecycle.
Different chain adapters.

Base, BNB Chain and Robinhood Chain are EVM networks. Solana uses Rust programs and account-based bindings. Markets open on Uniswap v4 with SPRAWL’s hook on the three EVM networks, and on Raydium on Solana. Every network can be HOME, and each must prove the same economic invariants.

Implementation status by network, November 2026
NetworkRecorded implementationBoundary
Base SepoliaEVM HOME and destination; Genesis curve, graduation contracts and Uniswap v4 markets.As HOME: graduations onto two, three and four networks with real swaps on every network. Testnet only.
BNB testnetEVM HOME and destination; SPRAWL’s own testnet instance of Uniswap v4.As HOME: a clean four-network graduation. Uniswap v4 is the intended BNB Chain venue; messages from BNB Chain use a testnet-only verifier.
Robinhood testnetEVM HOME and destination; Uniswap v4 markets.As HOME: two four-network graduations. The testnet confirmation depth is sequencer inclusion only, not settlement finality.
Solana devnetNative HOME program with the same Genesis curve; landing and transport programs; Raydium pools; six-decimal tokens.As HOME: two-, three- and four-network graduations; an unattended four-network run in 48 s. Pools are created through a testnet pool-creator.

A release is part of the trust boundary.

Each HOME network runs its own isolated testnet suite, and the earlier release behind the hosted testnet app is left untouched alongside it. The same signed opening is checked on every network against that network’s own state; identities are 32 bytes, so an EVM network and Solana name the same asset exactly. A network name or a single working message is never enough to open a market.

Solana programs verify the signed opening themselves, before creating and locking their pool. These checks do not turn an upgradeable Solana deployment into immutable code: on devnet, the programs’ upgrade authority is a testnet key. Production upgrade authority and production transport coverage remain open.

PAIR FAMILIES / PRODUCTION ROUTES OPEN

A family is an identity.
A route is a separate proof.

A chain can support messages without supporting the required asset transfer. Both the project-token leg and the paired-asset leg must reach the destination safely.

  1. 01 / ECONOMIC PAIRINGFamily

    The immutable economic asset selected at creation.

  2. 02 / LOCAL ASSETRepresentation

    An explicitly approved token and issuer on the destination.

  3. 03 / DIRECTED PATHTransport

    A verified funding route, with conversion and custody assumptions made explicit.

Current launch eligibility requires approved usable coverage on at least two chains, including HOME. Broad pairing is an architectural capability, not an unrestricted production token menu.

Test dollars do not prove stablecoin coverage.

On testnet, a mock Relay depository and a SPRAWL filler stand in for Relay’s solvers and deliver SPRAWL’s own test dollar. Production assets bring issuer-specific representations, permissions, decimal formats and possible conversions. A USD family label does not make USDC, USDG and other dollars interchangeable.

In production, the paired asset reaches each network through Relay. A Pair Family maps one economic unit to each network’s approved asset, for example USDC on Base and Solana and USDG on Robinhood Chain. Production Pair Family routes remain to be confirmed, and neither production Pair Families nor universal cross-chain stablecoin routing is presented as delivered. No bridge, issuer representation or tokenised stock is approved by this whitepaper.

07 / THE ECONOMIC ENGINEACTIVITY WITH A PURPOSE

Trading funds
what comes next.

A Genesis fee and a canonical trading fee support the protocol, the people behind a project, permanent liquidity and shared market-balancing capital.

CANONICAL TRADING FEE1.00%

One fee, with defined jobs.

Protocol treasury0.30%
Project Rewards0.30%
Permanent liquidity0.20%
Community LP rewards0.10%
Market Growth0.10%

After graduation, 0.20% strengthens the official pools and stays locked forever, 0.10% rewards community liquidity providers and 0.10% funds Market Growth.

A CRITICAL DISTINCTION

Liquidity strengthening deepens the existing official pools and is locked forever. Market Growth is recoverable capital for the planned balancer, which trades only when the expected net profit is positive. Neither is a promise of returns or a price peg.

The current model, subject to final validation before mainnet. External network, transport and venue costs may apply separately. Project Rewards can be split among the controller, named recipients and holder cashback.

The paired asset pays the fee.

Genesis trades carry 1.2%: 0.6% to a separate liquidity fund used only after graduation, 0.3% to the protocol treasury and 0.3% to Project Rewards. After graduation, canonical buys and sells in every market carry 1%. The fee is collected from the local paired-asset side. Ordinary fee and reward settlement does not accumulate project tokens and sell them later to fund payouts.

Permanent liquidity and community LP rewards both serve the official pools. The first adds protocol-owned positions that are locked forever; the second rewards eligible community liquidity providers, whose positions stay separate from SPRAWL’s locked ones. The treasury and Project Rewards shares are the same before and after graduation.

The five shares have different purposes and custody rules. In particular, shared market-balancing capital is not treasury revenue, a payout promise or liquidity automatically added to a pool. Network gas, venue and transport costs can apply separately. Wallet transfers are not subjected to the canonical trading fee merely because the asset moves between wallets.

08 / PROJECT REWARDSSPRAWL / WHITEPAPER

Built for the people
behind the project.

Creators can direct Project Rewards to their own wallet, named recipients and eligible holders. The split belongs to the project, with enforceable policy rules.

ILLUSTRATIVE CANONICAL TRADE$1,000

Trade value

PROJECT REWARDS$3.00

Before any payout-path costs

Example allocation

40% Controller $1.20

60% Holder cashback $1.80

Example only. The creator chooses the reward split; 40/60 is not a required allocation, yield or return. This is a split of Project Rewards, not a distribution of token supply.

A policy that can be understood.

Reward percentages must total 100%. Each named recipient uses one payout wallet, with supported settlement routes determining how an entitlement reaches that wallet. A creator launching with Solana as HOME names an EVM wallet at creation for rewards earned on the EVM networks. Automatic payouts are the intended settlement experience; value may remain queued when route availability, float liquidity or economic payout minimums prevent immediate delivery.

The initial policy is committed at creation. The protocol permits one optional amendment during each period of control, subject to notice and its policy rules. Previously accrued liabilities retain their original entitlement. A project that commits 100% to holder cashback makes that choice irreversible, including after a change of control.

Cashback follows eligible ownership.

Global Holder Cashback is based on eligible token balance over time across chains, with continuity across authenticated transport. It is not a share calculated independently against each chain’s local supply. Protocol custody and other excluded balances must not earn rewards intended for holders.

As a simple weighting example, 100 eligible tokens held for two equal periods contribute the same balance-time as 200 held for one. Actual payouts also depend on the total eligible weight, accrued rewards, exclusion rules and settlement costs. This is activity-funded distribution, not a fixed APY.

Control can change without changing the asset.

The controller manages the permissions the protocol grants to project control. An ordinary transfer of control and a Community Takeover are distinct processes. A CTO follows the approved governance procedure; it is not an unrestricted right for any wallet to replace the creator.

Neither process creates a new supply, changes the immutable pairing or changes the selected networks. Readers should be able to inspect the current controller, applicable reward policy and effective changes without needing to understand internal accounting terminology. Automatic payouts and holder cashback are not yet enabled on testnet.

09 / MARKET BALANCINGSPRAWL / WHITEPAPER

A spread is a signal.
Profit is the test.

Market Growth funds the Market Growth balancer, the cross-chain arbitrage engine SPRAWL plans to build. It acts on a price difference only when the whole cycle is expected to be profitable after every cost.

PLANNED / TRADE CONDITION

Expected sale proceeds > Purchase cost
+ fees + gas + transport + impact + risk margin

01

Quote both markets

Use executable quotes on both networks, never displayed prices or a remote observation alone.

02

Buy where it is cheaper

Buy on the cheaper canonical market only while the complete cycle is expected to stay profitable.

03

Sell where it is dearer

Sell on the more expensive market and return the proceeds, and any profit, to the Market Growth float.

Prices point. Execution decides.

A displayed difference between two chains is not a guaranteed profit. Both canonical trading fees, price impact, gas, transport, slippage and time affect the result. A remote observation can suggest where to look; it does not authorise a purchase at an obsolete price.

The balancer holds no pre-positioned SPRAWL-owned token inventory. It may buy and sell tokens within a profitable cycle, but it never sells permanently committed liquidity. If a cycle no longer satisfies the cost and risk limits, the balancer does not start it: there is no deliberate loss-making price support.

Strictly scoped capital.

Market Growth receives 0.10% of every canonical trade after graduation and forms a recoverable float, pooled per token across the relevant networks. The market that generated a contribution is recorded for attribution; the contribution is not an isolated investment account belonging to that project.

The float is separate from permanent liquidity, Project Rewards, the Genesis liquidity fund and transport custody. Balancing does not permit discretionary liquidation of those balances. Realised profits compound in the float under strict loss and exposure limits; open positions still carry risk, so limits and observability are part of the design.

The Market Growth balancer is planned. An earlier balancing design was exercised on testnet; that historical demonstration is not proof of a production or four-network service. The balancer does not peg prices, guarantee convergence, support a failing token or promise returns to holders.

Balancing capital is not pool depth.

Market Growth starts from trading fees. Its contributions are shared by the protocol’s network-local float vaults, pooled per token; project attribution is analytics, not a ring-fenced entitlement. It does not enter permanent liquidity positions and is not treasury revenue.

Pool depth grows through the separate liquidity-strengthening programme: the Genesis liquidity fund and 0.20% of trading after graduation, added to the official pools and locked forever. Neither a new narrative nor an API can change the custody rules that keep these balances apart.

10 / SECURITY & ASSUMPTIONSSPRAWL / WHITEPAPER

Trust should be
specific.

Security comes from explicit boundaries, reproducible evidence and conservative failure behaviour. “Cross-chain” is a set of dependencies, not a security guarantee.

Conserve

Reconcile normalised supply, backing, in-flight obligations and dust.

Authenticate

Bind messages, pools, releases and receipts to authorised counterparts.

Constrain

Apply minting caps, opening windows, spend bounds and replay protection.

Observe

Track pending work, failed conditions, custody balances and finalised events.

Different components, different powers.

Immutable EVM deployments do not make every dependency immutable. Release registries, parameter permissions, chain infrastructure and transport administration still matter. Solana program upgrade authorities are a separate trust boundary. The testnet permits a deployment arrangement that must not silently become the mainnet authority model.

Two of three SPRAWL signers must approve each opening, and only after the Genesis freeze and funding are observed on every selected network. They choose only the opening time and confirmation profile, inside limits each network enforces. They cannot move funds, set prices or skip a network. Production requires the signers to run on independent hosts.

LayerZero messages are verified by independent DVNs. Minting caps limit what any single network can issue. Each opening waits a configured confirmation depth on HOME. A guardian can hold a market before it opens.

Keepers, the coordinator and indexers are operational services. A stopped keeper or coordinator can delay an opening; a lagging indexer can show stale state. None of them can bypass authenticated contract checks. Wallet signatures authorise user transactions, while protocol capital follows its own narrowly scoped contract rules.

Dependencies readers should understand
BoundaryWhy it mattersRequired discipline
Transport & destinationDelayed delivery, compromised counterparties or an invalid binding can threaten availability or backing.DVN verification, minting caps, signed-opening checks and fresh-price recovery.
Opening signersA compromised signer pair could choose a poor opening time; an unavailable pair delays an opening.On-chain lead and window limits, one opening per network, a guardian hold and independent production hosts.
Paired assets & venuesIssuer controls, depegs, market manipulation and thin liquidity affect execution.Approved representations, usable routes, pricing checks and venue-specific validation.
Permissions & upgradesA privileged change can alter the assumptions under which funds were committed.Publish the authority matrix, enforce release rules and resolve production upgrade policy.
OperationsRPC outages, reorgs, unavailable keepers and stale observations can delay or misreport progress.Confirmation depth before signing, several RPC providers per network, monitoring, retries and reconciliation.

Reviews are evidence, not immunity.

The recorded review sequence provides specific evidence. The LayerZero transport had targeted security reviews of its EVM and Solana changes and an independent check before its first testnet deployment, approved with conditions. The graduation path was examined in an adversarial review before its design was chosen, and each defect it found is covered by regression tests on the EVM contracts and the Solana program.

The reviews are independent agent reviews and follow-up passes, not a formal external audit. We do not equate a closed finding with a production-safety certification.

The distinction matters: fixes can remove a specific defect while recovery, upgrade authority, signer hosting and production transport still require explicit treatment.

Residual risks and limits

Users can lose value through price movement, low liquidity, slippage, MEV, compromised wallet credentials, smart-contract defects, transport failures, issuer restrictions or chain failures. Initial pool positions are permanently locked: on the EVM networks a locker holds them with no removal path, and on Solana all LP sits in Raydium’s lock with its fee rights kept; both were read from chain on testnet. A permanent liquidity position still does not imply a stable price or sufficient exit depth.

Cross-chain actions are asynchronous. Timeout, pause and recovery behaviour must preserve liabilities already created. An automatic system can wait indefinitely when safe conditions are unavailable. Public testnet assets and valuations are test data and do not carry mainnet economic value.

A production specification must tie its security claims to exact release artefacts, deployed addresses, authority configurations, review scope and known unresolved findings. This edition is not that specification.

DOCUMENTED REVIEW SEQUENCE / OCTOBER 2026
01

Find the failure.

Reviews of the graduation path found real defects: a balance donated before the freeze could make a network look ready or block a cancellation, and paired asset beyond what an opening used had no exit.

02

Verify the correction.

Both are fixed in the EVM contracts and in the Solana program, each with regression tests, before the live testnet graduations.

03

Keep the limits visible.

Recovery when HOME misses the opening is built, not deployed. Hosted unattended operation is not running yet. Production signer hosting, confirmation depths and verifier sets are not chosen. Production upgrade authority remains open.

These are reviews of development artefacts, not proof of a production deployment.

11 / BUILD ON SPRAWLSPRAWL / WHITEPAPER

Your experience.
A shared foundation.

A launchpad is the first product. The wider direction is open-source infrastructure, SDKs and APIs that developers, projects and other launchpads can build on.

Architectural concept: an open ivory workshop built on a shared structural foundation
Different experiences. Shared infrastructure. Conceptual artwork.

Start with a concrete integration.

A developer can explore asset discovery, local-market views, launch progress, project rewards and cross-chain analytics through the protocol’s typed interfaces and indexed state. A project can design its own community experience around those primitives rather than treating its token as a ticker detached from its lifecycle.

Possible applications include specialist launch interfaces, trading dashboards, destination alerts, portfolio views and tools that explain how a project’s activity funds its liquidity. These are integration opportunities, not claims that every example is already deployed or available as a self-service product.

01 / DISCOVERGET /v1/capabilities

Check the environment and enabled chain-specific capabilities before offering an action.

02 / READGET /v1/assets/:assetId

Resolve the global asset and its current data through the typed asset interface.

03 / INTEGRATEValidate. Simulate. Sign.

Bind executable flows to the approved release and the user’s selected wallet and network.

Supported from prototype to launch.

SPRAWL can provide technical guidance, integration support, direct coordination with the team, co-marketing and launch support. The useful starting point is a defined use case, required networks, custody assumptions and the capabilities it needs.

The current codebase contains typed schemas and client interfaces; this whitepaper does not announce a production-ready public SDK, unrestricted API SLA or a grants programme. Access, scope and launch arrangements are agreed with the team. Support does not waive protocol safety checks or imply endorsement of every asset launched on the platform.

Discuss an integration team@sprawl.fun

PLANNED / OPEN-SOURCE INFRASTRUCTURE

Build the experience.
Connect to the lifecycle.

The goal is reusable launch and market infrastructure: documented interfaces, release-aware client libraries and integration examples that let teams create their own products around SPRAWL’s protocol.

Typed schemas, clients and hosted API paths already exist in the project. Public source releases, an externally supported SDK, licence terms, versioning commitments and self-service access are not announced as available in this edition. Source publication and developer tooling will be introduced through explicit releases, with supported capabilities and trust assumptions documented.

12 / THE BUILDTESTNET EVIDENCE / NOVEMBER 2026

An ambitious idea.
A tangible foundation.

From architecture to contracts.
From contracts to markets opening together.

1,423Automated tests passing
4Networks proven as HOME
About these figures

The figures in this chapter are the SPRAWL team’s own counts, recomputed on 1 November 2026 from the repository’s test suites and its recorded live runs. They are not live telemetry and have not been independently verified. How they are counted is set out below.

The four networks are Base Sepolia, Robinhood Chain testnet, BNB Chain testnet and Solana devnet. Each has served as HOME for a Genesis and a coordinated graduation onto all four networks, with a real swap on every network.

How the figures are counted

The test count was recomputed on 1 November 2026 on the Base-HOME development code, where 1,423 automated tests pass and none fail: 567 Foundry tests for the transport and graduation contracts, 19 for the Genesis curve, 670 TypeScript tests for the transport and graduation services, 110 Solana client tests and 57 Rust program tests. A further 202 are skipped: fork tests that need a live network endpoint, and Solana simulator tests that do not run on the counting machine.

The Robinhood-, BNB- and Solana-HOME code builds on the same base and adds its own tests: 574, 602 and 603 Foundry tests respectively, all passing, plus 38 Rust tests for Solana’s native HOME program. Their wider TypeScript suites include a few failing tests in older deployment-review tooling and in work in progress; those are recorded with the counts. Branches share most of their code, so their figures are not added together.

Live runs are counted from each HOME’s recorded evidence, to 1 November 2026. A run is clean only when every selected market opened at the shared time with a real swap on every network and no network was late or recovered. Times are read from block timestamps on chain.

Live graduations on testnet, by HOME, 29 October – 1 November 2026
HOMEGraduationsClean openingsFinal buy → first trade everywhere
Base20 four-network
plus one two- and one three-network		16 of 20
2 of 2		median 29.3 s
range 22.4–59.5 s; 25.5 s and 24.9 s
Robinhood2 four-network2 of 2about 30–34 s
33.9 s and 29.5 s
BNB Chain3 four-network2 of 327.5 s
the run with valid timing
Solana7 two-, three- and four-network6 of 748 s
the unattended four-network run

Testnet only, with the stand-ins listed in chapter 13. Failed runs are counted: a late or recovered network, or a run where nothing opened, is not a clean opening. Attempts stopped by a set-up error before graduation are excluded.

13 / RELEASE STATUS & THE ROAD AHEADSPRAWL / WHITEPAPER

Prove the journey.
Then expand access.

SPRAWL runs on public testnets. Mainnet readiness requires working integrations, explicit trust decisions and evidence from the complete lifecycle.

Proof status by HOME network, 1 November 2026
CapabilityBaseBNBRobinhoodSolana
Genesis + graduation as HOMEDemonstratedDemonstratedDemonstratedDemonstrated
Two- and three-network graduationDemonstratedNot runNot runDemonstrated
Permanent LP read from chainDemonstratedDemonstratedDemonstratedDemonstrated
Holder transfers, both waysDemonstratedDemonstratedDemonstratedDemonstrated
Graduation timing29.3 s median27.5 s29.5–33.9 s48 s
Message verificationLayerZero DVNsTestnet onlyLayerZero DVNsLayerZero DVNs
Hosted, unattendedIn developmentIn developmentIn developmentIn development

Source: the recorded live runs on each HOME network’s testnet suite, to 1 November 2026. Rows describe each network as HOME, except permanent LP and holder transfers, which cover each network in any role. All networks shown are testnets. The hosted testnet app, private to the team since 14 October 2026, still runs the earlier release; deployed contracts alone do not enable a product capability.

TESTNET ONLY

Stand-ins, named.

The testnet proofs use the stand-ins below. None of them is a production component, and none is presented as production proof.

Relay solvers
A mock Relay depository and a SPRAWL filler deliver the paired asset after graduation.
Stablecoins
SPRAWL’s own test dollars stand in for each network’s issuer assets.
Raydium opening
A SPRAWL testnet pool-creator opens the Solana pools at the shared time.
BNB Chain venue
SPRAWL’s own testnet instance of Uniswap v4.
BNB Chain messages
A SPRAWL testnet-only verifier, because LayerZero’s BNB-testnet verifiers no longer verify them.
Opening signers
The three signers run on one machine; production requires independent hosts.
TESTNET

Demonstrate the core lifecycle.

Genesis and coordinated graduation with every network as HOME, permanent liquidity and two-way token transfers are demonstrated on testnet, through contract calls and SPRAWL’s own tooling. The hosted testnet app, public from 10 October 2026 and limited to the team since 14 October 2026, still runs the earlier release.

IN DEVELOPMENT

Complete the four-network V1.

Run graduation unattended on hosted services, and finish recovery for a late HOME. Connect Create, Auto Buy and Auto Sell, liquidity strengthening and the Market Growth balancer to the new path. Promote each capability only after implementation, tests, deployment and hosted-product proof.

PRE-MAINNET GATES

Resolve production assumptions.

Complete final validation of the Genesis economics. Choose production confirmation depths, verifier sets and signer hosting. Confirm the Relay and Raydium production paths, production Pair Family routes and Solana upgrade authority. Freeze the production scope, then complete external audit and release-specific verification. None is certified complete here.

FUTURE ROADMAP

Launch a native $SPRAWL token.

There is no $SPRAWL platform token in V1. SPRAWL will launch its own native token later, as part of its future roadmap. The launch method, timing, utility, allocation, economics and tokenomics are not finalised.

Milestones are conditions, not dates.

Mainnet readiness is not inferred from a high test count, one successful bridge message or a deployed contract address. The whole supported journey must work with the intended representations, real transport, operational monitoring and production permissions.

This roadmap describes the order of proof. Dates depend on completion of those gates. The whitepaper will be versioned as the release scope and supported capabilities change, so a future production edition can cite the exact configuration it describes.

14 / THE FUTURE $SPRAWL TOKENPRODUCT FIRST. TOKEN AFTER.

A native token.
In the future.

There is no $SPRAWL platform token in V1. SPRAWL will launch its own native token, $SPRAWL, later, as part of its future roadmap.

In V1
No $SPRAWL platform token
Launch date
To be announced
Token utility
To be confirmed
Allocation, economics and tokenomics
Not finalised

Not the trading fee.
Not a creator’s token.

The 1.2% Genesis fee, the 1.00% canonical trading fee and their allocations (chapter 7) neither depend on nor reward a platform token. Tokens launched by creators on SPRAWL are their own assets, not $SPRAWL.

The launch method, timing, utility, allocation, economics and tokenomics are not finalised.

A statement of intent, not an offer of tokens. This edition specifies no token features or holder returns and commits to no launch date.

15 / REFERENCES & READING GUIDESPRAWL / WHITEPAPER

The detail
behind the claims.

A useful whitepaper should be traceable. External market context, protocol design and development evidence have different sources.

01

State of Crypto 2025

a16z crypto · 22 October 2025. Source for the estimated 40–70 million active-user range; an estimate of people, not monthly active addresses.

02

2025 Annual Crypto Industry Report

CoinGecko. Source for year-end 2025 stablecoin market capitalisation of $311 billion and 48.9% annual growth.

03

Omnichain Fungible Token standard

LayerZero documentation. Background for lock / mint and burn / release transport, shared decimals and message verification by DVNs. Does not certify SPRAWL’s integration.

04

SPRAWL protocol records

The project’s own design, economics and architecture records, decisions and review reports, as of November 2026. They are internal working records and are not published with this edition. The proof-status table in chapter 13 is a dated view of recorded testnet runs; development code is not presented as a production deployment.

05

SPRAWL build figures

The team’s own counts of automated tests and live testnet graduations, recomputed on 1 November 2026, with the method given in chapter 12. They are counts of development work on testnets, not independently verified and not live telemetry.

06

Relay

Relay documentation. Background for cross-chain deposits filled by solvers, used for paired-asset funding and planned cross-chain trading. Does not certify SPRAWL’s integration.

07

Uniswap v4

Uniswap documentation. Background for pools with hooks, the venue on Base, Robinhood Chain and BNB Chain. Does not certify SPRAWL’s integration.

08

Raydium

Raydium documentation. Background for constant-product pools, opening times and locked liquidity on Solana. Does not certify SPRAWL’s integration.

A short translation guide.

Canonical
The protocol-recognised asset, market or transport path, rather than an arbitrary copy.
HOME
The network where Genesis runs and where the backing of tokens on other networks is held.
Genesis / graduation
The bonding-curve sale / the coordinated opening of every selected market at one shared time.
Sprawl
The same asset’s canonical market, opened on another selected network.
Pair Family
The economic asset a token is paired with, expressed through approved local representations.
Market Growth / float
The planned cross-chain balancer / the recoverable capital it trades with, kept apart from permanent liquidity.
Controller period
The time under one project controller; called an epoch in internal policy accounting.
Global supply
Economic units across home, destinations and transit, without counting backing and its representation twice.
NOVEMBER 2026 EDITION / STATUS

This whitepaper describes SPRAWL’s protocol design and its state of development as of 1 November 2026. SPRAWL runs on public testnets only. This is not a final production specification: availability is qualified by chapter 13, the Genesis economics are the current model subject to final validation, and the contracts have had no formal external audit.

This document is not an offer of tokens. There is no $SPRAWL platform token in V1; the launch timing, utility, allocation, economics and tokenomics of the future $SPRAWL token are not finalised. No claim of guaranteed returns or risk-free liquidity is made.

THE SPRAWL WHITEPAPER

A new chapter
for token launches.

15 chapters. Read the core story, explore the diagrams and open the technical notes for implementation detail.
SEARCH THE WHITEPAPER

Search the full whitepaper — 15 chapters.