BrawlBond Protocol
Operational documentation for the double-or-nothing game platform
BrawlBond turns price prediction into a fast, social, Base-native game loop.
This documentation covers the core system: room-based gameplay, escrow and settlement patterns, player modes, token utility, and the architecture required to run a transparent on-chain gaming product.
Core mechanic
Double-or-nothing with transparent settlement
Primary network
Base for low-cost, frequent rounds
Product scope
Crypto prediction, skill arcade, and LP participation
Foundation
What BrawlBond is
BrawlBond is a room-based on-chain game platform built around short-horizon prediction and skill-based rounds. The product is intentionally easy to understand: players enter a room, post a stake, commit to a direction or score attempt, and settle against explicit rules.
Simple decision surface
Players only need to understand the market, direction, threshold, and timer.
Multiplayer by design
Rooms, ranks, guild loops, and duel modes make social presence part of the product.
Clear settlement model
Escrow and payout logic are designed to be auditable instead of opaque or discretionary.
Getting Started
How players use the protocol
The first-time user flow should be obvious. A player connects, joins a room, commits a stake, and waits for deterministic settlement under the room configuration.
Connect a Base wallet
Use a self-custodial wallet on Base. Players fund with USDC or ETH and keep direct control over their assets.
Join a prediction room
Enter a market room such as BTC 5H or ETH 1H, then review the threshold, timer, and active liquidity mode.
Commit a direction
Pick UP or DOWN, lock your stake, and let the position settle against the game rules for that room.
Settle and continue
Winning rounds return 2x on supported game types. Players can keep playing, switch rooms, or withdraw at any time.
Gameplay
Game families and resolution logic
BrawlBond supports more than one game family. The important distinction is not the visual layer, but what determines the result: an oracle or player performance.
Oracle-settled prediction rooms
Crypto rooms are resolved by reference price data and room parameters. A player picks UP or DOWN and must clear the configured threshold inside the active round window.
- Direction Call for short-horizon market moves
- Threshold Hit for touch-based targets
- Streak and survival variants with compounding tension
- Higher-or-Lower style formats for simplified repetitive play
Settlement rule
win_if(
direction === "UP" && r > threshold
direction === "DOWN" && r < -threshold
)
where r = ln(P_T / P_0)
UP Caller
Blue Nova
Represents momentum calls, fast room entry, and streak-based player behavior in docs examples.
DOWN Rival
Red Rift
Represents counter-direction pressure, duel framing, and player-versus-player examples.
LP Strategist
Vault Captain
Represents vaults, protocol bankrolls, LP participation, and long-term economy references.
Modes
Who provides liquidity in each mode
Every room needs a counterparty. The mode system explains where liquidity comes from and what risk the protocol carries.
1P vs House
The protocol bankroll or LP vault backs the round. The edge comes from the threshold or the calibrated target.
2P vs Player
Two players post equal stakes into one pot. The winner takes the pool minus a transparent protocol rake.
4P Team Battle
Two-versus-two peer-funded team mode for guilds and ranked squads. Same escrow pattern, expanded coordination layer.
Architecture
Reference architecture for the docs site
The documentation structure can map directly to the protocol stack. The frontend explains the system, while contracts and services execute the game logic underneath.
The docs UI should explain product rules, risks, and operating concepts without feeling like a landing page. This implementation uses a persistent sidebar, dense sectioning, and structured references closer to GitBook than a marketing site.
Suggested docs map
- Protocol overview and rule definitions
- Supported game families and mode matrix
- Settlement, escrow, and oracle references
- Token utility and LP participation
- Treasury controls, risk, and fee policy
- Roadmap, governance, and disclosure notes
Economy
Token utility, fees, and treasury alignment
A docs surface should explain where value accrues and where risk lives. This section frames BRAWL and protocol revenue in operational terms rather than hype.
BRAWL utility
- Governance and directional product incentives
- Seasonal rewards, rank progression, and participation loops
- LP alignment through vault access and protocol-native incentives
- Potential fee benefits, gated cosmetics, and ecosystem utility extensions
Revenue model
- House edge in protocol-backed 1P rooms
- Rake in peer-funded 2P and future 4P rooms
- Operational withdrawal or service fees where disclosed
- No dependence on hidden spread manipulation in the docs narrative
FAQ
Questions the docs should answer quickly
A GitBook-style product docs experience works best when common questions are answered in place instead of being buried in long prose.
What makes BrawlBond different from a normal prediction market?
BrawlBond compresses the decision surface into a fast, room-based game loop. It is not an order book market. It is a rules-based double-or-nothing arcade built on Base.
How are crypto rounds settled?
Crypto rounds settle against a public oracle and room parameters such as threshold, direction, and expiry window.
Does the protocol always take the other side?
No. In 2P and future 4P modes, players fund the pot directly. The protocol mainly earns a rake or operational fees there.
Where does BRAWL fit?
BRAWL supports governance, incentives, seasonal participation, LP alignment, and long-term ecosystem utility across the product.