From 86f2b3f4c59bde717fc7a2f630ad84fb49ed8b59 Mon Sep 17 00:00:00 2001 From: thesemaphoreslim <47706575+thesemaphoreslim@users.noreply.github.com> Date: Tue, 20 Aug 2024 10:49:28 -0500 Subject: [PATCH 1/3] Update timelords.md corrected typo in the "chia start..." command for bluebox timelord install from source instructions --- docs/getting-started/timelords.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/getting-started/timelords.md b/docs/getting-started/timelords.md index 0938f674b2..c1979294de 100644 --- a/docs/getting-started/timelords.md +++ b/docs/getting-started/timelords.md @@ -170,7 +170,7 @@ Once you build the Timelord with `sh install-timelord.sh` in the virtual environ - In the `full_node:` section and set `send_uncompact_interval:` to something greater than 0. We recommend `300` seconds there so that your Bluebox has some time to prove through a lot of the un-compacted Proofs of Time before the node drops more into its lap. ## Start the daemon, timelord-launcher, timelord, and node for a Bluebox timelord -chia start full node_timelord +chia start full_node timelord Note - The default settings may otherwise work but if the total effort is a little too much for whatever machine you are on you can also lower the `process_count:` from 3 to 2, or even 1, in the `timelord_launcher:` section. You know it is working if you see `VDF Client: Sent proof` in your logs at INFO level. From 32b2fa2d7e8e9f9c881d41593a4f22a208fe83ca Mon Sep 17 00:00:00 2001 From: thesemaphoreslim <47706575+thesemaphoreslim@users.noreply.github.com> Date: Tue, 20 Aug 2024 10:51:28 -0500 Subject: [PATCH 2/3] Update timelords.md Correct issue with "chia start..." command in bluebox timelord install from source instructions --- docs/getting-started/timelords.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/getting-started/timelords.md b/docs/getting-started/timelords.md index c1979294de..df440adbb3 100644 --- a/docs/getting-started/timelords.md +++ b/docs/getting-started/timelords.md @@ -162,7 +162,7 @@ chia init sh install-timelord.sh # Start timelord (skip this step and proceed below if installing a bluebox or ASIC timelord) -chia start full_node timelord +chia start node timelord # Bluebox timelord setup Once you build the Timelord with `sh install-timelord.sh` in the virtual environment, you will need to make two changes to `~/.chia/VERSION/config.yaml`. From 75609472967194444c3fc12ecfff3078e64947db Mon Sep 17 00:00:00 2001 From: thesemaphoreslim <47706575+thesemaphoreslim@users.noreply.github.com> Date: Tue, 20 Aug 2024 10:52:56 -0500 Subject: [PATCH 3/3] Update timelords.md Corrected typo in "chia start..." command for bluebox timelord install from source instructions --- docs/getting-started/timelords.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/getting-started/timelords.md b/docs/getting-started/timelords.md index df440adbb3..dad5ff2d81 100644 --- a/docs/getting-started/timelords.md +++ b/docs/getting-started/timelords.md @@ -170,7 +170,7 @@ Once you build the Timelord with `sh install-timelord.sh` in the virtual environ - In the `full_node:` section and set `send_uncompact_interval:` to something greater than 0. We recommend `300` seconds there so that your Bluebox has some time to prove through a lot of the un-compacted Proofs of Time before the node drops more into its lap. ## Start the daemon, timelord-launcher, timelord, and node for a Bluebox timelord -chia start full_node timelord +chia start node timelord Note - The default settings may otherwise work but if the total effort is a little too much for whatever machine you are on you can also lower the `process_count:` from 3 to 2, or even 1, in the `timelord_launcher:` section. You know it is working if you see `VDF Client: Sent proof` in your logs at INFO level.