BULK Builder Codes: How to Earn Fees Building on BULK Exchange

BULK Builder Codes let anyone with an idea build on top of BULK Exchange and get paid for the order flow they bring. No BD call, no revenue-share negotiation, no API key gatekeeping — a developer attaches a fee to the orders they route, the user approves it once, and it settles automatically on every trade after that.

This guide covers how the mechanics work, what you can build, and where to start.

What a Builder Code Actually Is

BULK Exchange is a single deterministic order book with one execution engine underneath it. Historically, “building on an exchange” meant either running your own infrastructure or negotiating a private revenue-share deal with the exchange’s BD team.

Builder Codes remove that step. A builder code is an identifier attached to an order that tells BULK’s fee logic to route an extra, user-approved fee to the builder’s address on top of the user’s standard BULK fee tier.

The mechanism, in three parts:

1. User approves once. A user signs an approval for a specific builder code and a specific fee, capped at a maximum the user controls.
2. Builder attaches the code to routed orders. Every order the builder’s product sends to BULK carries that code.
3. Fee settles automatically. On top of the user’s existing BULK fee tier, on every fill, with no manual invoicing or reconciliation.

The fee is visible in the signed order payload, capped by the user’s approval, and revocable by the user at any time — it isn’t a hidden spread or a private arrangement, it’s a term the user explicitly signed off on.

No Internalized Flow

The detail that matters most for anyone evaluating whether to build on BULK versus a venue with a private order-flow deal: every order routed through a builder code hits the same order book and receives the same BULK Best Bid and Offer as every other order on the network.

There’s no internalized flow, no private market makers sitting in front of builder-routed orders, and no execution games. A builder earns a fee for the distribution they bring — the acquisition, the UI, the community — not by degrading the price the user actually gets. That’s a meaningfully different model from payment-for-order-flow arrangements common elsewhere, where the entity routing the order and the entity filling it can be the same counterparty with an incentive to worsen execution.

What You Can Build

BULK’s own framing is: if it places an order, you can build it. Categories BULK has flagged explicitly:

Custom frontends. A different take on the trading UI — a pro terminal, a mobile-first simplified experience, or a regional frontend in a specific community’s language. The builder owns the product and the user relationship; BULK handles matching, margin, and settlement underneath.

Trading bots and automation. Copy trading, grid bots, DCA tools, signal execution. A user approves a bot’s code once, and every order the bot places routes through the builder’s code from then on.

Telegram and social trading. Slash-command trading (/long_SOL_5x) without leaving a chat client, tap-to-trade buttons under calls in a trading community, group-scoped leaderboards with verifiable onchain track records. Every copied trade routes through the builder’s code.

Gamified trading. One-tap directional markets (“up or down by Friday”), trading leagues with seasons and divisions, head-to-head PnL duels, achievement systems funded by the fee flow the activity generates.

Aggregators and portfolio apps. Any dashboard that already shows a user their positions can add execution and monetize it directly instead of just displaying data.

Vaults and strategy products. Structured products, managed strategies, one-click hedging tools — anything trading on a user’s behalf can route through BULK and capture the fee on that flow.

Wallets. Perps natively inside a wallet’s own interface, with no redirect out to a separate exchange UI — users trade where their keys already live.

Relevant if you’re already using the BULK client SDK: Builder Codes plug into the same order-submission path the SDK exposes, so a bot or integration built against the SDK today is close to builder-code-ready.

Getting Started

Builder Codes are live now on staging, and ship live on BULK Mainnet from day one.

• Docs and payload formats: docs.bulk.trade/bulk-exchange/builder-codes
• SDK: github.com/Bulk-trade/bulk-client, release v0.1.2

The practical starting point is the same SDK used for any other integration — see the BULK SDK guide for install and first-connection steps — with a builder code attached to the orders your product submits.

Frequently Asked Questions

What are BULK Builder Codes? An onchain fee-attribution system letting any developer route orders to BULK Exchange and earn a transparent, user-approved fee on that flow — no BD call, revenue-share negotiation, or API gatekeeping required.

How do Builder Codes pay out? Users approve a builder’s code and fee once. The fee then settles automatically on top of the user’s standard BULK fee tier, on every order routed through that code — visible in the signed payload, capped, and revocable.

Does a Builder Code change my execution? No. Every order still hits the same order book and gets the same BULK Best Bid and Offer as any other order. Builders monetize distribution, not execution quality.

What can I build? Custom frontends, trading bots, Telegram/social trading products, gamified trading, aggregator dashboards, vaults and structured products, and wallet-native perps — anything that places an order.

Related:

• BULK Exchange SDK Guide — install, connect, and place your first order
• BULK Exchange Trading Guide — the full feature walkthrough
• Portfolio Margin Explained — the risk engine your integration’s orders settle against
• What is BULK Exchange?

Source: BULK Exchange — Introducing Builder Codes, July 13, 2026. Docs: docs.bulk.trade/bulk-exchange/builder-codes.

Trade on BULK Exchange → early.bulk.trade