Proposal for TRUF Token Burn Mechanism on Transactions

General
1

Author: TRUFNATIC
Date: 2025-07-12
veTRUF Locked: 10,000.

  1. Summary
    Implement a 0.01% token burn on every TRUF transaction to reduce circulating supply and enhance long-term token value.

  2. Problem / Opportunity
    The TRUF token, powering the Truflation Stream Network, has a circulating supply of approximately 350 million tokens, with a total supply of 1 billion. High token supply can dilute value and reduce scarcity, potentially limiting price appreciation. A small burn per transaction could gradually reduce supply while maintaining network functionality.

  3. Proposed Action

  • Implement a 0.01% token burn on every TRUF transaction (e.g., data consumption, staking,) across the Truflation Stream Network.
  • Integrate the burn mechanism into the smart contract, automatically sending 0.01% of each transaction to an irretrievable “eater address.”
  • Announce the mechanism via official Truflation channels (website, Discord, X) post-implementation.
  1. Rationale
  • Token Value: Reducing circulating supply increases scarcity, potentially supporting price stability and growth, as seen in other projects like Crypto.org (100M CRO burned annually).
  • User Growth: A deflationary mechanism signals long-term commitment to token holders, encouraging retention and attracting new investors.
  • Ecosystem Integrity: Minimal burn rate (0.01%) ensures no disruption to data provider incentives or governance, maintaining TSN functionality.
  1. Success Criteria
  • Token Supply Reduction: Achieve a 0.5-1% reduction in circulating supply within 12 months (1.75-3.5M tokens).
  • Price Impact: Monitor TRUF price for a 5-10% increase within 6 months post-implementation, compared to market trends.
  • Community Engagement: Increase governance participation by 10% (measured via Snapshot votes) due to heightened interest in tokenomics.
  • Trading Volume: Maintain or increase daily trading volume by 5% within 3 months, indicating sustained user activity.
  1. Dependencies & Risks

  • Dependencies: Requires smart contract development and audit; coordination with exchanges (MEXC, Gate, KuCoin) to ensure compatibility.

  • Risks:

    Smart contract vulnerabilities if not thoroughly audited; mitigated by engaging top-tier auditors (as done for token migration).

    • Market volatility could mask price impact, requiring longer evaluation periods.

  • Mitigation: Transparent communication via Discord and X; phased rollout with community feedback.

  1. Next Steps
  • Week 1-2: Community discussion on governance forum; collect feedback.
  • Week 3: Snapshot vote for approval.
  • Week 4-6: Smart contract development and audit.
  • Week 7: Test burn mechanism on testnet.
  • Week 8: Deploy on mainnet; announce via Truflation.com, Discord, and X.
  • Ongoing: Monitor burn rate, price, and community metrics quarterly; report to token holders.
2

Hey @Trufnatic one thing is unclear. Are you suggesting this mechanism is built into the token contract itself, or in the nodes that process transaction fees for requesting data and indexes?

3

Hello @cameronlee ! Thanks for replying.
I’d say ideally, implementing this in the token contract itself would be perfect, however I`m aware it would require token swap which could be a hassle.

4

ok got it. our token contract is immutable so we cant change that. even if we could, i wouldn’t want to build it into every single transaction. but if you’re ok letting that go then let’s discuss what we can do.

i do think its worth considering an Ethereum-style burn mechanism that happens during transactions on the nodes themselves. i’m not sure how effective it will be at reducing supply, but it is worth looking into.

it would be a tradeoff between:

  • this proposal would want a meaningful reduction of supply
  • network participants (data providers, etc) want maximum payment per transaction

this isn’t something we can implement right now. but we can make it a part of our discussions around incentives and transaction fees. why dont we leave this topic open for now and we can update it as things start to solidify.