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
Currently, Eth2-to-Near-relayuses some hard-coded values on contract initialization: validate_updates, verify_bls_signatures, hashes_gc_threshold, max_submitted_blocks_by_account, trusted_signer. These values should be stored in the configuration file.
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]>
Currently,
Eth2-to-Near-relay
uses some hard-coded values on contract initialization:validate_updates
,verify_bls_signatures
,hashes_gc_threshold
,max_submitted_blocks_by_account
,trusted_signer
. These values should be stored in the configuration file.The text was updated successfully, but these errors were encountered: