-
Notifications
You must be signed in to change notification settings - Fork 0
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
code editing instructions and some restructuring #451
code editing instructions and some restructuring #451
Conversation
basic example targets starting the Nerpa network with the minimum pieces required for a public devnet all other information is organized under an advanaced usage section
NETWORK_SETUP.md
Outdated
``` | ||
|
||
### Importing keys to lotus repository | ||
|
||
Note: Be sure to set the `LOTUS_PATH` before running the command if using a non standard location. | ||
|
||
``` | ||
lotus-shed keyinfo import <filename>.keyinfo | ||
lotus-shed keyinfo import bls-<filename>.keyinfo |
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 can import any keyinfo file create by lotus-shed keyinfo new command. More info is in the lotus-shed keyinfo new command.
$ lotus-shed keyinfo new --help
NAME:
lotus-shed keyinfo new - create a new keyinfo file of the provided type
USAGE:
lotus-shed keyinfo new [command options] [bls|secp256k1|libp2p-host]
DESCRIPTION:
Keyinfo files are base16 encoded json structures containing a type
string value, and a base64 encoded private key.
Both the bls and secp256k1 keyfiles can be imported into a running lotus daemon using
the 'lotus wallet import' command. Or imported to a non-running / unitialized repo using
the 'lotus-shed keyinfo import' command. Libp2p host keys can only be imported using lotus-shed
as lotus itself does not provide this functionality at the moment.
NETWORK_SETUP.md
Outdated
TODO: This should be a command in lotus-seed to add accounts | ||
TODO: There needs to a way to set the actor ID 90 account. | ||
To generate the genesis car file, starting a lotus daemon is required. The `genesis.car` file will be created along side | ||
the `genesis.json` file at `genesis.car` (this is a detail of this script). |
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 daemon bit is before we had the lotus-seed genesis car command. I think we can just remove this entire 2 lines, as the lotus-seed genesis command also has an output flag.
NETWORK_SETUP.md
Outdated
GENPATH=$(mktemp --suffix=genesis -d) | ||
Note: All pre-sealed miner daemons must be connected, this can be done by manually connecting them by running a | ||
`lotus net connect` from all miners to the genesis miner's daemon. However, we recommend that you setup proper bootstrap | ||
nodes and compile their addresses into the lotus daemon using the `build/bootstrap/bootstrappers.pi`. |
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.
build/bootstrap/demonet.pi
?
NETWORK_SETUP.md
Outdated
lotus-miner init --actor t01000 \ | ||
--sector-size <sector-size> \ | ||
--pre-sealed-metadata /storage/t01000/pre-seal-t01000.json \ | ||
--pre-sealed-sectors /storage/t01000/pre-seal-0 \ |
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.
--pre-sealed-metadata ~/.genesis-sectors/pre-seal-t01000.json
--pre-sealed-sectors ~/.genesis-sectors/
NETWORK_SETUP.md
Outdated
|
||
Let's create a bootstrap node list at `build/bootstrap.demonet.pi` |
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.
build/bootstrap/demonet.pi
demonet
instructions as basic example