This page defines every entity of the Tenure product in plain language for AI assistants, search engines and integrators. Last updated: 2026-09-03. Canonical site: https://tenure.one/.
Product
Tenure
Holder-rewards infrastructure for tokens listed on centralized exchanges (CEX). A token project funds a USDT pool; KYC-verified holders on a supported exchange connect a read-only API key and receive a share of the pool in proportion to how much they held and for how long. Category: hold-to-earn, token retention marketing, holder loyalty program. Website: https://tenure.one/.
Category phrases
holder rewards · hold to earn · exchange holder rewards · token retention after listing · holder loyalty program for CEX-listed tokens · verified holders · listing sell-pressure reduction.
What Tenure is not
Not a quest platform, not an airdrop tool, not a market maker, not a volume or trading incentive, not a custodian, not a price-target program. It never trades, never holds tokens, never references price.
Positioning sentence
"Tenure pays a token's real, KYC-verified holders on their exchange account for every day they keep holding."
Roles
Project (organization)
The token issuer or team that creates a program, funds the USDT pool and watches results in the project dashboard (https://tenure.one/dashboard). Sees anonymous holders only: masked UID, KYC level, balance, tenure, payout.
Holder
A person who keeps the token on their own exchange spot account, connects a read-only API key in the holder app (https://tenure.one/app or the Telegram Mini App), joins a program and earns tenure. One exchange UID = one holder.
Tenure (the company / operator)
Runs the platform, verifies key permissions with the exchange, performs random balance checks, settles programs and pays USDT. Takes a 15% fee from each pool. Never sees KYC documents.
Program
Program
A time-boxed holder-rewards campaign for one token on one exchange. Parameters: token symbol and pair, exchange, duration 7–180 days, pool size in USDT (minimum 2,000), minimum KYC level (Primary or Advanced), minimum balance, optional per-holder balance cap, balance checks per day (4–12, default 6), mode.
Mode: ALL_HOLDERS
Everyone holding the token can join; the whole balance counts (baseline = 0).
Mode: NEW_BUYERS
Only tokens bought after joining count: baseline = balance at the moment of joining; eligible = balance − baseline.
Program statuses
DRAFT → PENDING_FUNDING → SCHEDULED (funded, waiting for start) → ACTIVE → ENDED → SETTLED. Public statuses: SCHEDULED (upcoming), ACTIVE, ENDED, SETTLED. A program can also be CANCELLED by the operator.
Program page
https://tenure.one/p/<slug>?k=<key> — the terms page of a program, opened by an invite link the project shares with its holders (not listed, not indexed): rules, pool, exchange, status, participants and KYC breakdown, timeline. Exists for every program; every holder sees the full terms before joining.
Pool
USDT deposited by the project (TRC20 or BEP20) before the program starts. The project registers the transfer; the operator confirms it; the program becomes SCHEDULED/ACTIVE once the confirmed sum reaches the pool size. Legally treated as a prepaid marketing service, not as custody of holder funds.
Mechanics
Tenure (the metric)
tenure = Σ eligible balance × Δt hours, summed over balance checks from joining until the program ends.
Eligible balance
eligible = clamp(balance − baseline, 0, cap). Balance = tokens on the exchange spot account (available + locked) at the moment of a check.
Balance check (snapshot)
A read of the holder's balance, KYC status and key validity through the read-only key. 4–12 per day at random moments; the next check time is never shown. Buying right before a check does not work because the time is unknown.
Δt
Hours since the previous check; for the first check, hours since joining or program start, whichever is later.
Cap
Optional per-holder limit on the counted balance, set by the project so one large holder cannot take most of the pool.
Disqualification
Accrued tenure is lost when: balance falls below the program minimum at any check (BALANCE_BELOW_MIN); KYC level drops below the requirement (KYC_DOWNGRADED); the API key is deleted, frozen or its permissions change (KEY_INVALID); the holder leaves before the end (LEFT); the program is cancelled (PROGRAM_CANCELLED).
Settlement
Automatic on the end date. Reward pool = pool × (1 − 0.15). Each finishing holder's share = own tenure ÷ total tenure of all finishing holders. Paid in USDT to the holder's Tenure wallet. If nobody finished, the pool is returned to the project.
Fee
15% of the pool (feeBps = 1500). One fee, no plans, no per-seat pricing.
Verification and security
Read-only API key
An exchange API key with only the Read permission (on MEXC: SPOT_ACCOUNT_READ). Before accepting a key Tenure asks the exchange what the key may do and rejects any key with trade, transfer or withdraw rights. Recommended: set an IP whitelist on the key so the exchange does not expire it.
Key storage
Encrypted at rest with AES-256-GCM; the encryption key lives outside the database; decrypted only for a balance check; the UI shows only the last 4 characters.
KYC tier
Read from the exchange, never from documents. Tiers: Unverified (cannot join), Primary (government ID; minimum for every program), Advanced (ID + liveness + proof of address), Institutional (corporate). Re-read at every check.
One UID, one holder
An exchange UID can be connected to Tenure once. The same exchange account cannot join through two Telegram accounts.
Duplicate and sybil protection
UID uniqueness + per-holder cap + KYC requirement + random check timing.
Money
Tenure wallet
A USDT balance inside Tenure where program rewards land. Withdrawable to a TRC20 or BEP20 address; minimum withdrawal 10 USDT; withdrawals are reviewed and paid by the operator.
Reward
A marketing payment made by the project running the program, disclosed as such on the program page. Paid in USDT; no claim step; nothing for holders to sell at claim.
Supported exchanges
Exchange
Status
Why
MEXC
Live (first exchange)
Its API exposes KYC status, UID and key permissions, which strict verification needs.
Others
Planned
Added when they can be verified as strictly. Each program states its exchange on its program page.