Builder programme

Every trade on Montra pays the protocol $0.40 of each $100 traded, on every fee tier. A builder (a launch site, a bot, an agent, a wallet, a terminal's launch button) that brings new launches earns a share of that fee on the tokens launched through it, worked out from on-chain data and paid from Montra's treasury each week. Nothing in the contracts changes: a token, its pool and its fees work the same whether or not a launch is attributed.

A builder registers a code with the wallet that will be paid, by signing the programme's terms with it, on the site; signing costs no gas and moves no funds. Credit starts at once. Builders with a working product and users are approved and paid; until then what they earn is held, not lost. Join the programme, or read the programme's page first.

• Launch share: 25% of the protocol's fee on every trade in a token launched with your code, for 90 days from its launch.
• Through any interface: the share is of the fee each trade of the token paid, through whatever interface the trade was made, except the trades under what is not paid; the builder is paid for bringing the token, never for trading it.
• Never on volume alone: every payout is a share of a fee a trader actually paid, and trading volume itself earns nothing.

One form and one signature. What it asks for:

Your code is 3 to 32 characters: lowercase letters, digits and dashes, starting with a letter or a digit (^[a-z0-9][a-z0-9-]{2,31}$). It can't be changed, but a builder can hold up to five. The programme's own words, the ecosystem's names and anything that reads as the launchpad's are reserved.

Put your code on the launch transaction as an ERC-8021 suffix: the code's ASCII, its length in a byte, the schema (00) and the 16-byte marker 0x8021…8021, appended after the factory call's calldata. The factory never reads it, so the launch is exactly the same; Montra's indexer reads it from the transaction.

Building the launch itself, every field of it, is under Launch a token. The guide has these lines, and a builder's desk has them with its own code in them.

// "my-terminal" in ASCII, its length (11 bytes), schema 0, then the ERC-8021 marker
const dataSuffix = "0x6d792d7465726d696e616c" + "0b" + "00" + "80218021802180218021802180218021";

const { request } = await client.simulateContract({
  address: factory, abi: factoryAbi, functionName: "launch", args: [params],
  account, value, dataSuffix,
});
// then send `request` from your wallet client, as any write: the suffix goes with it

const tx = await factory.launch.populateTransaction(params, { value });
tx.data = tx.data + dataSuffix.slice(2); // after everything the factory reads
await signer.sendTransaction(tx);

• A code counts only on launches made after it was registered, and one builder is credited for each launch: a launcher contract registered to you that sent it, otherwise the first registered code in the calldata, read from its start.
• A smart wallet that wraps the call carries the factory's calldata, suffix and all, inside its own, and the code is still found. A transaction that launches several tokens is credited only through a launcher contract.
• Montra's own site tags the launches it sends with a code of its own: those are Montra's, and never paid.

A launch your registered contract sends is yours, with or without a suffix. The factory takes whoever calls launch as the token's creator, salts its address with it and sends the first buy to it, so through your contract the creator is your contract: name your user in feeRecipients and pass the first buy on in the same call. Register the contract on your desk; it is proven yours by its deployment transaction from your wallet or its owner() being your wallet, or checked by hand.

A launch whose user is you, or whose fees pay you, earns nothing; a slot of your own in the creator's fee split, at most 20%, is your own fee and allowed.

Everything a trading integration needs is free: the docs, the ABIs, the API and, once it is published, the SDK. Trading volume itself isn't rewarded: a product that only trades, in any volume, earns nothing under the programme. Quoting and trading a pool are in Build on Montra, the tokens, wallets and live trades in the Public API, and every address and ABI under Contracts.

Each statement lists every pool a builder earned in, the trades counted, the protocol's part, the share, the rate and the cap, and carries the SHA-256 of its document. Every figure is from public data: the hook's FeeAccrued events for each pool, the launch transaction's calldata and the vault's HubSold. Payouts are plain HYPE transfers from the treasury multisig in one batch a week; each shows on the builder's desk with its transaction. A builder may object to a statement within 7 days.

The site's builders page has the programme and the directory of approved builders. A builder's desk, found by its wallet, gathers what it needs: its code in lines it can paste, a check of any launch transaction, the tokens credited to it, its earnings week by week, its payouts and what the next one will be, files of all three, and its profile, contacts, codes and contracts, each change a signature of its own.

Each approved builder has a public page, /builders/<code>, made to be posted: the tokens launched through it, what they have traded and what it has been paid, with a share card drawn from the same figures.

The terms are version 2026-11-01; changes that lower a share or a cap apply from a week that starts at least 7 days after they are announced.