Developers trying to interact with's Smart Contracts, might encounter errors, or reverted transactions.

Tools like Etherscan might not be very helpful in this case, as's Smart Contract implement Custom Errors, which are not stored on-chain. This is to save on storage and gas costs.

The best way to investigate this issue is to inspect the 4-byte selector for the Custom Error and compare it against the list of Custom Errors in our public codebase, available on GitHub (make sure to scroll down).

A useful tool that is able to do this comparison, is tenderly, thanks to the fact that's Smart Contracts have been verified. Here is SSVNetwork contract, for example.

Last updated