TRNToken

🪙 TRN Token

The TRN Token is the core utility currency of the TRN platform. It governs economic activity, engagement incentives, content access, and DAO voting. TRN operates as a modified ERC-20 token with critical internal restrictions to maintain fairness, enforce debt reconciliation, and power a seamless web2-style user experience behind a highly structured decentralized architecture.

✅ Key Roles of TRN

TRN is used for:

  • Viewing any post (1 TRN per view)

  • Retrning (curator re-posts, earning credit from original post)

  • Voting in DAO proposals (1 TRN per vote)

  • Subscribing to content (daily renewals, creator-defined price)

  • Boosting posts (advertising)

  • Gating content via SubscriptionNFT

  • Watching ads or boosted posts to earn TRN

  • Powering the AMM economy (TRN↔BRN, TRN↔USD)

  • Accessing system features (posting, pinning, reporting, moderation hooks)

  • Acting as the platform’s unit of accounting for daily Merkle-based reconciliation

🧠 Core Properties

Property
Description

Symbol

TRN

Decimals

18

Mintable

Yes, only via TRNUsageOracle-approved systems

Burnable

Yes, only through TRNUsageOracle debt reconciliation

Transferable

Yes, but routed through the TRNUsageOracle

Withdrawable

Yes, only after debt reconciliation; up to 333,333 TRN ($1K) per swap (initially)

Exchangeable

Internally via private AMMs: TRN↔USD and TRN↔BRN

All minting, burning, transferring, and withdrawing are mediated through the TRNUsageOracle, ensuring no user interaction causes net-negative balance or exploits the Merkle reconciliation.

🔁 Minting Logic

Minting is allowed only via the TRNUsageOracle as a result of confirmed platform engagement activity.

Examples of actions that trigger minting:

  • A user watching a boosted post (TRN credited after view completes)

  • A creator receiving blessings or retrns

  • DAO rewards or Merkle-based airdrops

Minting rules:

  • Only occurs after debt reconciliation

  • Minting must not violate ±2% price peg enforced by internal AMM (TRN↔USD)

  • Mint cap: 333,333 TRN per swap until the stability pool is fully funded

🔥 Burning Logic

TRN is not permanently destroyed — burning functions as a staking proxy for Merkle tree calculations.

Key rules:

  • TRN is burned via the TRNUsageOracle at time of spend (viewing, boosting, gating, etc.)

  • Burned TRN is locked until the Merkle batch processes at 00:00 UTC

  • View costs, subscription fees, boost campaigns, and downvotes all initiate TRN burns

  • If content is burned (moderation), remaining TRN is returned to booster or DAO

DAO receives TRN from:

  • Content burns

  • Boost campaign burns (e.g., if ad is burned early)

  • View commissions (10% cut on views and retrns)

💡 Transfer Rules

TRN is only transferable through the TRNUsageOracle, which enforces:

  • No transfers if the user has any unclaimed Merkle debt

  • No transfers if the user’s real-time fruit balance < account balance

  • Transfers routed through a simulated ledger to ensure accuracy

  • No self-transfers to evade restrictions

  • Transfers limited to avoid price disruption

  • All transfers logged for indexing and Merkle batching

⛔ Withdrawal Control

Withdrawals (e.g. to fiat or self-custody) are strictly gated:

  • User must have no outstanding debt in the ledger

  • Only real-time fruit-earned balance can be withdrawn

  • Limit: 333,333 TRN per withdrawal (until stability pool is funded)

  • All requests go through a seamless UI (wallet invisible to the user)

  • User KYC and fiat onramp handled per country NFT rules

Withdrawals settle from the system vault only after Merkle reconciliation and debt clearance.

🧾 Usage Ledger (Fruit System)

TRN operates on a fruit balance system:

  • Fruit = pre-authorized usage credit for the day

  • Real-time ledger tracks all TRN usage, earnings, and debits

  • At 00:00 UTC, Merkle tree finalizes account deltas

  • Claims are automatically distributed post-drop

  • If fruit = account balance, user is blocked from further actions until they:

    • Watch boosted content

    • Receive blessings or retrns

    • Top up via fiat

    • Earn TRN from others

Users can never go negative. Attempted actions that would create negative fruit balance are rejected.

🛡️ Debt Enforcement

All user actions are sandboxed to enforce:

  • Real-time balance enforcement

  • No negative usage

  • All credits logged in the ledger

  • All debits settled before TRN is withdrawable or transferred

If the ledger shows a mismatch between actual TRN and earned fruit, the system blocks all outgoing transfers and new engagements.

🧠 AI Rules

  • TRN fraud is detected via AI Bot Verifier

  • Behavior anomalies (mass views, brn manipulation) trigger review queues

  • Bot detection may disable ad view earnings or delay Merkle claims

  • Bots can be silently paused or escalated to DAO/AI moderation

🔧 Governance Integration

  • Voting requires sending 1 TRN to the DAO per proposal

  • Proposals can be triggered by MasterNFT or CouncilNFT

  • No staking, only 1 TRN payment for vote

  • Votes are irreversible

  • Voting weight = participation count, not token weight

📌 Pricing

  • 1 TRN = 1 post view

  • Boosts cost 3× normal rate per view (paid by booster)

  • Users earn 90% of each view price unless burned

  • TRN ≈ $0.003 USD (price anchored by internal AMM)

🧩 Files Used

File
Purpose

TRNToken.sol

Modified ERC20 with hooks for TRNUsageOracle, burn routing, mint delegation

TRNUsageOracle.sol

Enforces all real-time balance rules, ledger simulation, Merkle diff, and debt

FruitBalanceTracker.sol

Tracks ledger of daily fruit debits and credits per user

TRNMerkleBatcher.sol

Runs daily Merkle diff, distributes rewards, handles vault payouts

TRNWithdrawalRouter.sol

Handles TRN off-ramp routing and country-specific KYC

TRNAMM.sol

Anchored internal swap logic for TRN↔BRN and TRN↔USD pools

PreviousToken EconomyNextBRNToken

Last updated