whitepaper 1.0

t0n

t0n is a TON Jetton issued through a deterministic Reserve Engine. There is no seed AMM, no discretionary market maker, and no manual pricing. Every buy deposits TON into a reserve contract and mints t0n from the engine's emission path. Every sell burns t0n and releases TON from the same reserve through the inverse path.

Purpose

The protocol is designed for transparent primary issuance. Price discovery starts inside the program itself instead of depending on an initial liquidity pool. The reserve is the counterparty: it receives TON on buys and pays TON on sells according to deterministic state.

Reserve Engine

The engine uses an asymptotic supply path. The cap is approached but never crossed by ordinary minting, keeping issuance deterministic while making late-stage supply increasingly expensive.

supply(reserve) = K * reserve / (S + reserve)
reserve(supply) = S * supply / (K - supply)

Parameters

• Supply cap: 21,000,000 T0N
• Scale: 31,000 TON
• Max buy: 5,000 TON
• Cooldown: 1 slot after buy before sell

Canonical Addresses

The following identifiers are the canonical mainnet references for this deployment. Users should verify these values before interacting with the engine or importing the Jetton.

• Network: TON mainnet
• Token name: t0n
• Token symbol: T0N
• Jetton master / CA: EQAJXg4N-TA0xNkM6ApEOBzEXhW15keZRTk_eCrXye8IfXbK
• Reserve Engine contract: EQAJXg4N-TA0xNkM6ApEOBzEXhW15keZRTk_eCrXye8IfXbK
• Owner/dev authority: EQCKYa5PPBqkjI0So3mP4huwYvUWUxwikK_UBMuO0uhHjBzv

Contract Interface

• Buy: send TON to the Reserve Engine with the engine buy message.
• Sell: burn T0N through the user's Jetton wallet; the master contract releases TON through the inverse path.
• Fee withdrawal: owner-only instruction that transfers accumulated engine fees to the owner/dev authority.
• Read methods: reserve data, Jetton data, and wallet address derivation follow the deployed Jetton master contract.

Settlement

Buys and sells settle directly against the TON reserve contract. A buy deposits TON and mints t0n through the forward path. A sell burns t0n and releases TON through the inverse path.

Exhaustion

Full cap is mathematical, not practical: reaching 100% would require infinite reserve. The protocol therefore treats exhaustion as a threshold. Once the configured threshold is reached, new buys stop while sells remain available against the remaining reserve.

Authority

The mint authority is program-derived. The owner/dev wallet is used for initialization and metadata operations. It does not manually price trades and does not mint outside the Reserve Engine.

Mainnet Launch

A mainnet deployment should publish the canonical Jetton master, reserve contract, metadata URI, owner/dev authority, and source hash before public use. The deployed Jetton master should use the authority expected by the Reserve Engine, and metadata should identify the token as t0n with symbol T0N.

Risks

t0n is experimental software. The interface shows deterministic quotes from current on-chain state, but final execution depends on transaction ordering, wallet approval, network conditions, and current reserve state. The Reserve Engine is not an AMM and does not promise secondary-market liquidity. Users should verify the deployed addresses and understand that smart-contract risk, wallet risk, and market risk remain.