The Post-Quantum L1
Built for Long-Term Value

Executive Summary

TCC Chain is a Byzantine Fault Tolerant (BFT) Proof-of-Stake Layer-1 blockchain built from first principles for the post-quantum era. It prioritizes three properties most chains compromise.

1. Sustainable economics — fee-funded validator rewards extend indefinitely beyond initial pool depletion.
2. Structural decentralization — economic incentives naturally distribute validator count rather than aggregate stake.
3. Future-proof architecture — state migration framework and reserved extension fields enable governance-driven upgrades without breaking existing users.

Token Economics

2.1 Supply & Distribution

All allocations are enforced at genesis through deterministic hash computation. Each role address is independent with optional multi-signature governance (Wave 2 enhancement).

2.2 Block Reward Schedule

Block rewards emit from the Reward Pool (not minted from thin air), ensuring strict adherence to the 100B hard cap.

The 700M pool includes approximately 11% buffer above the 630M asymptotic emission, providing a safety margin against minor parameter adjustments.

2.3 Fee Distribution (3-Way Split)

Every transaction fee splits immediately upon block production:

Validator share:     75%   →  Block producer's owner address
Developer share:     20%   →  Foundation-controlled developer wallet
Pool refill:          5%   →  Refills the Validator Reward Pool
─────────────────────────────────────────────────────────────────
Total:              100%

This sustainability mechanism makes TCC the first Layer-1 designed to operate indefinitely beyond pool exhaustion, rather than relying on inflation to subsidize validators.

Staking Returns

3.1 Delegator APY Formula

A delegator's annual percentage yield depends on three measurable factors:

delegator_APY = base_APY × validator_uptime × (1 - effective_commission)

Where:
  base_APY = (block_reward × blocks_per_year) / network_total_active_stake
  effective_commission = min(declared_commission, uptime_tier_cap)

3.2 Uptime-Based Commission Cap

Delegator protection mechanism — validators cannot extract high commissions while delivering poor service:

Excess commission auto-redirects to delegators. This prevents high-commission, low-quality operator behavior.

3.3 Operator vs Delegator Economics

For an operator running their own validator node, the economic advantage compounds with attracted delegations. A node with 100k self-stake and 5M delegations earns approximately 6× the base APY on its self-stake, through commission income on delegator pools.

3.4 Concrete Return Examples

Year-1 estimates assuming network active stake of ~30B TCC: base_APY ≈ 0.525%

Decentralization Mechanisms

4.1 Anti-Concentration Unbonding Tiers

When unstaking, lock-up period scales with the validator's network share at the time of unstaking:

This discourages concentration: delegators staking with mega-validators face longer lock-ups, making such validators less attractive over time. The penalty applies symmetrically to the validator's own unstaking, preventing concentrated operators from gracefully exiting.

4.2 Natural Economic Equilibrium

The fee structure creates inherent pressure toward distributed node operation:

Running own node:  100% reward on self-stake (no commission cut)
Delegating:         95% of stake-share reward (5% commission to validator)
─────────────────────────────────────────────────────────────────────────
Net advantage:      ~5% per year for running own node

For capital holders above $10,000 worth of TCC, the savings from running their own validator typically exceed monthly infrastructure costs. This creates organic incentive for new validators to spin up, rather than concentrating delegation onto fewer operators.

4.3 Comparison to Other Networks

Security & Reliability

5.1 Cryptographic Foundation

• Post-quantum signatures: Dilithium3 (CRYSTALS-Dilithium, NIST PQC Standard) for transaction signing and validator authentication
• Cryptographic hash: BLAKE3 throughout for state roots, block hashes, and Merkle tree computation
• Forward security: signature scheme resistant to quantum computer attacks anticipated within 10-30 years

5.2 Byzantine Fault Tolerance

• 2/3 quorum requirement: protocol halts (preserves safety) rather than fork in partition scenarios
• 100% slash on equivocation: validators signing conflicting blocks lose entire stake
• 1% slash on downtime: validators offline beyond grace period face proportional reduction
• No autonomy bypass: solo nodes cannot produce blocks without quorum, preventing minority forks

5.3 State Integrity

• Self-healing boot integrity check: every node validates database consistency at startup, detecting tampering before producing blocks
• State migration framework: schema versioning enables protocol upgrades without losing existing state
• Cross-node determinism: tested live with 3-node devnet showing byte-identical state roots across all validators

5.4 Audit Status

• External pre-launch audit: planned 4-6 weeks before mainnet, conducted by reputable firms (Trail of Bits, ChainSecurity, OtterSec, or Halborn)
• Open-source codebase: full source available for community review
• Test coverage: 1,036+ tests across 30 test suites, 100% passing, zero regressions

Smart Contract Platform

6.1 Native Standards (Pre-Launch Ready)

6.2 VM Capabilities

• Cross-program invocation (CPI): contracts can call other contracts atomically, with rollback support
• Per-call rollback: callee writes discard atomically on revert
• Account ACL: Solana-style declared account list per transaction
• Gas accounting with refund: unused gas refunded to caller
• Up to depth 4 nested calls: prevents call stack exhaustion attacks

6.3 Performance Baseline

Measured on standard hardware (release build):

• Token transfer: ~140 microseconds per operation
• Token batch transfer (64 items): ~22 microseconds per item (33× speedup)
• NFT mint: ~160 microseconds per operation
• Marketplace buy (3-leg CPI): well within 10s block budget

Investment Opportunity

7.1 Allocation Mechanisms

Sales Allocation (IDO/IEO)

• Total: 15B TCC available
• Vesting: 6-month cliff + 24-month linear
• Earliest unlock: 6 months post-mainnet
• Vesting tokens may be stake-able during lock-up (design pending)

Secondary Market (Post-Mainnet)

• Liquidity Bootstrap pool: 10B TCC seeded for DEX
• Expected DEX deployment: 3-6 months post-mainnet
• Permissionless trading after deployment

Airdrop Eligibility

• Community pool: 25B TCC distributed via campaigns
• Criteria: testnet participation, early dapp deployment, early staking
• First campaign expected within 3-12 months post-mainnet

Strategic Reserve Participation

• Total: 20B TCC managed
• Foundation-controlled with multi-signature governance
• Long-term aligned holders

7.2 Return Pathways

7.3 Comparison to Industry Peers

Risk Factors

8.1 Technical Risks

• Pre-audit codebase: external security review scheduled before mainnet but not yet completed. Critical vulnerabilities could emerge.
• First mainnet launch: complex coordinated event with 21+ independent operators. Genesis hash mismatch or operator failure could delay launch.
• Smart contract bugs: while reference contracts are tested, third-party application code carries normal smart contract risk.

8.2 Economic Risks

• APY decline with adoption: base APY shrinks as more TCC stakes. Early high-APY periods are temporary.
• Reward pool exhaustion timing: depends on actual block production rate and fee volume. Variance from 25-year projection possible.
• Liquidity constraints: limited initial DEX liquidity may cause price volatility. Exit liquidity unavailable until liquidity bootstrap pool deploys.

8.3 Decentralization Risks

• No hard concentration cap at launch: relies on soft incentives plus foundation behavior. If foundation delegates concentrated, a single validator could exceed 33% threshold.
• Sybil attack potential: nothing prevents a single operator from registering multiple validator slots. Hard cap mechanisms deferred to governance vote post-launch.

8.4 Regulatory Risks

• Securities classification uncertainty: TCC token classification varies by jurisdiction. Consult local legal counsel.
• Geographic restrictions: some jurisdictions restrict participation. Foundation will publish jurisdictional limitations before sales open.
• Tax implications: staking rewards may be taxable income depending on jurisdiction.

8.5 Operational Risks

• Validator slashing: delegators face proportional slash if their chosen validator equivocates (100%) or experiences extended downtime (1%). Diversification across 3-5 validators reduces risk.
• Smart contract upgrades: governance-activated upgrades may change parameters. All changes require 2/3 stake vote with 14-day timelock.

Development Roadmap

9.1 Pre-Launch (Current)

Status: 14 of 17 protocol items shipped, test suite 1,036+ passing.

Remaining work to mainnet (estimated 9-13 weeks):

• Final protocol hardening (10-12 days code)
• Codebase refactor (Layer 1/2/3 separation)
• External security audit (4-6 weeks)
• Operator recruitment + multi-signature setup
• Public testnet dry-run
• Coordinated genesis launch

9.2 Mainnet Phase 1 (Launch + 6 months)

Focus: stability, monitoring, ecosystem bootstrap.

• 21 genesis validators producing blocks
• Foundation 6-role allocation distribution begins
• Reference applications deployable day one
• Public block explorer and validator dashboard
• Concentration metrics published weekly

9.3 Mainnet Phase 2 (6-18 months)

Focus: ecosystem growth, governance activation.

• DEX deployment (liquidity bootstrap activated)
• TIP-Vesting contract live (founder enforcement)
• TIP-Soulbound reputation system
• Validator scoring dashboard with auto-recommendation
• Optional governance-vote activation of: hard concentration cap, vote inclusion bonus, 90-day liveness window

9.4 Mainnet Phase 3 (18+ months)

Focus: maturity, advanced features.

• Cross-chain bridge infrastructure
• Native oracle for price feeds
• Stablecoin reference contract
• Advanced staking patterns (liquid staking, restaking)
• On-chain governance framework formalization

Frequently Asked Questions

Key Specifications