It is Bitcoin, on an EVM chain.
A reserve denominated in wrapped Bitcoin does not move with the chain's own gas token. That is the whole reason for pairing against it rather than against ETH.
Live on Robinhood Chain · launching through pons
Launch through the live pons launcher on Robinhood Chain, with one field changed: the creator fee wallet points at the foundry instead of a personal wallet. One transaction, signed by you.
Launchpad
| Token | Pair | Opening buy | Contract address | Launched | Trade |
|---|---|---|---|---|---|
|
No launches yet No launch has routed its fees to the foundry yet. The first one takes this row. Launch the first one |
|||||
Launched with fees routed to the foundry.
Opened once a launch graduates and is paired.
The sweep contract is not deployed yet.
Nothing deposited, nothing withdrawn.
The reserve asset
pons quotes every launch in ETH. What the foundry adds is the second step: the creator fees that launch earns are meant to end up as wBTC-paired liquidity, not as income.
A reserve denominated in wrapped Bitcoin does not move with the chain's own gas token. That is the whole reason for pairing against it rather than against ETH.
The launch sets the creator fee wallet in the same transaction, so the fee stream is captured from the very first trade rather than reassigned later.
The contract that converts collected fees into permanent wBTC liquidity is still being written. When it ships it will have no withdraw path at all.
Mechanism
pons pays the creator a share of trading fees. The launch sets that wallet to the foundry, in the same call that deploys the token.
On a timer, the collected ETH is cut in two: one half buys the token on the open market, the other buys wBTC.
Both legs are deposited together and never withdrawn. Every trade that pays a fee makes the floor beneath the token deeper.
Open to anyone
One transaction, signed by your wallet, straight to the pons launcher — with the fee stream pointed somewhere better than a personal wallet.