Fig. 1. Each twig is one burn: a transaction that sent GITLAWB to the burn address. Its bud sits at the moment of the burn, and its length follows the square root of the amount. Time runs left to right on a square-root scale from 23 May 2026, Base on the upper limb and Robinhood Chain on the lower. The newest bud is green. Hover, tap or use the arrow keys to read a burn.
A burn
A larger burn
The newest burn
No burns then
Sources
Burned: read · Base and Robinhood RPC, balanceOf the burn address on each chain
Burns: read · Base and Robinhood RPC, every Transfer log to the burn address
Holders of GITLAWB on Base: read · Base RPC, replay of every transfer, kept current by the indexer
Holders of TWIG: read · Base RPC, replay of every transfer, total supply reconciled
Holders on Robinhood Chain: read · Robinhood RPC, replay of every transfer (indexed)
Wrapped as TWIG: read · Base RPC, TWIG totalSupply
TWIG's backing: read · Base RPC, GITLAWB balanceOf the TWIG contract
On Robinhood Chain: read · Robinhood RPC, totalSupply of the OFT
Locked in the bridge: read · Base RPC, balanceOf the OFT adapter
Your tokens.Three addresses on two chains, all GITLAWB underneath.
GITLAWB on Base is the original. GITLAWB on Robinhood Chain is the same token moved over a bridge, and TWIG is its optional wrapped form. Each crossing is 1:1 and works both ways.
GITLAWB on Base
Canonical
The original token, launched on 11 Mar 2026 through Bankr: a standard Bankr launch of Doppler’s DERC20. Its owner is Doppler’s Airlock, a protocol contract, not a Twigpine key.
Supply
100Bread · Base RPC, totalSupply
Holders
11,438read · Base RPC, replay of every transfer, kept current by the indexer
The same token, bridged 1:1 over LayerZero: locked on Base and created on Robinhood Chain. Bridging back removes it here and releases the same amount on Base.
On this chain
586.57Mread · Robinhood RPC, totalSupply of the OFT
Locked on Base
586.57Mread · Base RPC, balanceOf the OFT adapter
Holders
332read · Robinhood RPC, replay of every transfer (indexed)
An optional 1:1 wrapped form of GITLAWB, live since 1 Oct 2026. Wrap and unwrap any time; each TWIG is one GITLAWB held by the TWIG contract. The contract has no owner.
Supply
2,779.16Mread · Base RPC, TWIG totalSupply
Held by the contract
2,779.16M GITLAWBread · Base RPC, GITLAWB balanceOf the TWIG contract
Holders
276read · Base RPC, replay of every transfer, total supply reconciled
Since launch
910 wraps, 784 unwrapsread · Base RPC, every TWIG mint and burn log
A box is a token, or the burn address on one chain. Dark outline: GITLAWB on Base, the original.A line is a way GITLAWB moves: the wrap and the bridge, both 1:1, and sends to the burn address.A moving dot is one real transfer; its area is in proportion to the amount, up to 79.27M GITLAWB.A settled dot is one burn transaction; the green one is the newest.
Fig. 2. Each box is a token, or the burn address on one chain; GITLAWB on Base, outlined in ink, is the original. Lines are the wrap (1:1 with TWIG), the bridge (1:1 with Robinhood Chain) and sends to the burn address. The figure replays the last 24 hours of transfers at one hour a second: each dot is one real transfer, sized by amount, and the boxes show the reading at the time on the rail. Hover or focus a box to see what it is.
Transfers: read · Base RPC logs (TWIG mints and burns, OFT adapter sends and deliveries) and both chains' burn logsTWIG supply: read · Base RPC, TWIG totalSupplyGITLAWB held by TWIG: read · Base RPC, GITLAWB balanceOf the TWIG contractOn Robinhood Chain: read · Robinhood RPC, totalSupply of the OFTLocked on Base: read · Base RPC, balanceOf the OFT adapterBurned: read · Base RPC, balanceOf the burn address and read · Robinhood RPC, balanceOf the burn addressWhile replaying: Base RPC, TWIG mint and burn logs replayed to each UTC hour; Robinhood RPC, OFT mint and burn logs replayed to each UTC midnight
Market
GITLAWB/WETH the main pool, Base
Price
$0.00001851
24h volume
$28.8K
Liquidity
$425K
Market cap, price × supply outside the burn addresses
The TWIG/WETH pool can print odd prices and can differ from GITLAWB. TWIG is always redeemable 1:1.
Both pools: read · DexScreener, our pool by its id · Market cap: the GITLAWB price × the 100B supply less both burn addresses' balances (Base and Robinhood RPC), as of
Tools.Each one says which chain it works on.
Wrap and unwrap Base
Turn GITLAWB into TWIG 1:1, or TWIG back into GITLAWB, any time. Nothing to do if you only hold GITLAWB.
Move GITLAWB between Base and Robinhood Chain over LayerZero, 1:1. It usually arrives in a few minutes. TWIG does not cross; unwrap it to GITLAWB first.
Paste a token address. The page compares all 40 characters with the address the launcher returns from twig(), and says only whether it is the official TWIG.
Checking GITLAWB? Compare it with the addresses under Your tokens.
Add to wallet Base and Robinhood Chain
Each token's card under Your tokens adds it to your wallet on the right chain. Your wallet asks before it adds anything, and adding a token never moves one.
Basescan reads Base and Robinscan reads Robinhood Chain: every address on this page links to one of them. Bridge messages between the two chains can be followed on LayerZero Scan.
Supply.Where all 100B GITLAWB are, read from the chain.
Fig. 3Where all 100B GITLAWB are
As of
At the burn address on Base
912.57M
912,568,775 · 0.91%
Nobody holds the key to this address.
read · Base RPC, balanceOf the burn address
Locked in the bridge for Robinhood Chain
586.57M
586,565,406 · 0.59%
GITLAWB on Robinhood Chain is not extra supply: each one is minted against one locked here. Hatched: the 76.20M at the burn address on Robinhood Chain.
read · Base RPC, balanceOf the OFT adapter
Held for TWIG, 1:1
2,779.16M
2,779,159,971 · 2.78%
The TWIG contract holds one GITLAWB for every TWIG.
read · Base RPC, GITLAWB balanceOf the TWIG contract
Everything else on Base
95.72B
95,721,705,848 · 95.72%
Wallets, pools and other contracts.
as of · the total supply minus the other three parts
At the burn address on Base912.57M912,568,775 · 0.91%Nobody holds the key to this address.read · Base RPC, balanceOf the burn address
Locked in the bridge for Robinhood Chain586.57M586,565,406 · 0.59%GITLAWB on Robinhood Chain is not extra supply: each one is minted against one locked here. Hatched: the 76.20M at the burn address on Robinhood Chain.read · Base RPC, balanceOf the OFT adapter
Held for TWIG, 1:12,779.16M2,779,159,971 · 2.78%The TWIG contract holds one GITLAWB for every TWIG.read · Base RPC, GITLAWB balanceOf the TWIG contract
Everything else on Base95.72B95,721,705,848 · 95.72%Wallets, pools and other contracts.as of · the total supply minus the other three parts
At the burn address on Base
912,568,775 · 0.91% GITLAWB. Nobody holds the key to this address.
Locked in the bridge for Robinhood Chain
586,565,406 · 0.59% GITLAWB. GITLAWB on Robinhood Chain is not extra supply: each one is minted against one locked here. Hatched: the 76.20M at the burn address on Robinhood Chain.
Held for TWIG, 1:1
2,779,159,971 · 2.78% GITLAWB. The TWIG contract holds one GITLAWB for every TWIG.
Everything else on Base
95,721,705,848 · 95.72% GITLAWB. Wallets, pools and other contracts.
Total supply 100B: read · Base RPC, totalSupplyAt the burn address on Robinhood Chain 76.20M: read · Robinhood RPC, balanceOf the burn addressReplay: one reading a day at 00:00 UTC from 8 Sep 2026, rebuilt from Base and Robinhood RPC logs
Fig. 3. The top bar is all 100B GITLAWB on Base, to scale; the band under it draws the first 5B 20 times wider so the small parts can be read. Solid ink is at the burn address on Base. GITLAWB on Robinhood Chain is counted inside the bridge part, and that part's hatched end is what sits at the burn address on Robinhood Chain. On load it replays one reading a day from 8 Sep 2026, then the current readings.
Burns.Tokens sent to an address nobody can spend from.
Tokens at the burn address can never move. They still count in the 100B total supply.
The total is the burn address's balance on Base plus its balance on Robinhood Chain. The GITLAWB behind a burn on Robinhood Chain stays locked in the bridge on Base, not at Base's burn address, so adding the two counts nothing twice. Bridging back from Robinhood Chain is not counted here: it removes GITLAWB there and releases the same amount on Base.
The burn address, the same on Base and on Robinhood Chain
Cross-check: at the Base explorer's transfer list showed 231 Base burns; the chain's logs up to then show 235.
By month
GITLAWB burned per month, UTC
GITLAWB burned per month, on each chain
Month
Base
Robinhood Chain
Total
Oct 202624 burns
43.37M
0.02M
43.39M
Sep 2026162 burns
533.85M
73.24M
607.09M
Aug 20264 burns
27.42M
None
27.42M
Jul 202658 burns
186.80M
2.93M
189.73M
Jun 2026No burns
None
None
None
May 202652 burns
121.14M
None
121.14M
Holders.Counted per token, on each chain.
GITLAWB on Base
11,438
read · Base RPC, replay of every transfer, kept current by the indexer
GITLAWB on Robinhood Chain
332
read · Robinhood RPC, replay of every transfer (indexed)Cross-check: the Robinhood Chain explorer shows the same count, read
TWIG on Base
276
read · Base RPC, replay of every transfer, total supply reconciled
An address can hold on more than one chain, and hold TWIG as well, so these counts are not added together.
Fig. 4Holder counts over time, one reading an hour
As of
Fig. 4. One row per token, each on its own scale because the counts are far apart. Hourly readings started 2 Oct 2026, 13:49 UTC; the line runs through them and ends at the current count, the dot at the right. The shaded part is time before the readings started, and nothing there is filled in.
Official contracts.If an address is not on this list, it is not ours.
Copy addresses from here, never from a reply or a direct message. Compare all of the characters, not only the first and last few.
The Robinhood Chain side is the token itself: GITLAWB on Robinhood Chain, under Tokens. It adds supply when GITLAWB arrives from Base, and bridging back removes it there and releases the same amount from the adapter.
The name comes from git itself, which already calls its history a tree: every signed commit is a twig, and the network is the pine that grows from them.
Gitlawb is now Twigpine. The reveal film, 60 seconds, with sound; it plays only when you press play.A git branch named gitlawb is renamed twigpine. Signed commits land one by one and grow into a pine, each commit a twig; the history stays as it was and only the name changes. It ends on the Twigpine mark. An original score plays throughout; there is no narration.
For holders: what changed, and what you do
Item
What changed
What you do
Your GITLAWB
Nothing. Same contracts on Base and on Robinhood Chain, same balance. The contract cannot be renamed on-chain, so wallets still show Gitlawb.
Nothing.
TWIG
New and optional: a 1:1 wrapped form of GITLAWB on Base.
Safety.Same rules as the wrap page, word for word.
Signing
Wrapping never asks you to sign a message.
Sending
Never send GITLAWB to the TWIG address.
Tokens sent straight to the TWIG contract are not wrapped for you and cannot be recovered. Use Wrap.
Approvals
Approvals: GITLAWB approvals go to TWIG; TWIG approvals go to Permit2; the Permit2 spender and router is 0x6fF5693b99212Da76ad316178A184AB56D299b43. If your wallet shows any other address, stop.
The official TWIG
The TWIG address is posted first and only by @twigpine and matches twigpine.base.eth. It never changes. No migration, claim, airdrop, snapshot or presale. We never DM first; Kevin has no new or backup account. Wrapping never asks you to sign a message. Anyone can name our wallets as a token's admin or fee recipient without our consent. Any other $TWIG/$TWIGPINE/$PINE/'Twigpine' token is not ours.
The contracts
No admin keys. Source verified. Tested on a Base mainnet fork. Not audited.
The wrap page states these two in its section on fees. In the second, “this page” is the wrap page.
The TWIG/WETH pool
500M TWIG, wrapped from the founder's GITLAWB, is placed as liquidity in a TWIG/WETH pool that nobody, including the founder, can withdraw. Buyers take TWIG out of it, and that TWIG then circulates normally. This is not a burn and does not reduce supply. WETH paid in stays in the pool as bids that TWIG sellers can take back out. The pool's 1% LP fee goes to the founder's fee Safe. Uniswap may also take 0.1%, so traders pay about 1.1%.
The main GITLAWB pool
Routes through the main GITLAWB pool pay its 1.2% fee; 57% of that goes to the founder. This page picks the best output.
Questions.Short answers.
Do I need to wrap?
No. Your GITLAWB stays as it is. TWIG is optional: wrap only if you want TWIG, and unwrap any time.
Why does my wallet still say Gitlawb?
A token's name is written into its contract and cannot be changed on-chain, so wallets still show Gitlawb. The contract, the address and your balance are the same.
Can TWIG go to Robinhood Chain?
No. Unwrap TWIG to GITLAWB on Base, then bridge the GITLAWB, 1:1, from the bridge page.
Why did a swap app quote me less for TWIG?
Some swap apps skip the 1:1 wrap route and price TWIG from the TWIG/WETH pool alone. The wrap page compares the routes and picks the best output.
Where do fees go?
Trades through the TWIG/WETH pool pay an LP fee that goes to the founder's fee Safe. Trades routed through the main GITLAWB pool pay that pool's fee, and part of it goes to the founder. The wrap page's exact sentences, with the rates, are under Safety.
Has TWIG had a security review?
No admin keys. Source verified. Tested on a Base mainnet fork. Not audited.
Is TWIG an airdrop or a new launch?
No. TWIG is an optional 1:1 wrapped form of GITLAWB: each TWIG is one GITLAWB held by the TWIG contract, and you can unwrap it back any time. There is nothing to claim.
How are these numbers read?
From the chains. Burned totals, supplies and wrapped and bridged amounts are read over RPC from Base and Robinhood Chain; explorer counts are used only as a cross-check, and each holder count names its method. Every number shows its source and the time it was read. If a source fails, the number is hidden and the page shows when it was last read; nothing is filled in.
Talk to the community.Questions in Discord, news on X.