Not a valid way to create keys #1

New Issue

str3tch · 2024-10-13T14:56:38+02:00

str3tch commented

2024-10-13 14:56:38 +02:00

It seems like you've tried to create keys for genesis block, but you've missed the guide . What matters:

You don't have to create exact same repo here, just clone it to machine hosting your node
Create a new branch with any name you'de like, make changes and push that branch to the repository
Just create a pull request on the main repository

One of the crucial point, you've missed signing process. You can see it here.
We do not accept unsigned commits in order to avoid "fake users" that can pretend you, in order to put "fake keys" on your behalf. You can find all the necessary information in guide.

The best way is to follow the guide and ask questions if any!
Hope that helps, best regards
str3tch

Hey @IBN It seems like you've tried to create keys for genesis block, but you've missed the [guide ](https://blog.ghostchain.io/generating-keys-genesis-block-application/). What matters: - You don't have to create exact same repo here, just clone it to machine hosting your node - Create a new branch with any name you'de like, make changes and push that branch to the repository - Just create a pull request on the main repository One of the crucial point, you've missed signing process. You can see it [here](https://git.ghostchain.io/IBN/MrBoec/commit/485d50e4d76b1e66e494920ff6e0f6a16f5843ff). We do not accept unsigned commits in order to avoid "fake users" that can pretend you, in order to put "fake keys" on your behalf. You can find all the necessary information in guide. The best way is to follow the guide and ask questions if any! Hope that helps, best regards str3tch

str3tch added reference main

2024-10-13 14:57:11 +02:00

IBN was assigned by str3tch

2024-10-13 14:57:22 +02:00

IBN commented

2024-10-29 10:44:08 +01:00

Hey @IBN

It seems like you've tried to create keys for genesis block, but you've missed the guide . What matters:

You don't have to create exact same repo here, just clone it to machine hosting your node

Create a new branch with any name you'de like, make changes and push that branch to the repository

Just create a pull request on the main repository

One of the crucial point, you've missed signing process. You can see it here.
We do not accept unsigned commits in order to avoid "fake users" that can pretend you, in order to put "fake keys" on your behalf. You can find all the necessary information in guide.

The best way is to follow the guide and ask questions if any!
Hope that helps, best regards
str3tch

Thanks for the your comment
Now I finish all steps and I think it is correct
I have one question -
Who will give me a correct string to start a node instead of :
./ghost/ghost-node/target/release/ghost --port=30334 --rpc-port=3001 --chain=spec.json --node-key=0000000000000000000000000000000000000000000000000000000000000002 --base-path=/tmp/bob --bob --validator --unsafe-rpc-external --no-telemetry --state-pruning=archive --no-private-ip --no-mdns --bootnodes /dns/bootnode0.chain.ghostchain.io/tcp/30333/p2p/12D3KooWEyoppNCUx8Yx66oV9fJnriXwCcXwDDUA2kj6vnc6iDEp --no-hardware-benchmarks

> Hey @IBN > > It seems like you've tried to create keys for genesis block, but you've missed the [guide ](https://blog.ghostchain.io/generating-keys-genesis-block-application/). What matters: > > - You don't have to create exact same repo here, just clone it to machine hosting your node > - Create a new branch with any name you'de like, make changes and push that branch to the repository > - Just create a pull request on the main repository > > One of the crucial point, you've missed signing process. You can see it [here](https://git.ghostchain.io/IBN/MrBoec/commit/485d50e4d76b1e66e494920ff6e0f6a16f5843ff). > We do not accept unsigned commits in order to avoid "fake users" that can pretend you, in order to put "fake keys" on your behalf. You can find all the necessary information in guide. > > The best way is to follow the guide and ask questions if any! > Hope that helps, best regards > str3tch Thanks for the your comment Now I finish all steps and I think it is correct I have one question - Who will give me a correct string to start a node instead of : ./ghost/ghost-node/target/release/ghost --port=30334 --rpc-port=3001 --chain=spec.json --node-key=0000000000000000000000000000000000000000000000000000000000000002 --base-path=/tmp/bob --bob --validator --unsafe-rpc-external --no-telemetry --state-pruning=archive --no-private-ip --no-mdns --bootnodes /dns/bootnode0.chain.ghostchain.io/tcp/30333/p2p/12D3KooWEyoppNCUx8Yx66oV9fJnriXwCcXwDDUA2kj6vnc6iDEp --no-hardware-benchmarks

str3tch commented

2024-10-30 19:18:17 +01:00

Your pull request is valid on the main repository, thank you!

Correct command will be in the upcoming guide for the early validators. If your are interested in how the command will look like, check the scripts/starter.sh script under the --set-arguments flag. Feel free to modify systemd unit file, arguments or anything you want, script is just automation tool for the node operators.

For sure it's recommended to await for the guide if you are not 100% sure how it is working. Due to the fact that tomorrow will be the last day to fill the ghosties file, there's no genesis file and there's no bootnode running it.

Let's keep in touch and if you have any question you are welcome!

Your pull request is valid on the main repository, thank you! Correct command will be in the upcoming guide for the early validators. If your are interested in how the command will look like, check the `scripts/starter.sh` script under the `--set-arguments` flag. Feel free to modify systemd unit file, arguments or anything you want, script is just automation tool for the node operators. For sure it's recommended to await for the guide if you are not 100% sure how it is working. Due to the fact that tomorrow will be the last day to fill the ghosties file, there's no genesis file and there's no bootnode running it. Let's keep in touch and if you have any question you are welcome!

Sign in to join this conversation.

No Label

No Milestone

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: IBN/MrBoec#1