-
Notifications
You must be signed in to change notification settings - Fork 648
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
Add genesis-dev.json and move genesis jsons out of root source directory #1591
Comments
Thanks @nathanhourt appreciate the detail and references to the related items. |
Vis-a-vis |
@cedar-book please mention this file in our private testnet docs. |
@pmconrad, yes, I will do that. |
@pmconrad, I have updated the private testnet - Genesis file section
|
Resolve #1591: Relocate genesis and add dev genesis
I have created a draft of this sort of doc here, and referenced this file therein. Comments are welcome. |
this is awesoem work @nathanhourt |
Very good! |
Yes. I've contacted to Nathan. He creates valuable information. I am working on this with him. |
You will find the link below on the https://dev.bitshares.works site. |
@cedar-book I think you should add some links from @nathanhourt 's testnet description to your testnet documentation. |
@pmconrad Thank you for your advice. I will check into that. --> added ref links in this section. How do you think? |
Good, thanks! |
User Story
As a
developer
I wanta readily-available genesis for private testnet setup
so thatI can spin up private networks for testing use with minimal boilerplate or overhead
.To this end, I have added a
genesis-dev.json
which can be used with no modifications to create a testnet and produce blocks on it with the init* accounts.Furthermore, we wish to keep the root source directory as clean as possible. The
genesis.json
file is, by this stage in the maturity of the BitShares network, historical data which is not crucial to current development, and thus is not highly valuable in the root project directory. Accordingly, I move it to thelibraries/egenesis/
folder and place thegenesis-dev.json
file alongside it there.Impacts
Additional Context
The
witness_node
historically provided a--create-example-genesis
flag that would dump out a genesis.json file which could be used without editing to create a private testnet that produces blocks. This flag is no longer supported (ref #1536, #1529), but I would like to preserve a copy of a default-constructed genesis as it allows easy creation of private testnets. Using private testnets like this is an integral part of my workflow when working on core functionality, and I have helped two others in the last week with their private testnets as well, which indicates that I am not the only developer in the community utilizing them.Moreover, the ability to produce blocks on private testnets is useful for the development of new chains or side-chains which could benefit from the Graphene framework, but do not wish to alter the BitShares core protocol.
CORE TEAM TASK LIST
The text was updated successfully, but these errors were encountered: