Hi Zama team & community! 
First off, massive congrats on Testnet v2 launch today — the encrypted compute upgrades look game-changing! Been following since the July public testnet and can’t wait for mainnet EOY.
Quick technical hurdle while integrating:
- Following FHEVM tutorials (e.g., Sepolia setup with relayer-sdk@0.2.0), the default relayerUrl is https://relayer.testnet.zama.cloud.
- But pinging it returns DNS ENOTFOUND (no resolution at all).
Related threads I’ve seen:
- Error creating Relayer Instance from NodeJS (Nov 6, 2025) – Similar instance creation issues.
- Problem with relayer /v1/create-input on Sepolia (Oct 2, 2025) – Endpoint call errors.
Questions for clarity:
- Is the public relayer fully live for v2, or still in staged/whitelist rollout? (Gateway at sepolia.zama.ai works fine.)
- Any temp workaround/alt endpoint? (E.g., local relayer setup?)
- ETA for stable access? Building a confidential voting dApp and this is the last piece!
Code snippet for context (Node.js createInstance):