Repository navigation
CLI: nirium report, summary and export from the Reporting node #136
Description
The SDK already reads the Reporting node (getReportingSummary, getReportingExport, getReportingExportUrl), but the CLI has no way to see your own anchors and receipts.
Proposal: nirium report
nirium report summary [--from <date>] [--to <date>] [--json]
nirium report export anchors|payments|payroll [--from] [--to] [--limit] [--csv out.csv]
Uses the API key from the CLI config store. export anchors should print one CID per row, so it can be piped straight into nirium verify.
Keep the SDK's wording in the help text: this is a summary of your own records, not certified regulatory reporting.
Done when: tests with a mocked API cover summary, JSON export and CSV export, and the README documents the command.
Owner: @M0nsxx
Disclosure: drafted with AI assistance under my direction and reviewed by hand.
Activity
ravimahatonp commentedon Oct 14, 2026
Hello team,
I examined the issue "CLI: nirium report, summary and export from the Reporting node" in nirium-protocol/nirium and would be glad to implement the required changes.
Technical Implementation Outline:
Result/custom errors), and concurrency safety.cargo check,cargo test, andcargo clippy -- -D warningspass cleanly.Please assign this issue to me. I will submit a clean, well-tested, and production-ready PR promptly!
grantfox-oss commentedon Oct 15, 2026
🦊 GrantFox — @M0nsxx has been assigned to this issue!
Next steps:
Closes #136)Good luck! Track your progress on GrantFox.
grantfox-oss commentedon Nov 7, 2026
🎉 This issue has been marked as completed on GrantFox!
@M0nsxx's PR #266 was approved and merged by @Eras256.
🏆 @M0nsxx: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (643 total points). Track your full progress on GrantFox.
👏 Great work, @M0nsxx! Keep contributing to nirium-protocol.