-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unify networks and add Base support #3091
Conversation
b229b4f
to
87bb1f6
Compare
const MAINNET_BLOCK_TIME: u64 = 13_000; // ms | ||
const GNOSIS_BLOCK_TIME: u64 = 5_000; // ms | ||
const SEPOLIA_BLOCK_TIME: u64 = 13_000; // ms | ||
const ARBITRUM_ONE_BLOCK_TIME: u64 = 100; // ms |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was incorrect, it should've been 250. Any special reason for it @sunce86 ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, I just thought it's 100ms 😄
@@ -1,43 +0,0 @@ | |||
use primitive_types::U256; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Goodbye duplication
crates/network/Cargo.toml
Outdated
@@ -0,0 +1,15 @@ | |||
[package] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not married to the idea of making it a crate
since the code is not that big.
Advantages:
- more modular
- less code in
share
- faster compilation time
Disadvantages:
- more crates, difficult to navigate
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the idea of encapsulating all the necessary changes to add a new network in a single place. I think there are probably more types basic enough that we could have shared code for them (although this could also lead to another shared
crate with too much stuff in there if we are not careful).
Maybe it makes sense to leave this as a separate network
crate for now but be open to the idea to turn it into a primitive_types
crate later on to also move Address
, ContractAddress
, TokenAddress
, etc. into it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I love the idea to have a crate
with common domain stuff like Address
, TokenAddress
, Network
, etc. I proposed it in the past too. In the near future, we can rename the crate and stuff moving stuff there and removing duplicates.
87bb1f6
to
026347b
Compare
crates/network/src/lib.rs
Outdated
/// Represents each available network | ||
#[derive(Clone, Copy, Debug, PartialEq)] | ||
pub enum Network { | ||
Mainnet = 1, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now the chain IDs are unified in one place
crates/network/src/lib.rs
Outdated
Network::try_from(value).map_err(de::Error::custom) | ||
} | ||
|
||
fn visit_str<E>(self, value: &str) -> Result<Self::Value, E> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is not needed to add Deserialization
from str
, but since I was on it, I thought it could be handy in case we configure chain ID as "1"
. I am open to remove it too.
@@ -67,7 +67,6 @@ pub trait BalanceFetching: Send + Sync { | |||
|
|||
/// Contracts required for balance simulation. | |||
pub struct Contracts { | |||
pub chain_id: u64, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was unused.
match chain_id { | ||
1 => &[Self::Liquidity, Self::Blockscout, Self::Ethplorer], | ||
100 => &[Self::Liquidity, Self::Blockscout], | ||
_ => &[Self::Liquidity], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed the non-exhaustive case, otherwise when adding a new network we may overlook this.
026347b
to
6b9f83a
Compare
@@ -60,7 +60,6 @@ pub fn check_erc1271_result(result: Bytes<[u8; 4]>) -> Result<(), SignatureValid | |||
|
|||
/// Contracts required for signature verification simulation. | |||
pub struct Contracts { | |||
pub chain_id: u64, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was unused.
@@ -18,8 +18,7 @@ use { | |||
struct Config { | |||
/// Optional chain ID. This is used to automatically determine the address | |||
/// of the WETH contract. | |||
#[serde_as(as = "Option<serialize::ChainId>")] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need to do serde_as
when the type implements Deserialization
6b9f83a
to
03d4104
Compare
03d4104
to
7959140
Compare
crates/network/src/lib.rs
Outdated
/// Returns the block time in milliseconds | ||
pub fn block_time_in_ms(&self) -> u64 { | ||
match self { | ||
Self::Mainnet => 13_000, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Self::Mainnet => 13_000, | |
Self::Mainnet => 12_000, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was from legacy code. I corrected it. Maybe @sunce86 had a reason for it? 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, not too important from the aspect of settlement code where it was used as 13_000
crates/network/Cargo.toml
Outdated
@@ -0,0 +1,15 @@ | |||
[package] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the idea of encapsulating all the necessary changes to add a new network in a single place. I think there are probably more types basic enough that we could have shared code for them (although this could also lead to another shared
crate with too much stuff in there if we are not careful).
Maybe it makes sense to leave this as a separate network
crate for now but be open to the idea to turn it into a primitive_types
crate later on to also move Address
, ContractAddress
, TokenAddress
, etc. into it.
c342c23
to
643242f
Compare
ef30de3
to
2e49f97
Compare
2e49f97
to
9b2d13e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a eth::ChainId in driver domain::eth, can you check if you can remove that one as well?
I think crate chain
should not represent union of all functionalities related to chains, across all other crates, but rather just an enum and constructor => common code used in all crates, that rarely changes (only when new chain is added) and can be extensively reused as is.
infra::blockchain::Id::Sepolia => TARGET_AGE / SEPOLIA_BLOCK_TIME, | ||
infra::blockchain::Id::ArbitrumOne => TARGET_AGE / ARBITRUM_ONE_BLOCK_TIME, | ||
} | ||
chain.blocks_in(TARGET_AGE).round() as u64 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: blocks_in
is only used in autopilot. Just a personal preference to put ONLY COMMON functionalities in chain
crate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, I thought of that, but blocks in X time seemed to me pretty generic, regardless of it is used only by autopilot or not 🤔 it is not domain code, it is generic code. That's why I kept the 1 hour
settlement time where it is.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what's more, the code you are commenting on is NOT in the chain crate, but in the autopilot, so I don't know if you confused it 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, not a big deal for this function in particular. Just wanted to align what we put in chain
, as I can forsee that blocks_in
will be removed in a few months and that would lead to updating chain
crate which we might want to avoid (if we want it to change only when the new chain is added).
#[repr(u64)] | ||
pub enum Chain { | ||
Mainnet = 1, | ||
Goerli = 5, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why resurrecting Goerli?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Backwards compatibility. Many of the matches account for it. I am up for deleting all its occurrences.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Me to. But I'm also fine adding a separate issue to tackle it in a separate PR.
Yeah, that is exactly what I intended with this PR. By making the enum and consuming it in a non-exhaustive way in the domain logic, we guarantee that adding a new network is seamless, what's more, we avoid a lot of code duplication.
let me check it! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice
Description
Create a crate called
network
which unifies all the networks in the whole codebase. Thenetwork
crate is in fact an enum, which should be always consumed in a non-exhaustive way, therefore, when adding a new network, it will error in all the place it requires action.This reduced duplicated code, and makes it easier to add a new network. With this change, only
network
should contain reference to the realchain ID
.Added
Base
support.Changes
network
Network
as anenun
, and replace it in the code base in a non-exhaustive way, so it screams error when adding a new networkBase
How to test