Skip to content

Conversation

@jstuczyn
Copy link
Contributor

@jstuczyn jstuczyn commented Jan 22, 2026

this PR does the following:


This change is Reviewable

@vercel
Copy link

vercel bot commented Jan 22, 2026

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

Project Deployment Review Updated (UTC)
nym-explorer-v2 Ready Ready Preview, Comment Jan 23, 2026 11:48am
2 Skipped Deployments
Project Deployment Review Updated (UTC)
docs-nextra Ignored Ignored Preview Jan 23, 2026 11:48am
nym-node-status Ignored Ignored Preview Jan 23, 2026 11:48am

Request Review

Copy link
Contributor

@simonwicky simonwicky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Non of these comments are blocking on that PR per se, but are points that I think should be addressed before the release

pub use nym_registration_common::{
LpGatewayData, LpRegistrationRequest, LpRegistrationResponse, RegistrationMode,
LpDvpnRegistrationRequest, LpMixnetGatewayData, LpMixnetRegistrationRequest,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why the re-export in the first place? It's used in a place where registration-common is already imported anyway

inc!("lp_registration_dvpn_attempts");

// Check for idempotent re-registration (same WG key already registered)
// This allows clients to retry registration after network failures
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It doesn't, at this point, LPDvpnRegistrationRequest already contains a credential.
A malicious could say "Oh you're already registered", keep the credential to create a double spending when the client tries to use the same credential somewhere else

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants