Feature/gateway upgrade mode #5986
Closed
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
jstuczyn
force-pushed
the
feature/gateway-upgrade-mode
branch
from
3d8a06a to
a1b46ad
Compare
jstuczyn
force-pushed
the
feature/gateway-upgrade-mode
branch
from
8317741 to
df53d25
Compare
jstuczyn
force-pushed
the
feature/credential-proxy-jwt
branch
from
5f8be2d to
df54ef8
Compare
jstuczyn
force-pushed
the
feature/gateway-upgrade-mode
branch
from
de7e53b to
d69e499
Compare
jstuczyn
modified the milestones:
Isabirra (est. mainnet 30.09.2025),
Jarlsberg (est. mainnet 14.10.2025)
jstuczyn
modified the milestones:
Jarlsberg (est. mainnet 14.10.2025),
Kase (est. mainnet 28.10.2025)
jstuczyn
force-pushed
the
feature/credential-proxy-jwt
branch
4 times, most recently
from
be69a8f to
038c496
Compare
jstuczyn
force-pushed
the
feature/gateway-upgrade-mode
branch
from
d69e499 to
199df96
Compare
jstuczyn
force-pushed
the
feature/gateway-upgrade-mode
branch
from
199df96 to
0573b9f
Compare
jstuczyn
force-pushed
the
feature/credential-proxy-jwt
branch
from
17259f6 to
106cba0
Compare
jstuczyn
force-pushed
the
feature/gateway-upgrade-mode
branch
from
8f4b896 to
8ea0088
Compare
jstuczyn
force-pushed
the
feature/gateway-upgrade-mode
branch
from
8ea0088 to
bb3055a
Compare
jstuczyn
force-pushed
the
feature/credential-proxy-jwt
branch
from
106cba0 to
8c15a5c
Compare
benedettadavico
modified the milestones:
Leerdammer (est. mainnet 11.11.2025),
Mozzarella (est. mainnet 25.11.2025)
jstuczyn
force-pushed
the
feature/credential-proxy-jwt
branch
from
a0eafc0 to
737b465
Compare
post rebasing fixes AuthenticatorVersion helpers additional nits allow unwraps in mocks fixed linux build clippy integrating upgrade mode into authenticator fixed build after adding wrappers to response types conditionally updating peer handle bandwidth cleanup negotiate initial protocol during registration change auth to use highest protocol handler for JWT message dont meter client bandwidth in upgrade mode handling recheck requests sending information about upgrade_mode on client messages gateway watching for upgrade mode attestation wip: gateways to disable bandwidth metering on upgrade mode
jstuczyn
force-pushed
the
feature/gateway-upgrade-mode
branch
from
bb3055a to
b10e8db
Compare
Contributor
Author
|
superseded by #6174 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
implements naive versions NET-451 and NET-450 as part of NET-341
depends on #5957
relevant API changes:
nym-gateway-requests
Changed
CURRENT_PROTOCOL_VERSIONfrom 5 to 6 ('upgrade mode')ServerResponse::Authenticatecontainsupgrade_modeflag to indicate whether gateway thinks the system is undergoing the upgradeServerResponse::Registercontainsupgrade_modeflag to indicate whether gateway thinks the system is undergoing the upgradeServerResponse::Bandwidthcontainsupgrade_modeflag to indicate whether gateway thinks the system is undergoing the upgradeServerResponse::Sendcontainsupgrade_modeflag to indicate whether gateway thinks the system is undergoing the upgradenym-credentials-interface
Added
BandwidthCredentialto act as a wrapper for different types of credentials. current the oldCredentialSpendingData(i.e. ticketbooks) and jwt tokens issued during upgrade mode. in the future it will also include emergency mode credentials issued by signer quorum:nym-authenticator-requests
Added
BandwidthClaimtype to wrap aroundBandwidthCredentialand to also include an explicittype(i.e. mixnet/wg entry/exit)v6version of authenticator messagesupgrade_mode_enabled: boolfieldFinalMessageusesBandwidthClaiminstead ofCredentialSpendingDatafor thecredentialfieldChanged
FinalMessagetrait methodcredential()now returnsOption<BandwidthClaim>rather thanOption<CredentialSpendingData>to allow the upgrade mode flow where user would not have a valid zk-nymThis change is