TIDECOIN
Get TDC

Tidecoin Development Roadmap

Tidecoin's roadmap has three phases. Phase 1 covers the live genesis-era design: Falcon-512 signatures and YespowerTIDE mining. Phase 2 covers the built-but-not-yet-activated feature set tied to AuxPoW activation: merged mining, additional signature schemes, OP_SHA512, and witness v1. Phase 3 covers longer-term ideas that should be treated as planning, not whitepaper-canonical release commitments.

// status legend
LiveActive on mainnet
BuiltCode complete, tested, awaiting consensus activation
PlannedIn design or development
// phase 1 · foundation

What has Tidecoin already delivered?

  1. Falcon-512 signaturesDefault signature scheme securing all transactions from December 27, 2020
    Live since genesis
  2. YespowerTIDE miningCPU-friendly PoW with N=2048, r=8
    Live since genesis
  3. SegWitActive from block 1
    Live
  1. PQHD wallet designHardened-only derivation with SHA-512-based KDF
    Live
  1. Additional signature schemesFalcon-1024 and ML-DSA-44/65/87
    Built, activate with AuxPoW
  2. AuxPoW merged miningScrypt-based merged mining with Litecoin, Chain ID 8
    Built, activates with AuxPoW
  3. OP_SHA512 and witness v1SHA-512 script support and 64-byte witness hashing
    Built, activate with AuxPoW
  4. Strict PQ validationLegacy-vs-strict transition tied to AuxPoW
    Built, activates with AuxPoW
  5. Longer-term ideasAny release/version roadmap beyond the whitepaper should be sourced separately
    Planning only

Operational track-record claims on the public site should point to /status for visible evidence and timestamped verification.

// phase 2 · auxpow activation

What does the AuxPoW activation unlock?

All Phase 2 code is already implemented and tested. Phase 2 is a single consensus-height activation that simultaneously enables:
01

Scrypt merged mining

  1. What it does

    Transition from standalone YespowerTIDE to Litecoin-secured merged mining

  2. Why it matters

    Substantial increase in 51% attack cost via Litecoin hashrate leverage

02

Multi-scheme signatures

  1. What it does

    Falcon-1024, ML-DSA-44/65/87 become available for new addresses

  2. Why it matters

    Cryptographic agility — backup schemes if one is compromised

03

Witness v1 activation

  1. What it does

    SHA-512-based 64-byte script hashing with q1... addresses

  2. Why it matters

    256-bit PQ security vs 128-bit from SHA-256

04

OP_SHA512 activation

  1. What it does

    SHA-512 opcode available in Script

  2. Why it matters

    Post-quantum hash operations in smart contracts

05

Strict PQ validation

  1. What it does

    Legacy Falcon format rejection

  2. Why it matters

    Tighter security margins with standard PQClean bounds

Implementation detail: All features are gated behind nAuxpowStartHeight in consensus parameters. Currently set to AUXPOW_DISABLED on mainnet and active at block 1000 on testnet. Activation height will be set via a coordinated node software release.

// phase 3 · long-term

What is planned for Tidecoin's future?

01Planned

Hardware wallet integration

FALCON-512 and ML-DSA support for Ledger/Trezor secure elements

02Planned

Cross-chain bridges

Quantum-secure bridge protocols using ML-KEM key exchange

03Planned

SIMD-accelerated verification

Optimized signature verification for high-throughput nodes

04Planned

iOS wallet

Native App Store wallet

// roadmap faq

Roadmap FAQ

All FAQ

Is Phase 2 code already written?

Yes. All AuxPoW, multi-scheme, witness v1, OP_SHA512, and strict PQ validation code is fully implemented, compiled, and tested with unit tests and functional tests. Phase 2 is purely a consensus activation — setting a block height at which the features go live on mainnet.

When will AuxPoW activate?

The activation height will be set through a coordinated node software release with the mining community. All features are already testable on testnet (active at block 1000).

Will I need to update my wallet for Phase 2?

You will need to update to the latest node software release that includes the activation height. Existing keys and addresses will continue to work — no wallet migration is required.