Urgent: Unable to Deploy New Smart Contracts or Use Existing Contracts on XDC Apothem Network

We’re facing critical issues on the Apothem Test Network that are severely impacting our development and testing workflows.

❗ Problems Observed:

1. Unable to deploy any smart contracts via Hardhat

• Attempts to deploy fail with no response or timeout.

• We've tested across multiple RPC endpoints:

  • https://rpc.apothem.network
  • https://erpc.apothem.network
  • https://earpc.apothem.network

1. Existing smart contracts are not working

• Transactions and contract interactions revert or behave inconsistently.
• The network seems to rollback to older block numbers, resulting in previously confirmed transactions and contract deployments becoming unavailable or invalid.

🛠️ Steps We Tried:

• Switching between different RPC URLs.
• Re-deploying from a clean Hardhat project.
• Verifying block numbers via xdcscan — shows instability and rollback patterns.

🧪 Environment:

• Framework: Hardhat
• Network: Apothem

🚨 Request:

We kindly request the XDC team to:

• Investigate the network instability and rollback issues.
• Confirm whether Apothem RPCs are currently degraded or undergoing maintenance.
• Provide an estimated resolution timeline or suggest alternative RPCs we can use in the interim.

This issue is blocking us from both development and QA of our dApp.

Thank you for your support.