Условия обслуживания ToFee Protocol
1. Non-Custodial Protocol & Zero-Custody Architecture
ToFee operates strictly as an autonomous, non-custodial decentralized resource distribution protocol built on TRON's native Stake 2.0 smart contract layer. ToFee never requests, stores, or accesses user private keys, seed phrases, or wallet spending permissions.
2. Key Definitions & Terminology
The computational resource required by the TRON Virtual Machine (TVM) to execute smart contract transactions like TRC-20 USDT.
TRON's native protocol mechanism allowing temporary allocation of energy resources without transferring underlying TRX ownership.
ToFee's automated on-chain gateway that monitors incoming TRX deposits and executes sub-3s autonomous delegation.
Custodial platforms (e.g. Binance, OKX, Bybit) that broadcast withdrawals from pooled custodial hot wallets.
3. Energy Allocation, Rates & Validity Duration
Energy delegation is automatically triggered upon detecting TRX deposits to the designated recharge address:
- 15-Minute Flash Plan (2.5 TRX): Delegates 65,000 Energy for 1 instant USDT transfer, valid for 15 minutes.
- 1-Hour Standard Plan (3.0 TRX): Delegates 65,000 Energy for 1 USDT transfer, valid for 1 hour.
- Transfers to Empty Wallets (131K Energy): Sending 2x the standard deposit amount delegates 131,000 Energy to cover new account contract creation.
⚠️ Note: Once the rental duration expires, unused resources automatically reclaim per TRON blockchain rules. Users are responsible for broadcasting transfers within the active window.
4. Strict Prohibition of Direct Centralized Exchange (CEX) Deposits
Users MUST only deposit TRX from personal self-custody wallets (such as TronLink, Trust Wallet, Bitget Wallet, or Ledger).
Deposits broadcast directly from centralized exchanges will result in energy being delegated to the exchange's pooled hot wallet. ToFee is not liable for misdirected delegations resulting from CEX withdrawals.
5. Developer API & Enterprise Service Guidelines
Integration with the TronMax API V1 is subject to the following developer terms:
- Developers are strictly responsible for securing their x-api-key.
- Bulk order endpoints support up to 20 receiver addresses per single request.
- Abusive request rates or unauthorized vulnerability testing will result in immediate API key suspension.
6. Blockchain Irreversibility & Refund Policy
All confirmed on-chain resource delegations are final and non-refundable. In rare network failure events, unfulfilled orders will be refunded back to account credits following automated audit verification.
7. Network Parameter Updates & Terms Amendments
TRON DAO committee proposals may adjust network fee formulas over time. ToFee dynamically adapts its rates accordingly. Continued usage signifies acceptance of updated terms.