Known Issues
Migrate to Virtual TestNets
For new projects, we recommend starting with TestNets.
For automatic migration of DevNets to TestNets, .
If you encounter any issues not mentioned here, please contact our support team via the chat in the Dashboard or at support@tenderly.co. We appreciate your feedback, even for issues listed here.
Waffle is currently not supported
We are working on supporting Waffle in the future. In the meantime, try using plain Ethers.
hardhat-network-helpers is not supported
If your tests rely on this library, they will most likely fail because it expects the underlying network to be HardHat. We are working to expose this functionality for DevNets as well.
Timeouts
Due to the hosted nature of DevNets and the framework of the underlying RPC calls (e.g., sending a transaction in Ethers actually involves 13 RPC calls), more complex test suites can experience timeouts.
Missing custom RPC calls
We currently do not support every custom RPC call that other development nodes offer. This can cause some tests that rely on these calls to fail.
Check out the list of all supported custom RPC methods in DevNets**.**
Bad Request Error
There are several causes for bad request errors:
- Your input parameters do not match the Ethereum JSON RPC protocol. In that case, you will see the error message
invalid params. - Your RPC URL is not properly copied from the Dashboard or CLI. The error message will advise you to double-check the RPC URL.
- If everything above is fine, and you still get the error, it is probably because the DevNet has expired. The error message will advise you to double-check if the DevNet is still running in the Dashboard.