[skip changelog] chore: drand: cleanup legacy and unused configs

[ribasushi]

Related Issues

#10476

Proposed Changes

• Remove the network-portion of mainnet just like it was done for incentinet in fix: build: drop drand incentinet servers #10476. This will stop network clients being built for the unused network and will resolve spurious errors like:

{"level":"info","ts":"2024-07-09T15:36:34.379+1000","logger":"drand","caller":"client/optimizing.go:194","msg":"","optimizing_client":"endpoint down when speed tested","client":"HT
TP(\"https://api.drand.secureweb3.com:6875/\").(+verifier)","err":"decoding response: EOF"}

• As per @AnomalRoil remove unused devnet config

Additional Info

[rvagg]

As mentioned on Slack: I'm concerned that removing these configs impact clients syncing the chain from before the epochs where we've bumped the drand beacon. We're on quicknet now as per nv22 but if you wanted to sync prior to quicknet then I think you might need the config for mainnet? And then there's Incentinet used even earlier in the network's life too. Is it necessary to have access to these to sync? Could we make more headway on this issue by attacking how the clients are instantiated and only do it on demand:

lotus/chain/beacon/drand/drand.go

Line 239 in 1b06f5e

func BeaconScheduleFromDrandSchedule(dcs dtypes.DrandSchedule, genesisTime uint64, ps *pubsub.PubSub) (beacon.Schedule, error) {

- i.e. we have one client for each network, so we have 3 for mainnet running now and 2 for calibnet.

[ribasushi]

@rvagg we definitely should not do what you suggested. As I said: youu concern is not applicable, and is easy to validate either way. As luck would have it I currently need a one-time stock-lotus sync of calibnet, which I just started.

as you can see on the right this is running 1.28.1-dev+calibnet+git.4803c0481+api1.5.0 which corresponds to the head of this commit. Stock from-scratch config with the 4 envvars as specified:

LOTUS_API_LISTENADDRESS="/ip4/127.0.0.1/tcp/12347/http" 
LOTUS_CHAIN_BADGERSTORE_DISABLE_FSYNC=1
LOTUS_DISABLE_PRE_MIGRATIONS=1
LOTUS_CHAINSTORE_ENABLESPLITSTORE=0

I wil comment again in a bit once the headers are synced and oce the network moves past its first several upgrades as per schedule

[ribasushi]

About 1 hour to get the headers

Upgraded up through 🦈

I will let it run to finish, some time tomorrow, but it clearly works. Can haz ✅ ?

[rvagg]

#12414 is apparently one result of removing the network config, we've still been using it to look up per-epoch beacons with StateGetBeaconEntry.