What is this?
One new token replacing GITLAWB and TWIG, 1 for 1, on Base. This page is where you follow it and, when the window opens, where you migrate.
Why change tokens at all?
Five fixes: the name (GITLAWB is written into its contract forever), the fees (43% of every pool fee leaves the project today; on the new pool 100% of a 1% fee stays, 46% more per day at the same volume), a treasury (the old token never had one), owner powers (GITLAWB's code carries a 2% yearly mint and a pool lock; the new token has none), and one token instead of GITLAWB, TWIG and a bridge. See what the new token fixes.
Do I need to do anything today?
No. The window opens only after a second post from @twigpine with the exact steps. Nothing on this page sends a transaction until then.
What is the new token called?
We're keeping it private until launch, on purpose. Only the migration contract can create it, at the end of the window. Any token using our name before the second post is fake.
How much do I get?
1 GITLAWB = 1 new token. 1 TWIG = 1 new token.
What is the token for?
It is the native token of the Twigpine stack: after close, the quote pair on OpenLaunch (launch, boost, pair, badge), a free tokenize pair on Playground and what Museworld launches quote, and the token of the Twigpine network, the git protocol under all of them. It is spent inside the products. See where it works.
I hold TWIG.
Deposit TWIG directly; the contract unwraps it for you. Or unwrap first at wrap.twigpine.com.
I hold GITLAWB on Robinhood Chain.
Bridge back to Base first, then deposit. The bridge is on community.twigpine.com.
I hold MUSEWORLD.
Its own contract sells deposited MUSEWORLD back into its pool in one batch, hands the recovered GITLAWB to the main migration, and pays out evenly: the GITLAWB the batch recovers, divided across every MUSEWORLD deposited, then 1:1 into the new token. Its window closes 48 hours before the main one.
Can I change my mind?
Yes. Withdraw any time until close.
What happens at close?
One transaction: it records how much GITLAWB sits in the locked pool and the rate, mints the same amount of the new token for the new pool, sells every deposit into the old pool to recover its ETH, puts all of that ETH into the new pool at the recorded rate, and locks both positions forever.
Doesn't selling every deposit into the old pool push the rate down?
Not the rate the new pool opens at, and not the count a deposit claims. The migration contract sells no GITLAWB or TWIG during the window: deposits sit in it, and you can withdraw until close. The sale happens once, at close, after the window has ended. Before it sells, the contract records the rate the old pool shows, and the new pool is created at that recorded rate. 1 GITLAWB or 1 TWIG deposited is 1 new token, whatever the sale recovers. TWIG deposits are unwrapped into GITLAWB and sold in the same batch; TWIG is not sold separately. Where the sale does push the rate down is the old pool: it moves ETH out of the old pool into the new one, so GITLAWB or TWIG that was not deposited trades in a far thinner pool afterwards, at a lower rate than the one recorded before the sale. Deposit before close. What the sale decides for the new pool is how much ETH it opens with: the more that migrates, the deeper it starts; the less, the shallower. The table shows it live at each amount.
Can GITLAWB or TWIG move down before close?
Yes. Like any token, it can move for any reason, this plan included: GITLAWB and TWIG trade freely during the window, and nobody can promise otherwise. If the old pool's rate moves during the window, the new pool opens at whatever rate the old pool shows at close. The contract sells no GITLAWB or TWIG before close, and 1 for 1 is about count, not about what the token trades for. We can't tell you whether to buy, hold or sell. This page is not advice; it tells you what the contract does and when: see how it works and what the new token fixes.
Does the team get any ETH?
None of the recovered ETH: all of it goes into the new pool's locked position, and no wallet, ours included, can take it out. What Twigpine receives is the new pool's 1% trading fee.
What if I don't migrate?
Your GITLAWB and TWIG stay yours. OpenLaunch's launch forms and Playground's tokenize stopped offering GITLAWB and TWIG on 6 Nov 2026. After close, the plan is for boosts and pair reviews to move to the new token and for launches to pair with it, and the old pool keeps far less ETH. Deposit before close; claiming can wait forever.
Who controls the new token?
No one. No owner, no mint, no pause, no upgrade. The migration contract has one admin power: extend the window once, by up to 14 days.
Where does the supply go?
Fixed at close. 80% is migrated supply: your deposits plus the mirror of the locked pool, the only supply circulating at launch. 20% is the treasury, on a 6-month cliff and a 24-month vest.
Is the code reviewed?
A fork test suite, a rehearsal on Base Sepolia and an outside review happen before the second post. Each result is linked here as it lands.
I build on OpenLaunch and my pool is quoted in GITLAWB or TWIG.
Your pool is not part of this migration. Museworld is the only quoted pool that folds in. Your pool stays exactly as it is, its locker is ownerless, and after close GITLAWB trades in a thinner pool. OpenLaunch quotes the new token after close: launch your next one there.
Taxes?
We can't advise on that. Ask your own adviser.
How do I know this page is real?
Only migrate.twigpine.com, linked from twigpine.com and @twigpine. We never DM first, and this page never asks you to sign a message.