Skip to content

PUT token

PUT is PUTGO's token. 90% of the supply fair-launches on PONS, and every participant gets PUT under the same rules; 10% belongs to the development team. PUTGO goes live one week after PUT launches.

Allocation and fair launch

Use Share Amount
Public launch on PONS 90% 900,000,000 PUT
Development team 10% 100,000,000 PUT
Total 100% 1,000,000,000 PUT
  • 90% of PUT enters the market through one public launch on PONS, and every participant gets PUT under the same rules.
  • 10% belongs to the development team from the launch.
  • Beyond that, there is no presale, no private round and no tokens reserved for anyone.
  • No lockups and no release schedule: the team's 10% is delivered in full at the launch, and after the launch no PUT is ever unlocked or released.

Fixed supply

1,000,000,000 PUT
  • 18 decimals.
  • The whole supply is created once at launch; no more can be minted afterwards.
  • Burned PUT leaves the supply for good and is never re-minted.

Launch timing

Launch day        PUT fair-launches on PONS
One week later    PUTGO goes live

The launch date will be announced separately. Until then you can walk through the whole flow on the testnet with test tokens (see the Testnet guide).

Using PUTGO does not produce PUT

The protocol distributes no PUT. Buying protection, depositing USDG, exiting early, settlement and claiming produce no PUT; there are no token rewards, points or emission programmes. A depositor's only income is the premium, paid in the market's asset; see Earn.

Protocol revenue: 80% buyback and burn, 20% to the development team

PUTGO charges one fee only: the protocol share of every premium, which goes to the protocol treasury at purchase (its ratio is on Markets and parameters). Depositing, withdrawing, expiry, delivery and claiming are free. This protocol revenue is split per asset into two parts:

  • 80% buys back PUT and burns it;
  • 20% goes to the development team for operating costs and income.
Every premium
→ the protocol share goes to the protocol treasury (in the market's asset: NVDA or UNI)
→ 80% goes to the buyback reserve
    → an authorized operator triggers a buyback manually
    → the asset is swapped for PUT and the PUT is burned in the same transaction
    → PUT supply goes down
→ 20% goes to the development team (operating costs and income)
  • Buybacks never happen automatically. The authorized operator decides when to execute and how much; there is no fixed schedule.
  • The swap and the burn happen in one transaction: either both steps succeed, or the whole transaction reverts and the assets stay in the buyback reserve.
  • Bought-back PUT is always burned and never handed to anyone.
  • The buyback reserve and the team share are accounted for separately: the buyback reserve can only be used for buyback and burn, and only the team can withdraw the team share. Neither a buyback nor a team withdrawal ever touches any user assets in a Money Pool.
  • The team share is paid in assets such as NVDA and UNI, not in PUT, and is separate from the development team's 10% of PUT.

Transparency

After launch the following will be public:

  • the premium each market has received in total;
  • the treasury's total protocol revenue per asset, and the parts that went to the buyback reserve and to the development team;
  • the current balances of the buyback reserve and the team share, and the total the team has withdrawn;
  • the total amount of assets spent on buybacks;
  • the total PUT burned;
  • the current PUT supply, that is 1,000,000,000 PUT minus the total burned.

Nothing on this page is a promise of PUT value.