Skip to content

Roadmap

tgibbsz32 edited this page Oct 25, 2026 · 4 revisions

ForgeCoin native-network roadmap

Planning baseline: October 25, 2026. This roadmap contains actual native L1, wallet, mining, explorer, pool and governance implementation workstreams. It intentionally omits speculative trading/token-bridge/yield projects, and does not announce target launch dates.

Stage 1 — Approve the standalone PoW mainnet (release-blocking)

  • Settle/verify permanently unspendable genesis output and zero allocated founder/team/ICO premine. If current genesis cannot be proved safe, obtain explicit approval of a replacement and rerun all affected tests.
  • Reconcile 50M primary-emission reference, 0.20 FRG perpetual tail, 100% miner subsidy, block-weight penalties, exact atomic precision and 60-block coinbase maturity with final release code.
  • Validate proposed 500,000 initial difficulty, 400,000 floor, height-16 progressive LWMA90 bootstrap with native blocks at heights 1–17 and 90–92, adversarial timestamps, alternative branches and restart consistency.
  • Verify distinct prefixes, network UUID, genesis, ports, cross-platform consensus on Windows x64/Linux x86-64/ARM64, chain synchronization, trusted peers and independent review.
  • Publish reproducible signed/checksummed builds, documented rollback and a separately authorized launch procedure. No automatic migration from the old development chain.

Completion gate: independently reviewed candidate genesis and consensus, interoperable validated binaries, finalized chain identity and explicit owner authorization. Not met.

Stage 2 — Release reliable Windows desktop and native wallet

  • Complete native daemon + wallet RPC digest-pinned packaging and Windows Tauri installation.
  • Finish self-custodial wallet creation/restore/send/receive, local node sync, safe child-process handling and recovery.
  • Validate actual Solo accepted block(s) and maturity, with no production data or wallet keys exposed in tests.
  • Validate real compatible third-party Pool accepted/rejected FRG shares, disconnect/reconnect/telemetry, mature allocation/payout evidence using trusted XMRig and isolated infrastructure.
  • Fix miner provenance blocker #95 first; hold the desktop V1 release if Solo or Pool mode is not independently evidenced.

Completion gate: a reviewed downloadable Windows package whose Solo and Pool flows both satisfy release tests. Not met. A publicly hosted official pool is not required just to verify compatibility with an isolated private pool.

Stage 3 — Bootstrap and publish accurate network services

  • Bring up independently operated peers, finish accurate hosted explorer for the approved fresh chain, and test lookup, confirmation, reorg and API safety.
  • Publish correct node/miner connection instructions, verified release downloads, network stats freshness, monitoring, backups and recovery.
  • Retire the old development network only after dependency review, recoverable backup and explicit service transition safeguards.

Completion gate: externally verifiable, secured and correctly identified fresh-network services. Not met; existing hosted explorer currently serves old development data.

Stage 4 — Optional official native FRG pool and tools

  • Validate canonical fresh-chain jobs and RandomX shares (#28, #29, #30), rejecting duplicates, stale submissions, wrong difficulties and cross-worker replays.
  • Complete bounded Stratum networking, durable accounting, canonical-chain/reorg handling, 60-block reward maturity, safe payout authorization and restart recovery.
  • Publish a transparent 1% operator-fee basis and a reviewed payout policy (scheme, rounding, minimum payout, transaction costs).
  • Add optional official-pool selection to Tauri while preserving independent pools and Solo mining.
  • Deliver a live, accurate pool dashboard and independent read-only Pool Observer. Load-test an intended 100-concurrent-worker target before claiming capacity.
  • Private beta, independent audit, monitored deployment and rollback before accepting public miners or coins.

Completion gate: actual accepted shares, chain rewards, accurate miner allocations and verified mature payouts. Not met. Synthetic loopback proof checks are not sufficient.

Stage 5 — Ratify native governance, without changing PoW issuance

  • Complete privacy-preserving miner participation evidence and enforceable FRG governance bond prototype.
  • Resolve the proposed ten-seat chamber's constituencies, seat allocation, founder participation (if any), elections, terms, quorum, checks/appeals and conflict rules.
  • Publish and independently review the charter, security design and decision enforcement before any binding election.
  • Require independent full-node software adoption for consensus upgrades irrespective of project governance outcomes.

Completion gate: explicit charter ratification, proved technical eligibility, verified independent election process and published limited authorities. Not met. Native bonding is not staking yield or proof-of-stake consensus.

Explicitly excluded from this committed roadmap

No treasury-at-genesis premine, secondary mining token, Solana wrapper/bridge, smart-contract yield or guaranteed exchange liquidity is in the implementation plan being published here. Any later such project needs separate approval and risk analysis.

Detailed references: Owner decisions · Original engineering roadmap · Pool implementation plan.