fix: Updated to use ethers-rs

[Maikol]

Dependency changes

Removed dependencies:

eip-712-derive
solidity-bindgen
web3

Added dependencies:

ethers
url

Code changes

Config changes

Removed the ORACLE_CONTRACTS env variable. This was used to get the network name, chain id, contracts addresses and RPC url. Value was split with a : so you had to pass sepolia:RPC_URL. Replaced this with two variables REWARDS_MANAGER_CONTRACT and RPC_URL. We only really need the rewards manager address so by doing this change we can remove all contract configs and if we need to run on a different network we just need to pass the contract address and url, no need for code changes. We are also getting the chain id from the provider so we removed common/src/chain_id.rs since we no longer need it.

Contract interactions

By switching from solidity-bindgen to ethers-rs we can get rid of over 8k lines in common/src/contracts/abis.rs and only import availability-oracle/src/abi/RewardsManager.abi.json which is what we want to interact with. We're also simulating the transaction to check of errors and if we detect one we log the revert reason.

[gitguardian]

⚠️ GitGuardian has uncovered 5 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
8215355	Triggered	Generic High Entropy Secret	e3bff41	common/src/contracts/config.rs	View secret
8215358	Triggered	Generic High Entropy Secret	e3bff41	common/src/contracts/config.rs	View secret
8215360	Triggered	Generic High Entropy Secret	e3bff41	common/src/contracts/config.rs	View secret
8215361	Triggered	Generic High Entropy Secret	e3bff41	common/src/contracts/config.rs	View secret
8215365	Triggered	Generic High Entropy Secret	e3bff41	common/src/contracts/config.rs	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[Theodus]

LGTM. Just some suggestions

[Theodus]

This can be a separate PR: probably a good idea to upgrade these dependencies. I typically check for the latest versions with cargo-outdated (cargo outdated -R)

[Maikol]

Definitely, I'll do it as a new PR.