Loading price
Unlock TimelinePublic lock topology

Unlock is where direct-buy batches become liquid: each purchase mints immediately, locks immediately, and releases only when its own 14-day timer expires.

The mobile wallet shows a personal unlock timeline for the selected signing wallet. The public site should not fake that personal state, but it can show the global picture: how much 4TEEN is currently locked by active direct-buy batches, how much sits in reserve vault custody, and which recent batches unlock next.

Total Supply

10.1m

Current FourteenToken totalSupply including direct-buy minting.

Locked Now

21.79

System-wide direct-buy batches still inside the 14-day lock window.

Vault Custody

6.49m

4TEEN held by FourteenVault, AirdropVault, and TeamLockVault.

Freely Circulating

3.61m

Public estimate after removing active locks and vault custody from total supply.

Wallet Context

Personal unlock timeline lives inside the mobile wallet

The website can explain the lock model and show public release topology, but the personal unlock timeline belongs to the app because it depends on the selected wallet address, direct-buy history for that wallet, and live on-chain reads for lockedBalanceOf(account).

  • Every direct buy creates its own lock batch with its own release timestamp.
  • Wallet unlock timeline tracks only direct-buy history tied to the selected wallet, not generic swap history.
  • Once a batch unlocks, the tokens become transferable and market routes like swap become relevant.

Live Lock Map

How much 4TEEN is locked and how much is actually liquid

Total Supply10.1m 4TEEN
Active Lock Batches1
Currently Locked21.79 4TEEN
Vault Custody6.49m 4TEEN
Freely Circulating3.61m 4TEEN
Next Unlock2026 M05 4 20:52:57 UTC
Snapshot Updated2026 M05 4 06:42:15 UTC

Freely circulating here is a public systems estimate: total supply minus active direct-buy locks minus tokens held in reserve vault contracts. It is intentionally stricter than a naive totalSupply view.

Vault Layer

Reserve custody is not the same as free circulation

The 4TEEN architecture keeps reserve allocations in dedicated contracts. FourteenVault holds liquidity reserve tokens, AirdropVault holds staged community distribution reserves, and TeamLockVault isolates the team allocation. These balances exist on-chain, but they should not be presented as freely circulating supply.

AirdropVault also receives routed TRX on direct buy, but the token balance shown here is only the 4TEEN reserve actually parked in vault custody.

Upcoming Unlocks

Recent direct-buy batches that still have time left on their lock

BuyerLocked BatchUnlock AtSource
BuyerTEGQN1...TmCi1s
Locked Batch21.79 4TEEN
Unlock At2026 M05 4 20:52:57 UTC
SourceOpen tx

This release map is built from confirmed BuyTokens events that still sit inside the 14-day lock window. It shows public batch timing, not a private wallet portfolio.

Lock Mechanics

What the main token contract actually enforces

Mint

Direct buy mints first

buyTokens() mints 4TEEN in the same transaction that receives TRX. There is no off-chain fulfillment queue for the purchased amount.

Batch

Every purchase creates a separate lock entry

The token contract appends a new LockInfo record per direct buy. Locks are not merged into one generic timer.

Rule

Transfers are blocked by lockedBalanceOf()

transfer() and transferFrom() both require available balance after subtracting lockedBalanceOf(account). Locked tokens cannot be moved early.

Wallet Route

How the app turns this contract state into a usable timeline

Balance

Reads total, locked, and available balance

The wallet combines balanceOf(account) with lockedBalanceOf(account) to show what is still frozen and what is already movable.

History

Builds rows from confirmed BuyTokens events

Each direct-buy event becomes a visible unlock row with exact amount, unlock time, countdown, and Tronscan transaction path.

Action

Points the user to the next valid route

Unlock timeline is the right route after buy. Swap becomes relevant only after the locked batch is released and actually transferable.

This is why the public site should explain unlock clearly, then send the user into the wallet for personal history instead of pretending to be the execution surface.

Verification

Where the numbers and lock logic come from

This page uses the deployed FourteenToken contract, the wallet unlock-timeline implementation, and the known reserve vault addresses. It explains live mechanics and custody structure instead of flattening everything into a generic token-supply chart.

Next Step

Use the app when you need your personal unlock timeline

The public site can show the protocol-wide lock map. The wallet is still the right surface for address-specific unlock rows, countdowns, and post-buy follow-up.