Direct Price
Unavailable
Per 1 4TEEN via protocol
4TEEN Mobile App
One place for buy, lock visibility, and liquidity flow.
The wallet app is already the operating layer of the system. Direct buy, unlock timeline, liquidity controller, Telegram claim state, ambassador cabinet, and the compact info route already exist as real screens with real state instead of promises in copy.
Prepare the real direct-buy flow with estimate, split context, and confirmation before signing.
Track each locked purchase event by countdown, unlock state, and source transaction.
Use one info route for contracts, asset wallets, executors, and runtime readiness.
DEX Price
Unavailable
Router quote read failed
Unlock Cycle
14 Days
Direct purchase lock period
Wallet Support
Wallet support matters because the app now reflects wallet state across live surfaces.
Direct buy, unlock rows, cabinet actions, and Telegram claim state all change depending on whether the selected wallet can sign, whether it is watch-only, and whether balance and resource state resolve cleanly in the flow.
Best mobile experience
Binance WalletWorks • Balance visible
Bitget WalletWorks • Balance visible
OKX WalletWorks • Balance visible
TokenPocketWorks • Balance visible
Works in mobile browser
FoxWalletWorks • Balance not displayed
imTokenWorks • Balance not displayed
MetaMaskWorks • Balance not displayed
TronLinkWorks • Balance not displayed
WalletConnectWorks • Balance not displayed
Trust WalletUse desktop Chrome extension
Recommended for app + buy flow:
Binance Wallet, Bitget Wallet, OKX Wallet, and TokenPocket give the smoothest experience because they correctly display balances and make the wallet-aware surfaces easier to trust.
Binance Wallet, Bitget Wallet, OKX Wallet, and TokenPocket give the smoothest experience because they correctly display balances and make the wallet-aware surfaces easier to trust.
Verify the Protocol
The wallet app, website surfaces, repos, and chain should all point to the same truth.
How It Works
What the operating surfaces now cover.
The app is no longer just a shell around links. It already handles explanation, wallet-aware gating, confirmation flow, surface-specific history, controller state, reward routing, and social-claim state.
1
Prepare the direct buy inside the app
The buy screen is a preparation step first. The selected signing wallet enters TRX, sees estimated 4TEEN, and only then moves into the confirmation layer where the app builds the real transaction and checks resources.
2
Track every locked batch by purchase
Unlock Timeline is not generic history. It reads direct-buy events for the selected wallet, shows UTC unlock time, live countdown, lock status, and the Tronscan transaction behind each purchase row.
3
Open the controller when you need liquidity truth
Liquidity execution is a real surface in the app. It shows the 100 TRX threshold, 6.43% daily release rule, executor split, contract links, and recent controller-side history instead of hiding that logic in copy.
4
Read social airdrop state as a real screen
The airdrop page combines three checks at once instead of pretending every social route is live.
WalletSigning or watch-only state changes whether the claim flow can continue
SessionTelegram bot session decides whether the card is available, verify-now, or session-live
ChainOn-chain claim state can already show received, queued, or legacy-used
5
Use one cabinet for registration, buyers, purchases, pending rows, and rewards
Ambassador flow is no longer a dead-end sign-up page. The same route starts with one-time slug registration and then becomes a working cabinet where referral identity, tracked purchases, claimable rewards, claimed totals, and pending allocation replay are visible together.
Architecture Diagram
How the info route explains the system on-chain.
The compact info route in the app now ties contracts, routing, vaults, executors, asset wallets, and runtime checks together. The website can still show the map, but it should reflect that this architecture already has a working product screen behind it.
EntryUser TRXDirect protocol buy enters the system
Core ContractFourteenTokenMint on purchase + 14-day lock + automatic TRX split
Mint on purchase
14-day lock
TRX split: 90% / 7% / 3%
90% TRX Path
Liquidity Execution Layer
The largest share moves into a dedicated liquidity system. Release timing, reserve storage, bootstrap preparation, and DEX execution are isolated into separate roles.
ControllerFourteenLiquidityControllerReleases 6.43% once per UTC day and controls when liquidity can move
Reserve VaultFourteenVaultStores the 4TEEN reserve used specifically for liquidity provisioning
Preparation LayerLiquidityBootstrapperCalculates required token amounts, pulls from FourteenVault, supplies executors, and triggers execution flow
50%LiquidityExecutorJustMoneyDEX-specific execution path for JustMoney
50%LiquidityExecutorSunV3DEX-specific execution path for Sun.io V3
7% TRX Path
Control + Ambassador Reward Layer
This path stays outside token issuance and liquidity execution. It combines protocol control with referral attribution, verified purchase allocation, level progression, and claimable ambassador rewards.
ControllerFourteenControllerOwns FourteenToken, manages owner functions, operator logic, reward accounting, purchase allocation, and controlled withdrawals.
Ambassador FlowRegistration → Binding → Verified Purchase → RewardWallet registration, public slug identity, buyer binding, verified purchase recording, claimable reward accrual, and reward withdrawal.
Ambassador Reward Ladder
Bronze0–9 buyers10%
Silver10–99 buyers25%
Gold100–999 buyers50%
Platinum1000+ buyers75%
Allocation logic: ambassador reward is calculated from the purchase owner share during verified purchase allocation. Level override is supported, and rewards move into claimable balance before withdrawal.
3% TRX Path
Community Distribution Layer
This path feeds the live airdrop structure. Distribution is staged by waves and expanded across multiple social routes instead of being treated like a one-off giveaway.
VaultAirdropVaultCommunity and growth reserve used for staged ecosystem distribution, wallet-linked reward flows, and live campaign routes
Distribution Model1,500,000 4TEEN • 6 Fixed WavesWave-based release structure with one live route today and more campaign routes added over time
Telegram LiveX SoonInstagram SoonMore Socials Ahead
Current Live RouteTelegram CampaignCurrent public route inside the live airdrop infrastructureOpen current live route
Live Airdrop Snapshot
StatusLive Now
Reward Range1–5 4TEEN
VerificationRequired
Wallet NeededTRON Wallet
Reward DeliveryOn-Chain
Claim TypeplatformBit = 4
LiquidityRelease timing, reserve storage, bootstrap prep, and DEX execution are isolated into dedicated contracts.
AmbassadorsLevel progression and reward percent are tied to real buyer count and verified purchase allocation.
AirdropThe community route is wave-based, multi-platform, and already live through Telegram.
Why it matters4TEEN behaves like a system of separated roles, not one overloaded contract blob.
Why This Structure Matters
The product layer is finally catching up with the protocol layer.
Contracts always had separated roles. What changed is that the app now exposes those roles as readable, wallet-aware screens instead of leaving users with only raw on-chain ideas and scattered links.
One hub already exists in the wallet app
The app home is already the compact product hub: buy, unlock, liquidity, airdrop, ambassadors, and info are grouped as surfaces, not buried in one long explanation.
Why it matters:
The website should point people into those same surfaces instead of describing an older imaginary roadmap.
The website should point people into those same surfaces instead of describing an older imaginary roadmap.
Wallet-aware state is real behavior now
Watch-only versus signing wallet, claimable versus pending rewards, Telegram session state, and resource readiness all change what the user can actually do in the app.
Why it matters:
That means the homepage text should describe states and actions, not only contract theory.
That means the homepage text should describe states and actions, not only contract theory.
Verification is already a working route
Architecture, contract roles, vaults, executors, asset-wallet balances, and allocation replay readiness are no longer only whitepaper topics. The app already exposes them as one compact info screen.
Why it matters:
The site is strongest when it describes that info layer as live product, not as future documentation.
The site is strongest when it describes that info layer as live product, not as future documentation.
Live Protocol Metrics
A live read of entry, liquidity, rewards, and operational state.
These cards should mirror what the user can actually open in the app: direct-buy context, unlock and controller-side state, cabinet reward flow, and the current Telegram-first social distribution route.
Direct Price
Unavailable
Per 1 4TEEN via protocol
DEX Reference
Unavailable
Router quote read failed
Unlock Cycle
14 Days
Fixed lock for direct purchases
Daily Liquidity Rule
6.43%
Released once per UTC day by controller logic
Liquidity Engine
Rule-Based Liquidity Flow
| Controller | FourteenLiquidityController |
|---|---|
| Reserve Vault | FourteenVault |
| Preparation Layer | LiquidityBootstrapper |
| Execution Split | 50% / 50% |
| DEX Paths | JustMoney + Sun.io V3 |
In the app this shows up as threshold checks, next release context, executor split, contract links, and controller-side history instead of one opaque “liquidity” sentence.
Ambassador Layer
Cabinet reward flow
Bronze10%
Silver25%
Gold50%
Platinum75%
In the app this route combines on-chain cabinet state with backend attribution rows, so claimable now, claimed total, and pending replay live together in one place.
Airdrop Layer
Live social distribution snapshot
| Total Allocation | 1,500,000 4TEEN |
|---|---|
| Wave Structure | 6 Fixed Waves |
| Current Live Route | Telegram |
| Other Socials | Read-only placeholders |
| Reward Delivery | On-Chain |
Tools
Open the same surfaces the app already exposes.
These are not placeholder menu items anymore. They map directly to routes and behaviors that already exist in the wallet-style product flow and already carry live wallet state.
OpenLiveTrackTrackLiveManageVerify
Mobile App
Open the dedicated mobile-app route with store download options and a clean fallback back into the web surfaces.
Buy 4TEEN
Open the direct-buy preparation screen with amount input, estimate, split context, and confirmation path.
Unlock Timeline
Read direct-buy event rows by wallet, unlock timestamp, live countdown, and transaction source.
Liquidity Controller
Follow threshold, 6.43% daily release, executors, recent controller events, and execution readiness.
Airdrop Status
See Telegram live-claim state, watch-only restrictions, bot session state, and on-chain reward state.
Ambassador Cabinet
Move from one-time registration into cabinet mode with slug, buyers, purchases, pending rows, and rewards.
Info Route
Open the compact architecture screen for contracts, asset wallets, runtime health, and public proof links.
Verification / Contracts
Verify the protocol across contracts, repos, docs, and the app hub.
The public story is stronger now because the wallet app already acts as an operating layer on top of those contracts, repos, docs, asset-wallet checks, and live surfaces.
Repositories
Public infra and operating code
Docs
Public reading layer
Hubs
Public ecosystem entry points
FAQ
Clear answers before you open the live surfaces.
The right questions are changing. Users now need clarity about what each route actually does, which actions depend on wallet type, and which growth or verification flows are already live in the app.
Why does 4TEEN need a direct-buy screen instead of only a swap?
Because the app treats direct buy as a separate contract-side surface. It prepares a mint-on-purchase flow, shows the estimate, explains the 14-day lock, and then moves to the real confirmation step.
What exactly does Unlock Timeline track?
Only direct-buy events tied to the selected wallet. Each row shows the amount, UTC unlock time, live countdown, current lock state, and the Tronscan transaction behind that purchase event.
Why do some routes care whether the wallet is watch-only?
Because the app now enforces behavior by wallet type. Watch-only wallets can read state, but cannot register as ambassadors, withdraw rewards, or execute signing flows like direct buy or liquidity actions.
Is the airdrop page just a promo page now?
No. It is already a stateful screen. Telegram is the live route, and the card combines local wallet state, current bot session state, and on-chain claim state before deciding what action is available next.
What does the info route verify that the website alone cannot?
It brings contracts, vaults, liquidity executors, asset-wallet balances, and operator-side readiness into one compact operational screen. That makes verification part of the product flow, not only a docs page.
Risk / Disclosure
Structured mechanics do not remove market risk.
4TEEN is an on-chain token protocol with visible rules, separated contract roles, and public verification paths. That makes the system easier to inspect, but it does not turn token participation into a guaranteed-return product.
What users should understand
- Direct protocol price is not the same as open-market DEX price.
- A 14-day unlock changes timing, but does not guarantee a favorable exit.
- Liquidity rules describe release behavior, not future market outcomes.
- Ambassador rewards and airdrop routes are structured layers, not guaranteed income.
What users should do
- Verify contracts, repos, and public documentation before acting.
- Understand the lock, reward, and distribution mechanics before buying.
- Use supported wallets and check live routes carefully.
- Make independent decisions instead of treating protocol structure as a profit promise.
Important: 4TEEN is built around observable on-chain behavior, not guaranteed outcomes. Users should verify the system themselves and act only with risk they understand.
Final CTA
Choose the Surface You Need
Get the mobile app, prepare a direct buy, verify the compact architecture route, or go straight into the live growth and tracking surfaces.
OpenBuyTrackManage
Get the App
Start from the mobile-app route with store download options and a clean handoff into the wallet product.
Open Direct Buy
Go straight into the contract-side entry flow with amount preview, confirmation, and wallet-aware gating.
Open Verification
Use the public proof layer for contracts, repos, liquidity logic, and the architecture map behind the app surfaces.
Open Ambassador Cabinet
Register, inspect referral identity, track purchases, and work with live reward state in one route.