Aztec testnet: don't require wallet activation#162
Merged
Conversation
Aztec testnet uses SponsoredFeePaymentMethod with SponsoredFPCContract, so the SchnorrAccountContract deploys lazily on the wallet's first transaction — no separate activation step is needed. Returning requiresActivation=true causes AdminAPI to mark every newly generated wallet as Inactive, and since the activateAddress gRPC handler is also a stub returning "not supported", wallets get permanently stuck. Flip the GenerateAddress response to requiresActivation=false so wallets land in Active status and are usable immediately. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
Flip
GenerateAddressresponse fromrequiresActivation: true→falsein the Aztec testnet gRPC service.Aztec testnet uses
SponsoredFeePaymentMethodwithSponsoredFPCContract, so theSchnorrAccountContractdeploys lazily on the wallet's first transaction — there's no separate activation step required.Returning
truewas causing AdminAPI to mark every new Aztec wallet asStatus=Inactive, and sinceactivateAddressis also a stub returningaccepted=false / "not supported", wallets got permanently stuck. Verified manually: a freshly generated Aztec testnet wallet works (account contract auto-deploys on first send via SponsoredFPC).Changes
js-aztec-testnet/src/services/NetworkGrpcService.ts:77—requiresActivation: true→falseTest plan
aztec-testnet— should land inActivestatus, no activation prompt🤖 Generated with Claude Code