fix: add faucet pour to zauth allowed restrictions#1800
Open
guruhubb wants to merge 2 commits into
Open
Conversation
The `pour` method (faucet) was missing from AvailableRestrictions, causing zauth to reject faucet transactions for split-key wallets with "permission denied".
…ickets - Add HealthyByLFB() to NodeHolder: queries all sharders for current round, caches those within 3 blocks of max LFB (10s TTL), penalizes lagging sharders - Falls back to single highest-weighted sharder when no LFB data available - Fix initEncryption in downloadworker: skip encryption key validation when EncryptionPublicKey is empty (legacy files / auth ticket downloads)
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
1 participant
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.
Summary
AvailableRestrictionsto determine which smart contract methods a peer key is allowed to invokepourmethod (used by the faucet smart contract) was not listed in any restriction categoryChanges
"pour"to thetoken_transfersrestriction category inAvailableRestrictionsTest plan
transferrestriction still works correctly