Skip to content

Update testnet RPC endpoint to v5#263

Merged
critesjosh merged 3 commits into
testnetfrom
jc/update-testnet-v5-rpc
Jun 30, 2026
Merged

Update testnet RPC endpoint to v5#263
critesjosh merged 3 commits into
testnetfrom
jc/update-testnet-v5-rpc

Conversation

@critesjosh

Copy link
Copy Markdown
Collaborator

Summary

Updates the testnet node URL in config/testnet.json to the v5 endpoint:

  • https://rpc.testnet.aztec-labs.comhttps://v5.testnet.rpc.aztec-labs.com

This 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.com is returning a 503 from 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.

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`.
@critesjosh critesjosh merged commit 41dd9da into testnet Jun 30, 2026
2 checks passed
@critesjosh critesjosh deleted the jc/update-testnet-v5-rpc branch June 30, 2026 16:36
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.

1 participant