One project. One token. 🌲
Here's our full token migration plan.
TL;DR
→ GITLAWB and TWIG move 1:1 into one new token
→ 100% of its trading fees stay with the project
→ Liquidity rebuilt from the old pool and locked forever
→ A window of at least 2 weeks, and you can withdraw any time until it closes
No action needed today. The window opens only after a second post with the exact steps.
⚠️ Stay safe
We're keeping the new token's name private until launch, on purpose. Only the migration contract can create it, at the end of the window.
Any token claiming to be our new one before our second post is fake. We will never DM you. The address will come only from
@twigpine.
Why now?
In March, someone from ct launched GITLAWB through Bankr. It brought us early attention, and its trading fees have helped fund the build ever since.
Here's what we built with it. Today:
→ OpenClaude: 34.3K GitHub stars, 422K+ npm downloads
→ OpenGateway: 1.7T+ tokens routed
→ Playground: 3,500+ apps published by 3,200+ builders, 685K+ app visits
→ OpenLaunch: 6,500+ token launches
In September we became Twigpine. The code, the network and your keys all carried over. Now the token catches up.
What the new token fixes
→ Name: GITLAWB is written into its contract forever. The new token carries our own name.
→ Fees: today 43% of every trading fee leaves the project, permanently. On the new pool, 100% stays with Twigpine.
→ Treasury: the old token never had one. The new one has a vested treasury to build with.
→ One token: no more GITLAWB, TWIG, a Robinhood Chain bridge and split pools. One token only.
The community token got us here. The new one is built for what comes next.
How it works
The new token is designed to start where GITLAWB is today, so there's no reason to trade a certain way around the migration.
1. Holder migration
→ 1 GITLAWB = 1 new token
→ 1 TWIG = 1 new token (the contract unwraps it for you)
→ Deposit any time in the window. Withdraw any time until it closes.
→ After close, claim your new tokens yourself. Claims never expire.
→ On Robinhood Chain? Bridge back to Base, then deposit.
2. Liquidity migration
The old pool's liquidity is locked forever, so we rebuild it instead. At close, one transaction in the migration contract:
→ records how many GITLAWB sit in the locked pool, and the rate it trades at right then
→ mints the same amount of the new token as the token side of the new pool
→ sells every deposited GITLAWB into the old pool to recover its ETH
→ puts all of that ETH in as the ETH side of the new pool
→ opens the new pool at the rate it recorded, from before the sale
Both positions go to an ownerless locker, locked forever. None of the ETH goes to any wallet, ours included. The more holders migrate, the deeper the new pool starts.
3. Supply
Fixed at close. It can never grow.
→ 70% migrated: your deposits plus the mirror of the locked pool. The only supply circulating at launch.
→ 20% treasury: 6-month cliff, then vests over 24 months.
→ 10% raise reserve: locked 12 months. Any release needs 30 days' public notice. Whatever isn't used can be burned after that.
No owner. No pause. No upgrades.
Building on OpenLaunch?
If your pool is quoted in GITLAWB or TWIG, we'll give you the same migration tool, free, so your pool moves over with us. Your window closes 48 hours before the main one. Details come with the second post.
Don't miss the window. After close, everything Twigpine builds supports the new token only, and the old pool keeps far less ETH.
What's next
→ Tell us what you think in the replies. We read all of it.
→ A full fork-test suite and an outside review before anything goes live.
→ Then the second post: the name, the steps, the address and the dates.
→ Once the window opens, you'll have at least 2 weeks.
Shout out to
@AskSurplus for sharing this structure first. Ours lets you withdraw any time before close and puts 70% of supply with migrated tokens.
Roots to canopy 🌲
Subject to change based on community feedback.
