Update testnet RPC endpoint to v5#263
Merged
Merged
Conversation
The testnet node at v5.testnet.rpc.aztec-labs.com runs 5.0.0-rc.2; the 4.1.0 client failed with "Method not found: node_registerContractFunctionSignatures". Bump all @Aztec packages, the aztec-nr dependency, config/toolchain versions, and docs to 5.0.0-rc.2, and migrate code for v5 breaking changes: - Noir: MessageDelivery moved to aztec::messages::delivery and now uses constructor syntax (MessageDelivery::onchain_constrained()). - Run TS scripts with tsx instead of ts-node/esm (ts-node's ESM loader cannot resolve @aztec/standard-contracts subpath-pattern exports that @aztec/pxe now imports at runtime). - AztecAddress.fromString -> AztecAddress.fromStringUnsafe. - from: AztecAddress.ZERO -> NO_FROM for account/contract deployments. - Deploy: pass salt via deploy options and read contract/instance from the send result (returnReceipt option removed). - GasSettings.fallback now requires explicit gasLimits. - Fee-juice claims: wait for the bridged L1->L2 message to be available before claiming (rc.2 needs more than two blocks for the message to sync to L2).
5.0.0-rc.2's `aztec compile` shells out to `nargo`, which the installer places in ~/.aztec/current/internal-bin. Without it on PATH the local-network job fails with `spawn nargo ENOENT`.
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
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
Updates the testnet node URL in
config/testnet.jsonto the v5 endpoint:https://rpc.testnet.aztec-labs.com→https://v5.testnet.rpc.aztec-labs.comThis aligns the testnet config with the v5 RPC endpoint (the repo is migrating to v5.0.0).
Note
At the time of opening this PR,
v5.testnet.rpc.aztec-labs.comis returning a503from the Kong gateway (failure to get a peer from the ring-balancer), indicating the upstream nodes behind the gateway are not currently healthy. The endpoint URL itself is correct; the gateway just has no healthy upstream peers at the moment. Worth confirming the upstream is back before/after merge.