A standing bid on the last mile of Four's curve.
Before Pancake (or Lista) seeding, the token is still inside Four's pool. That slice — ≥90% of the curve — is where snipers and "almost bonded" size already sit. $4migrate proposes a rule-based bid on that slice. The router is not linked to this site yet.
One band. No exceptions.
$4migrate inventory is Four.meme tokens whose bonding progress reads p ≥ p_min. Nothing else qualifies.
Ship p_min = 0.90
...unless another number is published. When a name prints p < p_min, the contract must not buy it. No discretion, no "just this once."
One fork, chosen in code
When a name migrates, the contract either keeps the DEX bag, or exits to quote and recycles into the next p ≥ p_min name. See the fork below.
The proposed tax would buy the band.
Buy / sell tax → quote
Routes to BNB or USDT — matching Four's raise token for that curve.
Router scope
May only spend that quote on Four Portal tokens with live p ≥ p_min. Nothing outside the Portal.
Creator receiver = 0
No creator cut, no second wallet skimming the tax stream.
Idle rule
If no name is in the band, tax sits in the contract as quote. It does not buy a 40% curve "for narrative."
Check the contract before the claim.
A router needs a published selection rule before it can make a verifiable buy. Check a candidate below while the router contract is pending.
Graduation is the only event that matters.
A name can stall at 92% forever. There is no Four insurance.
Can stall at 92% forever with no PairCreated event.
Can get rugged mid-curve — paper can go to zero.
Can fail wash-trade checks and get delisted from the Portal.
No Four insurance. No refund path if a name never bonds.
Say the boundary out loud.
FourVault — no 500k mint address.
FourDaily — no BNC4 #1 burn.
A claim on Four's seeding fee.
An oracle that "predicts" which meme bonds.
The transaction ledger starts with a contract.
There are no verified 4Migrate buys or migration events to list. Once a router contract is published, this area can read its transactions from BNB Chain.
FourMigrate is a standing order for the last 10% of Four's curve.
If that 10% never becomes a pair, the bag is still the curve.
Before you ask in the replies.
The proposed p_min is 0.90. No deployed router contract or live configuration has been supplied, so the website cannot verify a binding threshold.
The inventory paper can go to zero — there's no Four insurance and no automatic exit before a PairCreated event. That risk is priced into NAV, not hidden from it.
No. That is the proposed router rule. No deployed router contract has been supplied, so the site cannot claim it is active.
Path A keeps the DEX bag after migration — you inherit the new LP token. Path B exits that bag to quote immediately and recycles the proceeds into the next p ≥ p_min name. A deployed contract would need to choose one path. No such contract has been supplied to this site.
No. $4migrate targets public bonding-curve mechanics on Four.meme and public seeding venues. None of them are involved in building, running, or endorsing this token.