casper-network / casper-network/casper-node

Modify the dry-run-deploys and retrieve-state tools to read the config parameters from the proper chainspec file

Open
#2,564 0 comments 0 reactions 0 assignees View on GitHub
low-priority
Dominant language
Rust
Stars
399
Forks
224
Avg merge
15h 44m
Merged PRs (30d)
2

Description

The tools are now using the forged config parameters, like so:
let merkle_tree_hash_activation = EraId::from(0u64);
and have some others hardcoded, like "test" for network_name.
Such change will make it easier to create storage in pub fn create_storage() function and, in turn, will allow for a more concise code in fetcher (we'll be able to pass the entire ref to chainspec to the Storage::new() instead of several separate parameters, like here).

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.