BATTLE.BAND

BATTLE.BAND does not run its own market. Tokens launch and trade on an existing launchpad, on bonding curves we did not write and do not control. We own the layer above it: which song a token belongs to, the one token per song rule, the chart, discovery, and the fee split.

That boundary is deliberate. The money sits in audited launchpad contracts rather than in something we wrote last month.

The song to token mapping, write once. It records which token belongs to a song and who coined it, and it refuses a second write for the same song. Only allowlisted launchers may write to it.

Its SongCoined event carries the unhashed song id, which is how the site reads the entire chart from the chain with a single log query and no indexer.

One clone per song, created before the token exists so that fees have somewhere to land from the very first trade. It is set as the token's creator fee recipient at launch.

collect() sweeps the curve, claims the escrow, and splits the proceeds 50/50 between the coiner and the treasury. It is permissionless: anyone may call it, and only those two addresses can receive from it.

Does the whole launch in one transaction: clone the splitter, launch the token with that splitter as fee recipient, write the registry, then bind the curve to the splitter.

Because it is atomic, there is no state where a song is registered but its fees are unrouted, or where a token exists that the chart cannot see.

Every figure on the site is read from the chain at page load. Coined songs come from the registry's logs; each song's price, progress and history come from its own curve.

Money raised excludes the curve's virtual seed reserve, so a brand new token reads as near zero rather than as already part way to its target.

Every contract below is deployed and verified, and every claim on this site can be checked against them. The fee split in particular is worth checking: read the splitter for a song and confirm the two recipients and the fixed halves for yourself.