$GITPAD

#Purpose

$GITPAD is gitpad's protocol token. Under gitpad's revenue policy, the largest share of the platform revenue gitpad claims is reserved for $GITPAD buybacks.

$GITPAD gives no equity, no redemption right, no governance, no staking and no claim on revenue. A ticker alone does not establish the official token: always compare the mint address published here.

#Revenue policy

gitpad's platform revenue is its partner share of trading fees: 0.406% of curve trades (after discovery rewards) and the fees earned by the locked partner position after graduation. Builder fees and discovery rewards are never platform revenue.

The active policy splits claimed platform revenue as follows:

How it applies:

• Only fees that have actually been claimed into gitpad's receiving wallet can be allocated. Accrued, unclaimed fees are never spendable.
• Before gitpad collects curve partner fees, it reserves every unpaid discovery reward. Only the remainder is platform revenue.
• Each claim is allocated once, in integer lamports. The buyback and liquidity parts are rounded down and the treasury receives the rounding remainder.
• Policies are versioned and immutable once active. A different split requires a new policy version; past allocations keep the policy that produced them.

A reserve records an allocation. It does not mean a purchase has happened.

#Buybacks

The 60% buyback reserve funds purchases of $GITPAD from the market. Buybacks can only happen after $GITPAD exists and its mint is configured.

Each buyback is recorded against a finalized transaction receipt. Hand-verified receipts are committed to data/platform-receipts.json in the public source; the worker detects later ones on chain. gitpad verifies the SOL spent from its custody wallet and the $GITPAD received before the purchase is counted, and the reserve is reduced by the verified amount. /stats shows the total SOL spent on buybacks with links to each receipt. Launch purchases and early team purchases are excluded from that total.

No burn mechanism is implemented. Any future burn policy would be announced separately. There is no promised buyback schedule or return.

#Protocol liquidity

The 20% liquidity reserve can be used to deepen a repository's graduated DAMM v2 pool. Each deployment is a manually reviewed, simulated operator action with explicit limits, and settlement is verified on chain.

These additional positions belong to gitpad's partner wallet and are not permanently locked, unlike the two positions created at migration. Automated protocol liquidity spending is disabled.

#Treasury

The 20% treasury share is retained by gitpad for operations. The treasury figure on /stats is a cumulative allocation, not a live wallet balance.

#Team token locks

If team tokens are locked at or after launch, each lock will be published here with its escrow account, original deposit, share of fixed supply, UTC release schedule, recipient, and whether it can be cancelled. Locks will also be shown on /stats and on the official market. A published lock covers only the escrowed tokens, not every token a team wallet may hold.

#At launch

This section will be completed at launch with:

• the official mint address;
• the launch transaction and market link;
• the launch wallet and any initial purchase;
• team lock escrows, if any.

Contract address: not yet published.