feat: NMv3: announce agents' ed25519 identities to the contract - #7080
feat: NMv3: announce agents' ed25519 identities to the contract#7080jstuczyn wants to merge 2 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Further builds up on the existing liveness tests stack. The agent derives an ed25519 client identity from its noise key and announces it, and the orchestrator records it on chain.
POST /v1/agent/announce, holds it in theKnownAgentsentry, and puts it on bothAuthoriseNetworkMonitormessages of the existing single transaction. An announcement whose identity differs from the cached one resets the announced flag so both addresses are re-authorised.This lands dark. The field is written but nothing reads it until the gateway session gate from branch 3 meets an agent that announces, which is branch 9.
This change is