bluebox timelord wont work

[Motophan]

What I am trying to do

-> run bluebox timelord

Why am I using docker
-> windows does not work for bluebox timelord
-> arch linux does not work for bluebox timelord

What did I do?

docker exec -it chia /bin/bash
. ./activate
bash install-timelord.sh

(venv) root@archlinux:/chia-blockchain# ./vdf_bench square_asm 400000
Time: 1857 ms; n_slow: 74; speed: 215.4K ips
a = 0x6ce27bdb0240cadd4f5ba8eda519bfbe0ffd5ad3004ff27b9d6f65c62815265730bce32258434615674124e204f3c3429e6c214fd171846f5c0acf27c754ac42
b = -0x2040323dc47947c6161535b2e1366a274671d9bd1f9cb7644cb0da6b237a886a8414c9d9fa33f3fd9d9072b34561bc51e93ec1fbb341f6a18de5dd5c63fa421f
c = 0x78869cb37a6a7d392b19000ce9dc30358093871a2753ea79c0cabe40e283d1a2f60234c2f2f8777fde662a87f55a4cb7fea3489750e83c9cefff52fc594b19ab

so the vdf is working

here is my docker compose (I do not need to expose the port because I am using the host adapter for nat port forwarding from a consumer internet connection

version: "3.6"
services:
  chia:
    container_name: chia
    restart: unless-stopped
    image: ghcr.io/chia-network/chia:latest
    network_mode: host
#    ports:
#      - 8444:8444
    environment:
      - TZ
      - PUID
      - PGID
      - log_level=INFO
      - service=timelord
    volumes:
      - ~/temp:/plots
      - ~/.chia:/root/.chia
      - ~/.chia_keys:/root/.chia_keys

2024-08-20T08:32:54.483 TLauncher chia.timelord.timelord_launcher: WARNING  Exception while spawning process 2: [Errno -2] Name or service not known
2024-08-20T08:32:54.490 TLauncher chia.timelord.timelord_launcher: WARNING  Exception while spawning process 1: [Errno -2] Name or service not known
2024-08-20T08:32:54.495 TLauncher chia.timelord.timelord_launcher: WARNING  Exception while spawning process 0: [Errno -2] Name or service not known
2024-08-20T08:32:54.536 TLauncher chia.timelord.timelord_launcher: WARNING  Exception while spawning process 2: [Errno -2] Name or service not known
2024-08-20T08:32:54.542 TLauncher chia.timelord.timelord_launcher: WARNING  Exception while spawning process 1: [Errno -2] Name or service not known
2024-08-20T08:32:54.547 TLauncher chia.timelord.timelord_launcher: WARNING  Exception while spawning process 0: [Errno -2] Name or service not known
2024-08-20T08:32:54.588 TLauncher chia.timelord.timelord_launcher: WARNING  Exception while spawning process 2: [Errno -2] Name or service not known
2024-08-20T08:32:54.595 TLauncher chia.timelord.timelord_launcher: WARNING  Exception while spawning process 1: [Errno -2] Name or service not known
2024-08-20T08:32:54.600 TLauncher chia.timelord.timelord_launcher: WARNING  Exception while spawning process 0: [Errno -2] Name or service not known
2024-08-20T08:32:54.641 TLauncher chia.timelord.timelord_launcher: WARNING  Exception while spawning process 2: [Errno -2] Name or service not known
2024-08-20T08:32:54.648 TLauncher chia.timelord.timelord_launcher: WARNING  Exception while spawning process 1: [Errno -2] Name or service not known
2024-08-20T08:32:54.652 TLauncher chia.timelord.timelord_launcher: WARNING  Exception while spawning process 0: [Errno -2] Name or service not known
2024-08-20T08:32:54.694 TLauncher chia.timelord.timelord_launcher: WARNING  Exception while spawning process 2: [Errno -2] Name or service not known
2024-08-20T08:32:54.700 TLauncher chia.timelord.timelord_launcher: WARNING  Exception while spawning process 1: [Errno -2] Name or service not known
2024-08-20T08:32:54.705 TLauncher chia.timelord.timelord_launcher: WARNING  Exception while spawning process 0: [Errno -2] Name or service not known
2024-08-20T08:32:54.746 TLauncher chia.timelord.timelord_launcher: WARNING  Exception while spawning process 2: [Errno -2] Name or service not known
2024-08-20T08:32:54.752 TLauncher chia.timelord.timelord_launcher: WARNING  Exception while spawning process 1: [Errno -2] Name or service not known
2024-08-20T08:32:54.757 TLauncher chia.timelord.timelord_launcher: WARNING  Exception while spawning process 0: [Errno -2] Name or service not known

[Motophan]

Also, the docker container will spam install everything again each time it starts, not sure if thats by design or a happy accident. It hits apt w/ like 200 requests each time I start the container.

[Starttoaster]

When you specify the service variable with any substring containing "timelord" it runs the install-timelord.sh script for you as part of the container's entrypoint, so exec-ing into the container to run it is not required. Since it's part of the entrypoint, this is by design, and you can simply stop doing the docker exec step.

I don't think we've ever tested bluebox timelords working in chia-docker but I'd imagine they should work 🤔 I can look into this a little bit later. Though in practice there's very little benefit in compacting proofs from the blockchain. If I remember correctly, it was found to reduce full_node sync time by a very small amount, and not really do much to decrease the size of the local blockchain database.

[Motophan]

Thanks, I have a lot of compute but my computers need to stay on either w11 or arch. The CNI bluebox timelords are too slow and every day they fall ~ 2500 blocks behind. I want to give you a lot of compute to get caught up and then I could reduce it to 1 or 2 5950x's and that should keep the chain completely compacted.

Docker would be easiest because I would not have to get wsl to mount a linux partition (since it will have db issues on ntfs since writelocks) because docker is crossplatform. I could run this on anything right away w/o setup. A kvm / virtualbox / wsl would be less desirable since I cant just deploy the container to 20 computers at once and get it done asap.

If arch could be added as a aur package I could use that, or the install-timelord.sh added w/ pacman support.

dashboard.chia.net you can see how far we are from current block for compression.

[github-actions]

'This issue has been flagged as stale as there has been no activity on it in 14 days. If this issue is still affecting you and in need of review, please update it to keep it open.'

[github-actions]

'This issue was automatically closed because it has been flagged as stale and subsequently passed 7 days with no further activity.'