feat: NMv3: submission of stress testing result into nym-api

[jstuczyn]

NYM-749

Summary

Allow the network monitor orchestrator to submit stress-testing results to the nym-api over a signed, authenticated channel.

• Contract: orchestrators can now announce an ed25519 identity key on-chain; shape-only validation (base58 + 32 bytes), no curve-point check by design.
• Orchestrator startup: verifies on-chain authorisation (with retry/backoff), reconciles its announced identity key against the local one, and self-checks that the nym-api recognises it before
  spawning background tasks.
• Result submission: new ResultSubmitter task periodically drains freshly-completed testrun rows, wraps them in a signed StressTestBatchSubmission, and POSTs them to nym-api. Watermark is
  advanced only on POST success (at-least-once delivery — losing measurements is worse than occasional duplicates).
• nym-api:
  • POST /v3/nym-nodes/stress-testing/batch-submit — staleness check, authorised-set membership, monotonic-timestamp replay protection, signature verify, then per-entry insert.
  • GET /v3/nym-nodes/stress-testing/known-monitors/{identity_key} — lets orchestrators self-check authorisation after announcing their key.
  • Authorised set is TTL-cached with single-flight refresh to avoid thundering the chain.
• Dedup: each result carries its orchestrator-local testrun_id, stored alongside the submitter's pubkey as a composite primary key. Retried submissions drop duplicates via INSERT OR IGNORE.

Results are persisted but not yet consumed — downstream usage lands in a follow-up PR.

---

This change is 

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
nym-explorer-v2	Ready	Preview, Comment	Apr 27, 2026 9:27am

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
docs-nextra	Ignored	Preview	Apr 27, 2026 9:27am
nym-node-status	Ignored	Preview	Apr 27, 2026 9:27am