docs: add public ROADMAP.md#686
Conversation
📝 WalkthroughWalkthroughThis PR introduces a public Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@ROADMAP.md`:
- Around line 36-37: Update the "## Contributing" section in ROADMAP.md to
include a clear commitment to update cadence: append a sentence such as "This
roadmap is updated quarterly or when material changes occur." so the "##
Contributing" heading explicitly states the quarterly update commitment
requested in issue `#626`.
- Around line 31-34: Update the "## Long-term" section to include status
indicators and the missing future items: prepend each bullet with the 🔮 Future
emoji (e.g., "🔮 Future - Cross-chain interoperability"), and add bullets for
"🔮 Future - Frontier F-3 parallel apply (`#618`)", "🔮 Future - DAG consensus
exploration (`#620`)", "🔮 Future - Grants program", and "🔮 Future - Bug bounty
program (Immunefi)"; also remove or relocate the duplicate "Immunefi" bug bounty
entry from the Q2 2026 Security section so the Immunefi bounty only appears
under the Long-term/Future list.
- Around line 25-29: Update the Q3 2026 roadmap entries so their status reflects
"Planned" instead of "Future": replace the 🔮 emoji with 📋 for each bullet
under the "## Q3 2026" heading (the bullets "Mainnet stability improvements",
"Mobile wallet SDK", "DEX integration", "NFT support") and append the
appropriate issue references (e.g., add "(`#626`)" or the exact issue
numbers/links) to each item—if "NFT support" maps to the "NFT marketplace" in
issue `#626`, add that reference specifically. Ensure each bullet becomes like "📋
Item description (#[issue-number])" so readers can navigate to the related
issue.
- Around line 6-24: Update the Q2 2026 section in ROADMAP.md to replace the
generic items with the concrete deliverables and issue references from issue
`#626`: list the "Done" items (Voyager BFT mainnet activation, cross-chain bridge
to Ethereum (Hyperlane), signed releases (cosign + SLSA L3), DEX (UniV2 fork),
CoinBlast launchpad, faucet, explorer) with links to their issues/PRs, add the
"In Progress" items including EVM value-passing bug fix (`#580`), apply-profile
observability (`#594` shipped), trie prune cycle tuning (`#610` shipped), add the
"Next" items stSRX (`#615`), Aave fork (`#616`), Sentrix Names (`#617`), NFT
marketplace, LayerZero V2 bridge, public Grafana templates with issue refs, and
add the "Future" items Frontier F-3 parallel apply (`#618`), DAG consensus
exploration (`#620`), grants program, bug bounty (Immunefi) so the Q2 2026 section
matches `#626` and includes traceable issue links.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 40115a48-3d2c-4ab0-b8f1-c6442d74aaab
📒 Files selected for processing (1)
ROADMAP.md
| ## Q2 2026 | ||
|
|
||
| ### Core Protocol | ||
| - ✅ Initial chain launch and token distribution | ||
| - 🔄 Validator staking and delegation | ||
| - 📋 Cross-chain bridge integration | ||
| - 📋 Governance proposal system | ||
|
|
||
| ### Developer Tools | ||
| - ✅ SDK v1.0 (Rust, TypeScript) | ||
| - 🔄 SDK v1.1 (Python, Go) | ||
| - 📋 Smart contract templates | ||
|
|
||
| ### Security | ||
| - ✅ Internal audit | ||
| - 🔄 External audit | ||
| - 📋 Bug bounty program | ||
| - 📋 Formal verification of core contracts | ||
|
|
There was a problem hiding this comment.
Major inconsistency: Missing specific deliverables and issue references from #626.
Issue #626 explicitly requests that roadmap items reference linked issues and include specific deliverables. The current Q2 2026 section contains only generic items without issue links.
According to #626, the roadmap should include:
- 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 (
#580), apply-profile observability (#594shipped), trie prune cycle tuning (#610shipped) - Next: stSRX (
#615), Aave fork (#616), Sentrix Names (#617), NFT marketplace, LayerZero V2 bridge, public Grafana templates - Future: Frontier F-3 parallel apply (
#618), DAG consensus exploration (#620), grants program, bug bounty (Immunefi)
None of these specific items or issue references appear in the current roadmap. Please update Q2 2026 to include the concrete deliverables and issue links specified in #626 to meet the traceability and accountability objectives.
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 8-8: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 14-14: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 19-19: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@ROADMAP.md` around lines 6 - 24, Update the Q2 2026 section in ROADMAP.md to
replace the generic items with the concrete deliverables and issue references
from issue `#626`: list the "Done" items (Voyager BFT mainnet activation,
cross-chain bridge to Ethereum (Hyperlane), signed releases (cosign + SLSA L3),
DEX (UniV2 fork), CoinBlast launchpad, faucet, explorer) with links to their
issues/PRs, add the "In Progress" items including EVM value-passing bug fix
(`#580`), apply-profile observability (`#594` shipped), trie prune cycle tuning
(`#610` shipped), add the "Next" items stSRX (`#615`), Aave fork (`#616`), Sentrix
Names (`#617`), NFT marketplace, LayerZero V2 bridge, public Grafana templates
with issue refs, and add the "Future" items Frontier F-3 parallel apply (`#618`),
DAG consensus exploration (`#620`), grants program, bug bounty (Immunefi) so the
Q2 2026 section matches `#626` and includes traceable issue links.
| ## Q3 2026 | ||
| - 🔮 Mainnet stability improvements | ||
| - 🔮 Mobile wallet SDK | ||
| - 🔮 DEX integration | ||
| - 🔮 NFT support |
There was a problem hiding this comment.
Status inconsistency: Q3 2026 items marked as "Future" (🔮).
All Q3 2026 items are marked with the 🔮 Future status, which seems inconsistent with the near-term quarterly timeframe. Consider using 📋 Planned status instead, since Q3 2026 is only one quarter away and these items should be in the "Next" category according to issue #626.
Additionally, these items lack issue references. For example, if "NFT support" relates to the "NFT marketplace" mentioned in #626, it should include the corresponding issue link.
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 25-25: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@ROADMAP.md` around lines 25 - 29, Update the Q3 2026 roadmap entries so their
status reflects "Planned" instead of "Future": replace the 🔮 emoji with 📋 for
each bullet under the "## Q3 2026" heading (the bullets "Mainnet stability
improvements", "Mobile wallet SDK", "DEX integration", "NFT support") and append
the appropriate issue references (e.g., add "(`#626`)" or the exact issue
numbers/links) to each item—if "NFT support" maps to the "NFT marketplace" in
issue `#626`, add that reference specifically. Ensure each bullet becomes like "📋
Item description (#[issue-number])" so readers can navigate to the related
issue.
| ## Long-term | ||
| - Cross-chain interoperability | ||
| - Privacy features (ZK proofs) | ||
| - Enterprise tooling |
There was a problem hiding this comment.
Missing status indicators in Long-term section.
For consistency with the rest of the roadmap, long-term items should also include status indicators (likely 🔮 Future). Additionally, issue #626 mentions specific future items that should be included here:
- Frontier F-3 parallel apply (
#618) - DAG consensus exploration (
#620) - Grants program
- Bug bounty program (Immunefi)
Note that "Bug bounty program" currently appears in Q2 2026 Security section, but according to #626, the Immunefi bug bounty should be in the Future category.
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 31-31: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@ROADMAP.md` around lines 31 - 34, Update the "## Long-term" section to
include status indicators and the missing future items: prepend each bullet with
the 🔮 Future emoji (e.g., "🔮 Future - Cross-chain interoperability"), and add
bullets for "🔮 Future - Frontier F-3 parallel apply (`#618`)", "🔮 Future - DAG
consensus exploration (`#620`)", "🔮 Future - Grants program", and "🔮 Future -
Bug bounty program (Immunefi)"; also remove or relocate the duplicate "Immunefi"
bug bounty entry from the Q2 2026 Security section so the Immunefi bounty only
appears under the Long-term/Future list.
| ## Contributing | ||
| Open issues with feature requests or comment on roadmap items. |
There was a problem hiding this comment.
Missing quarterly update commitment.
Issue #626 explicitly requests: "Commit to quarterly updates (or when material changes occur)." Consider adding a statement about the update cadence to the Contributing section or near the disclaimer to fulfill this requirement.
Example:
## Contributing
Open issues with feature requests or comment on roadmap items. This roadmap is updated quarterly or when material changes occur.🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 36-36: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@ROADMAP.md` around lines 36 - 37, Update the "## Contributing" section in
ROADMAP.md to include a clear commitment to update cadence: append a sentence
such as "This roadmap is updated quarterly or when material changes occur." so
the "## Contributing" heading explicitly states the quarterly update commitment
requested in issue `#626`.
1 participant
Summary
Adds a
ROADMAP.mdat repo root with the public development roadmap.Content
Fixes #626
Wallet: zp6
Summary by CodeRabbit