Base first
Base Mainnet is the home network for the T5D token.
Token Economics
Token Utility
How T5D utility connects support quality, provider capacity, and ecosystem participation — a token built around real support activity.
Official Visual Language
One mark. A complete support system.
The supplied T5D icon family gives the T5D utility a consistent visual vocabulary: support, community, intelligence, security, education, and the T5D core.
01 / Direction
Utility that grows with real support.
T5D's direction is set: a support-first ecosystem with a token that ties community contribution to the network.
Omnichain next
Expansion to other chains follows as interoperability and security work lands.
Support before utility
Token utility grows with real support activity, so value follows real work.
02 / Proposed Utility Loop
Support work first. Coordination layer later.
The proposed model treats the future token as economic glue around support demand, decentralized AI capacity, human quality review, and verified participation.
1
Support demand
dApps and communities define support needs through future service arrangements. Pricing, service levels, and settlement assets are set per arrangement.
2
Decentralized AI nodes
Community-run AI nodes could accept support work and contribute model capacity. Node requirements, security stake, and compensation are defined as the network launches.
3
Human quality assurance
Human validators could review quality and disputed outcomes. Selection, evidence, quorum, appeals, and rewards are defined as the network launches.
4
Proof of Support records
Verified assistance, useful knowledge, education, and resolution quality could become the basis for future recognition and utility.
03 / Support-Quality Adjudication
Fast path for routine work. Humans for disputed verdicts.
This is the control model guiding the protocol. Automated analysis may help route work or trigger review, but it must not directly slash a node or validator.
User-rating fast path
A user rating and basic outcome signal could enable fast-path settlement when the signals align within pre-defined confidence bounds.
- Fast settlement is conditional, not automatic entitlement.
- Rating manipulation and repeat-account patterns need monitoring.
- Thresholds, reward release, and audit sampling are set at launch.
Sentiment as audit trigger only
Automated sentiment analysis could flag an interaction for audit, but sentiment confidence is capped and cannot directly slash.
- Models can be wrong across language, culture, and context.
- Audit-rate, model choice, confidence caps, and retention are set at launch.
- Human review remains the source of final disputed judgment.
Random human peer review
Randomly selected human validators could determine final disputed verdicts through encrypted or commit/reveal review.
- Appeal rights, evidence standards, quorum, and escalation bonds are set at launch.
- Validator selection must address collusion and concentration.
- Severity-based penalties are only illustrative design options.
Guardrail: Sentiment analysis is an audit trigger only. It cannot directly slash, blacklist, or determine a final disputed verdict.
04 / B2B Service Access
Make service access legible before making token access mandatory.
dApp service access is built around operational commitments rather than fixed token thresholds. Exact bands, savings, service levels, and margin tests are set at launch.
Pay-as-you-go
USD or stablecoin-denominated service pricing with no long-term commitment. Exact service units and rates are set at launch.
Volume / prepaid
Discounts could reflect monthly volume or prepaid service commitments, subject to positive contribution margin.
Annual commitment
Enterprise service levels could use negotiated annual commitments and documented operational requirements.
Optional T5D participation
A token-linked rebate and participation layer arrives once liquidity, custody, and margin foundations are in place.
Commitment ≠ stake
Customer service commitments and deposits must remain separate from node or validator security stake.
No bundled governance
Service access should not grant control over validator selection, slashing, treasury, bridge security, or monetary parameters.
Margin gate
Any discount, rebate, burn, or treasury allocation must come after provider costs and operating requirements are covered.
05 / Initial Distribution
A balanced supply built for the long run.
Total supply is capped at 1,000,000,000 T5D. The allocation rewards the community, funds the work, and keeps the network healthy.
| Allocation | Share | Units | Release | Role |
|---|---|---|---|---|
| Node Mining & PoSpt Rewards | 40% | 400,000,000 | Long-duration emissions tied to verified support activity. | REWARDS |
| Private / Strategic Rounds | 10% | 100,000,000 | Lockup with linear release. | STRATEGIC |
| Community Funding | 7% | 70,000,000 | Early community access with staged release. | COMMUNITY |
| Ecosystem & Growth | 18% | 180,000,000 | Grants, partnerships, and ecosystem programs. | GROWTH |
| Core Team & Contributors | 15% | 150,000,000 | Extended lockup and vesting. | TEAM |
| Public Sale / Liquidity | 5% | 50,000,000 | Public access and market liquidity. | LIQUIDITY |
| Foundation / Treasury | 5% | 50,000,000 | Reserve for long-term stewardship. | RESERVE |
Supply is hard-capped on-chain at 1,000,000,000 T5D, with each allocation minted only when it is needed.
Proposed Allocation
STRUCTURE
One token. A full community build.
A visual look at the current proposed structure behind T5D—balancing community rewards, development, participation, liquidity preparation, and long-term stewardship.
1BT5D SUPPLY CAP
Community rewards
Future node mining and Proof of Support participation.
Ecosystem & development
Growth programs, partnerships, and building the support layer.
Team & contributors
Core builders and the people moving the work forward.
Strategic participation
Future aligned participation with long-term release planning.
Community Funding
Early community access.
Public sale & liquidity
Future public access and liquidity preparation.
Treasury
Longer-term stewardship and operating resilience.
The allocation is designed to connect the community, the work, and the infrastructure needed to grow T5D.
Proposed Infrastructure
OPERATING MODEL
Support in. Shared capacity out.
A simple view of how T5D is designed to connect support agents, future node capacity, service and DeFi rails, human review, and the wider community.
Support demand
Questions and requests from users, communities, and dApps.
Support agents
AI and human-assisted pathways focused on useful resolution.
T5D support layer
Shared records, support tooling, and proof-of-support direction.
Future node capacity
Community-contributed compute and support capacity.
Human review
Review and learning loop for outcomes that need another look.
Service & DeFi rails
Future settlement, access, and utility design as the system matures.
Community ecosystem
Participants, builders, and future rewards aligned around useful support.
T5D keeps support moving.
People and bots ask for help. Support agents create useful outcomes. Future node operators add capacity, while the T5D shield helps keep the service path clear around a future DeFi and service platform.
People & bots need help
Questions, requests, and support needs enter the path.
Support agent
Guides the request toward a useful next step.
Successful support data
Helpful outcomes build a proposed Proof of Support signal.
Future node operator
Adds compute or support capacity; proposed reward signals follow useful work.
FUTURE DEFI / SERVICE PLATFORM
T5DSUPPORT PATHClear access · support context · future settlement design
Support path
Requests and outcomes move through the T5D layer.
Capacity path
Future nodes add scalable help where it is needed.
Reward signal
Useful contribution can inform future recognition design.
Human backstop
Quality review remains available when more context is needed.
How the pieces connect
One request. Three connected loops.
Each support request is intended to move through a practical work loop, a quality loop, and a future service loop—so the people using T5D see helpful support while the system learns where more capacity is useful.
Agent receives the request
The support agent understands the question, gathers context, and identifies the help or capacity needed.
INPUT: support requestT5D routes the work
The support layer records the task and can match compatible future capacity to the part of the work that needs it.
OUTPUT: capacity requestNodes contribute capacity
Future community nodes can provide compute, model capacity, or support assistance and return a work result.
OUTPUT: work resultQuality closes the loop
Outcome signals guide improvement. Human review is available for work that needs a closer look.
OUTPUT: verified signalService rails record the value
Future service and DeFi rails can support access, usage records, and settlement design as the ecosystem matures.
OUTPUT: service recordAgents and nodes
Agents shape the task. Nodes add capacity. The result returns to the support experience.
Signals and review
Useful outcomes build a feedback trail; exceptions can move toward human review and improvement.
Access and settlement
Future rails connect service use to access, reconciliation, and longer-term capacity planning.
This is the direction for the infrastructure. The focus is simple: make support more useful, capacity more connected, and participation easier to understand.
06 / Pricing
One fixed price, clearly stated.
Community Funding runs at a single fixed USDC price for everyone, with full details published on the Community Funding page at launch.
$0.01 per T5D
One fixed USDC price for every contributor.
70,000,000 T5D
7% of total supply is set aside for Community Funding.
One official route
The contract, wallet connection, and terms all go live together on the Community Funding page.
07 / What Community Funding Supports
Fuel for the build-out.
Community Funding powers T5D's support infrastructure and operating foundation.
Product development
Engineering, design, testing, security, and documentation for the T5D support platform.
Cloud, data, and agents
Hosting, data access, APIs, and the AI agent usage that powers support.
Equipment and software
Hardware, testing environments, and the software tools the work runs on.
Specialists and licensing
Qualified contributors, software licensing, and professional services as T5D scales.
Early liquidity
Building the foundation for healthy, lasting market liquidity.
08 / What's Next
The next build steps.
The core design is in place. Here is where the work is headed, and the safeguards built into it.
- Reward design across AI nodes, human validators, and users.
- Base deployment and cross-chain expansion.
- Service pricing and dApp settlement.
- Governance and community voting.
- Privacy: consent, data minimization, and encryption for support conversations.
- Sybil resistance: ratings, rewards, and identities that can't be cheaply duplicated.
- Collusion resistance: randomized commit/reveal review and clear evidence trails.
- Fair appeals: escalation, deadlines, and reversible decisions.
- Human backstop: sentiment signals never act alone.
Join Early
Back the build.
T5D's utility grows with the people who show up first. Join Community Funding to get in early.