You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Eth2-to-NEAR-relay, network, contract_type, and near_network_id parameters are accepted as generic String types but would be best handled by Rust’s enum types.
The text was updated successfully, but these errors were encountered:
* Separate `logger`, `eth_rpc_client`, and `Eth2OnNearClient` contract initialization into separate crates
* Check configuration setup for Mainnet: add a verification on init args that it can't be executed in the trustless mode without `bls` verification on Mainnet (#767).
* Improve config file usage on contract initialization: `validate_updates`, `verify_bls_signatures`, `hashes_gc_threshold`, `max_submitted_blocks_by_account`, `trusted_signer_account_id` fields are set through the config file instead of hardcoded values (#769).
* Improve configuration of some args: `network`, `contract_type`, and `near_network_id` now use `enum`s instead of `String`s (#811).
* Add messages for unhandled `unwraps()` on relay start-up (#816).
Co-authored-by: Kirill <[email protected]>
Co-authored-by: Karim <[email protected]>
In Eth2-to-NEAR-relay,
network
,contract_type
, andnear_network_id
parameters are accepted as genericString
types but would be best handled by Rust’senum
types.The text was updated successfully, but these errors were encountered: