[feat] propagate NM agent noise keys to nym-node routing#6577
Merged
jstuczyn merged 9 commits intofeat/mix-stress-testingfrom Apr 23, 2026
Merged
[feat] propagate NM agent noise keys to nym-node routing#6577jstuczyn merged 9 commits intofeat/mix-stress-testingfrom
jstuczyn merged 9 commits intofeat/mix-stress-testingfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
jstuczyn
modified the milestones:
Tola - (mainnet release 7th april),
Urda - (mainnet release 21st april)
jstuczyn
force-pushed
the
feat/nmv3-agents-subscription
branch
from
964df4e to
916213f
Compare
jstuczyn
force-pushed
the
feat/nmv3-noise-support
branch
from
af43108 to
c7d018e
Compare
benedettadavico
modified the milestones:
Urda - (mainnet release 21st april),
Venaco - (mainnet release 5th may)
jstuczyn
force-pushed
the
feat/nmv3-noise-support
branch
from
c7d018e to
69fe5db
Compare
jstuczyn
force-pushed
the
feat/nmv3-agents-subscription
branch
from
916213f to
461075f
Compare
simonwicky
reviewed
Apr 22, 2026
jstuczyn
force-pushed
the
feat/nmv3-noise-support
branch
from
69fe5db to
b00c2b3
Compare
jstuczyn
force-pushed
the
feat/nmv3-agents-subscription
branch
from
461075f to
c01b728
Compare
jstuczyn
force-pushed
the
feat/nmv3-agents-subscription
branch
from
c01b728 to
617acd4
Compare
jstuczyn
force-pushed
the
feat/nmv3-noise-support
branch
from
b00c2b3 to
2ea6fa9
Compare
Base automatically changed from
feat/nmv3-agents-subscription
to
feat/mix-stress-testing
April 23, 2026 12:20
jstuczyn
force-pushed
the
feat/nmv3-noise-support
branch
from
2ea6fa9 to
91732bf
Compare
simonwicky
approved these changes
Apr 23, 2026
jstuczyn
modified the milestones:
Venaco - (mainnet release 5th may),
Waterloo - (mainnet release 19th may)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Network Monitor agents need to perform Noise protocol handshakes with nym-nodes, just like any other nym-node on the network. Previously the contract stored only the agent's IP address, and the noise key map in nym-node only tracked keys for nym-api-sourced nodes. This PR closes the gap end-to-end: from on-chain registration through to live packet routing.
This change is