Skip to content

Commit

Permalink
Merge pull request #650 from Chia-Network/update-bb-timelord-install
Browse files Browse the repository at this point in the history
update bluebox timelord install instructions
  • Loading branch information
BrandtH22 authored Aug 19, 2024
2 parents 19ebb51 + 82827bb commit 5d37c3c
Showing 1 changed file with 4 additions and 25 deletions.
29 changes: 4 additions & 25 deletions docs/getting-started/timelords.md
Original file line number Diff line number Diff line change
Expand Up @@ -83,31 +83,7 @@ chia start node timelord &
</TabItem>
<TabItem value="bb-tl">

```bash
# Install packages
sudo apt-get update
sudo apt-get install ca-certificates curl gnupg

# Add GPG key
curl -sL https://repo.chia.net/FD39E6D3.pubkey.asc | sudo gpg --dearmor -o /usr/share/keyrings/chia.gpg

# Set up repository
echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/chia.gpg] https://repo.chia.net/debian/ stable main" | sudo tee /etc/apt/sources.list.d/chia.list > /dev/null
sudo apt-get update

# Install chia-blockchain
sudo apt-get install chia-blockchain

# Bluebox timelord setup
For bluebox timelords you will need to make two changes to `~/.chia/mainnet/config.yaml`.
- In the `timelord:` section, set `bluebox_mode:` to `True`.
- 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.

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.

# Launch timelord
chia start node timelord &
```
The bluebox timelord must be installed from scratch following the instructions [here](/timelord-install#installing-a-timelord-from-source).

</TabItem>
<TabItem value="hw-tl">
Expand Down Expand Up @@ -193,6 +169,9 @@ Once you build the Timelord with `sh install-timelord.sh` in the virtual environ
- In the `timelord:` section, set `bluebox_mode:` to `True`.
- 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

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.

# ASIC timelord setup: install the timelord repo, run the timelord-only chia service, and run the ASIC software
Expand Down

0 comments on commit 5d37c3c

Please sign in to comment.