EDU Chain is in the process of updating its chain infrastructure. As a result, there will be some changes that may affect how your product interacts with EDU Chain. We’ve worked with our infra providers to minimize potential impact and downtime and appreciate your understanding and continued support.

ℹ️ What’s Changing

Conduit will be the primary chain infrastructure and RPC provider for EDU Chain starting later this month. This applies to both testnet and mainnet. As part of this change, we are standardizing our RPC endpoints and block explorer URLs.

New RPC endpoints (already active)

• Testnet:
  • https://rpc.testnet.educhain.xyz
  • wss://rpc.testnet.educhain.xyz
• Mainnet:
  • https://rpc.educhain.xyz
  • wss://rpc.educhain.xyz

<aside> 💡

We expect the existing Gelato RPC endpoints to still work and point automatically to the new ones for a limited period of time, but we would still recommend updating to the standardized endpoints above in a timely manner.

</aside>

New block explorer URLs (already active)

• Testnet: https://explorer.testnet.educhain.xyz/
• Mainnet: https://explorer.educhain.xyz/

🛠️ What You Need to Do

If you use only the public RPC (without API key)

• Update your RPC endpoints to the new, standardized ones above
• If you use a block explorer, update to the new URLs above

If you use a private RPC (with API key)

• Create a Conduit account (if you don’t already have one).
  • If you already have a Conduit account, their API keys are network agnostic and can be used for EDU Chain once the switch has taken place (see below for timing)
  • 👉 Create Conduit account
• Review Conduit’s getting started guide
• Prepare your product to use the new RPC endpoints + API key
  • For example: https://rpc.educhain.xyz/[YOUR API KEY]
• Make the switch to your new RPC settings once the infra update has taken place (see below for timing)