Skip to content

CLI: nirium anchor --sign, attach an agent attestation #134

New issue
New issue
Closed
#268
Closed
CLI: nirium anchor --sign, attach an agent attestation#134
#268
Assignees
M0nsxx
Labels
enhancementNew feature or request

Description

@Eras256
Eras256
opened on Oct 14, 2026

Follow-up to #133 (nirium anchor). The Audit Trail accepts an optional agent attestation: an ed25519 signature over nirium-audit-v1:<content_sha256> made with a Stellar key (AuditAnchorOptions.agent in the SDK). nirium verify already checks it, but there's no CLI way to produce one.

Proposal: nirium anchor --sign, using the secret key from the CLI config store or --key-env <VAR>. It computes the content hash, signs the statement locally, and sends agent: { key, signature, id? }. The secret never leaves the machine and is never printed.

Done when:

  • a signed anchor round-trips: nirium verify <cid> reports SIGNATURE: VALID with the right G key
  • a wrong key or a tampered signature gets the node's 400 and the CLI says nothing was anchored
  • tests use a throwaway Keypair.random() and no network

Owner: @M0nsxx

Disclosure: drafted with AI assistance under my direction and reviewed by hand.

Activity

  1. Eras256
    added
    enhancementNew feature or request
    on Oct 14, 2026

  2. rupesh-kumar-sah commented on Oct 14, 2026

    @rupesh-kumar-sah
    rupesh-kumar-sah
    on Oct 14, 2026

    Hi maintainers,

    I reviewed "CLI: nirium anchor --sign, attach an agent attestation" and have a structured approach ready for implementation:

    Technical Implementation Outline:

    1. Review target data structures, error handling (Result/custom errors), and concurrency safety.
    2. Implement resilient, idiomatic Rust logic with zero panics and defensive boundary checks.
    3. Add comprehensive unit and regression tests covering expected behavior and edge cases.
    4. Ensure cargo check, cargo test, and cargo clippy -- -D warnings pass cleanly.

    Please assign this issue to me. I will submit a clean, well-tested, and production-ready PR promptly!

  3. Eras256
    assigned
    M0nsxx
    on Oct 15, 2026

  4. grantfox-oss commented on Oct 15, 2026

    @grantfox-oss
    grantfox-ossBot
    on Oct 15, 2026 – with GrantFox OSS

    🦊 GrantFox — @M0nsxx has been assigned to this issue!

    Next steps:

    1. Open a Pull Request referencing this issue (e.g., Closes #134)
    2. Your PR will be reviewed by the nirium-protocol maintainers

    Good luck! Track your progress on GrantFox.

  5. Eras256
    added a commit that references this issue on Nov 7, 2026

    feat(cli): nirium anchor --sign - attach an agent attestation (#264)

    1fc5bed

  6. grantfox-oss commented on Nov 7, 2026

    @grantfox-oss
    grantfox-ossBot
    on Nov 7, 2026 – with GrantFox OSS

    🎉 This issue has been marked as completed on GrantFox!

    @M0nsxx's PR #264 was approved and merged by @Eras256.

    🏆 @M0nsxx: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (538 total points). Track your full progress on GrantFox.

    👏 Great work, @M0nsxx! Keep contributing to nirium-protocol.

  7. Eras256
    closed this as completedin #268on Nov 7, 2026

  8. grantfox-oss commented on Nov 7, 2026

    @grantfox-oss
    grantfox-ossBot
    on Nov 7, 2026 – with GrantFox OSS

    🎉 This issue has been marked as completed on GrantFox!

    @M0nsxx's PR #268 was approved and merged by @Eras256.

    🏆 @M0nsxx: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (678 total points). Track your full progress on GrantFox.

    👏 Great work, @M0nsxx! Keep contributing to nirium-protocol.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions