roadmap: public roadmap document with milestones

[satyakwok]

Publish a ROADMAP.md at repo root with the public roadmap — what's planned, what's in progress, what's done.

Why

Devs deciding whether to build on a chain want to see direction. Investors want to see ambition + execution discipline. A single canonical roadmap doc:

• Anchors community discussion
• Gives contributors clarity on where to plug in
• Shows accountability (items move from 'planned' → 'in progress' → 'done' over time)

Scope

• Top-level ROADMAP.md with 4 columns: Done / In Progress / Next / Future
• Reference linked issues for each in-progress / next item
• Quarterly updates (or as material changes happen)

Initial population (drawing from open issues)

• Done: Voyager BFT mainnet activation; cross-chain bridge to Ethereum (Hyperlane); signed releases (cosign + SLSA L3); DEX (UniV2 fork); CoinBlast launchpad; faucet; explorer
• In Progress: EVM value-passing bug fix (EVM: payable internal-call chain reverts at 27k gas on broadcast when msg.value > 0 (eth_call + eth_estimateGas succeed) #580); apply-profile observability (block_executor: per-block apply-phase profile (env-gated) #594 shipped); trie prune cycle tuning (perf(trie): bump TRIE_PRUNE_EVERY 1000 → 5000 #610 shipped)
• Next: stSRX (feat: stSRX liquid staking vault #615), Aave fork (feat: deploy Aave v3 fork on Sentrix as lending primitive #616), Sentrix Names (feat: Sentrix Names (.srx ENS-style naming service) #617), NFT marketplace, LayerZero V2 bridge, public Grafana templates
• Future: Frontier F-3 parallel apply (consensus: Frontier Phase F-3 — real parallel apply (replace F-2 shadow) #618), DAG consensus exploration (research: DAG-based consensus exploration (Narwhal / Bullshark / Mysticeti) #620), grants program, bug bounty (Immunefi)

Acceptance

• ROADMAP.md committed + linked from README

[zp6]

I've submitted a PR to address this: #686

Wallet: zp6