TrueCash Whitepaper

1. Legal & Compliance

1.1 Issuer Information

TrueCash Protocol is an independent, decentralized open-source software project. As of the date of this whitepaper, it operates without a centralized corporate entity. Protocol governance and parameter management are performed by the core developer team, with a planned transition to a Decentralized Autonomous Organization (DAO) following the launch of Phase 3 (Layer 1 migration).

1.2 Regulatory Stance

TRUECASH is designed as a utility token to access and pay for services within the TrueCash ecosystem (e.g., relayer rewards, future protocol fees). It is not structured as an investment contract, security, or equity interest in any entity. TRUECASH does not represent a share in any company and does not guarantee dividends, profit shares, or fixed returns.

This document does not constitute investment, legal, or tax advice. Participants should seek independent professional advice and ensure compliance with applicable laws in their jurisdiction.

2. Problem Statement

Web3 onboarding remains a major barrier to mainstream adoption. Users must:

• Acquire and manage native L1 gas tokens (e.g., ETH, BNB, MATIC).
• Understand gas prices, slippage, and transaction failure modes.
• Hold multiple assets to perform simple transfers or purchases.

This friction is especially problematic for micro-payments and small-value P2P transfers, where gas can exceed transaction value. TrueCash aims to abstract away gas complexity so users can transact using only TRUECASH, while relayers handle BNB gas payments on their behalf.

3. Technical Architecture: Zero-Gas Meta-Transactions

TrueCash removes the requirement for end users to hold BNB by using EIP-712 typed data signatures and a relayer (Paymaster) architecture, rather than full ERC-4337 Account Abstraction, to maintain broad wallet compatibility and lower integration overhead.

3.1 Components

• TRUECASH Token Contract (BEP-20): Standard transferable token with no mint function.
• TrueCashPaymaster.sol: Smart contract that holds BNB reserves to pay L1 gas fees, verifies EIP-712 meta-transaction signatures, executes TRUECASH transfers, and distributes rewards to relayers from the Miner Yield Pool.
• Relayer / Node Operator Software: Off-chain services that query the TrueCash mempool API for pending meta-transactions, package signatures into on-chain transactions, and submit them to BSC to collect TRUECASH rewards.
• Mempool API: Off-chain REST API that receives, validates, and queues signed meta-transactions.

3.2 Transaction Flow

1. Signature Creation: A user constructs a transfer intent and signs an EIP-712 typed data message using their EOA (e.g., MetaMask). This is off-chain and incurs no gas cost.
2. Mempool Submission: The signed meta-transaction is submitted to the TrueCash mempool API.
3. Relayer Execution: Relayer nodes query the mempool, select pending meta-transactions, construct a standard BSC transaction calling TrueCashPaymaster.executeMetaTx(...), and pay the BNB gas fee.
4. Settlement & Reward: The Paymaster contract verifies the EIP-712 signature and nonce. Upon successful verification, the contract transfers TRUECASH from sender to recipient and rewards the relayer with TRUECASH from the Miner Yield Pool.

3.3 Replay Protection & Anti-Spam

EIP-712 domain separators include chainId and contract address. Each user address maintains a strictly incrementing nonce in the smart contract. The Mempool enforces rate-limiting per address, and minimum transaction size thresholds prevent economically irrational spam.

3.4 Staking, Yield, and Zero-Gas Tiers

To access the Zero-Gas Paymaster and prevent token-cycling Sybil attacks, users must stake their TRUECASH in the TrueCashStaking vault. This inherently restricts the circulating supply and mathematically stabilizes the ecosystem.

Users who stake earn real-time Yield (APY) fueled by the Treasury, plus daily Zero-Gas transaction allocations based on their Tier:

• Tier 1 (Casual): Stake 2,000 TRUECASH → 5 Free Txs / Day
• Tier 2 (Pro): Stake 5,000 TRUECASH → 15 Free Txs / Day
• Tier 3 (Whale/Game Studio): Stake 10,000 TRUECASH → 50 Free Txs / Day

Large enterprise partners (e.g., integrated Game Studios) can bypass these retail staking tiers via an Admin Custom VIP Limit mapping within the Paymaster contract, enabling massive throughput for their player bases.

3.5 Sybil Protection & 72-Hour Unbonding

To mathematically eliminate exploiters attempting to cycle 2,000 TRUECASH across infinite wallets, the TrueCashStaking contract enforces a strict 72-hour unbonding cooldown. When a user requests to unstake, their funds are locked in a pending state for 3 days, instantly dropping their Zero-Gas Tier and neutralizing any profitability of a token-cycling attack.

4. Tokenomics

The total supply is permanently fixed at 10,000,000,000 TRUECASH.

4.1 Supply & Vesting Schedule

• Circulating Supply at TGE: 15% (Presale tokens + Initial LP) minus any LP locks.
• Team Vesting: 15% subject to a 6-month cliff, followed by a 24-month linear unlock.
• Miner Yield Emissions: 30% distributed over ~10 years. (illustrative: Year 1: 10% of pool, Year 2: 12%, with adjustments based on network volume and governance).
• Treasury: 40% unlocked at TGE, governed by the core team multisig with public spending reports, pending DAO transition.

4.2 Presale Mechanics & Fund Distribution

TrueCash conducts a two-phase presale to seed initial liquidity on PancakeSwap. 100% of presale BNB proceeds are allocated via the distributeFunds() function in the TrueCashPresaleV2.sol contract as follows:

• 30% - Paymaster Wallet: Sent to the Zero-Gas Paymaster contract to subsidize network gas fees. Withdrawal of Paymaster BNB reserves is restricted by a 30-day timelock.
• 40% - Liquidity Wallet: Paired with TRUECASH on PancakeSwap to create the initial trading pool. LP tokens will be locked via a third-party locker (e.g., PinkSale) for 12 months; lock transaction and address will be published post-presale.
• 30% - Operations Wallet: An allocation for marketing, technical partnerships, and exchange listing fees. Operations Wallet is a sub-allocation of the Protocol Treasury and subject to the same multisig governance.

Presale tokens are fully unlocked at TGE to provide immediate market liquidity. The team acknowledges this increases short-term sell pressure risk and is mitigated by locked LP and a multi-year miner emission schedule.

5. Smart Contracts & Security

All TrueCash smart contracts are implemented using industry-standard OpenZeppelin libraries where applicable. Contracts are intended to be open source and publicly verifiable on BscScan.

• Open Source Repository: GitHub
• Audits: An independent security audit is planned for Q4 2026 (target: October-November 2026); audit reports will be published upon completion. An ongoing bug bounty program is also planned.
• Governance & Access Control: Currently, critical parameters (e.g., relayer reward rates, treasury spending) are controlled by a 2-of-3 multisig operated by the core team. In Phase 3, governance over treasury allocations, emission parameters, and protocol upgrades is intended to transition to a DAO, subject to token-holder voting. The Paymaster Contract logic is immutable, and BNB withdrawals are restricted by a 30-day timelock.

6. Risk Factors

Participation in the TrueCash ecosystem involves significant risks. Key risks include, but are not limited to:

• Smart Contract Risk: Despite using standard libraries and planned audits, undiscovered vulnerabilities may exist and could result in partial or total loss of funds.
• Relayer Centralization Risk: In early phases, the decentralized relayer network may consist of a limited number of node operators. While the core team operates a robust fallback relayer server to guarantee transaction processing if community nodes go offline, this introduces a temporary point of centralization until the network matures.
• Market Volatility: TRUECASH's price is subject to extreme volatility. Miner profitability depends on both the price of TRUECASH and the cost of BNB gas.
• Regulatory Risk: Changes in global cryptocurrency regulations may affect the operation of the TrueCash marketplace or the classification of the token.
• Execution Risk: Roadmap delays or failures during the Phase 3 Layer 1 migration could impact token utility.
• Liquidity Risk: Initial trading liquidity depends on presale participation and LP locking; low liquidity may result in high price impact and slippage.

7. Roadmap