Peter-Jan Brone

hm so this is a breakdown of the release field on 1.6.0 hosts: ``` host_release cnt "" 181 "hostd v1.0.4" 174 "hostd v1.1.0-beta.2" 45 "hostd b194b8f" 12 "hostd dafc054" 2...

@daniel-lucio the first error indicates the caller cancelled the request, the second error indicates you don't have enough contracts. Even though your configuration is correct and from the first error...

@daniel-lucio reported he can no longer reproduce the error and his `renterd` is running fine. I think this was likely related to a networking related issue on his side, maybe...

@ChrisSchinnerl mind taking a look at this `DRAFT` if this is reasonable as a fix for pre v0.2.1 hosts?

This is marked as `high` priority but I'm not sure if it's still all that relevant? The hosts that are marked offline now are shown offline in siastats as well...

Small update on this one: it appears churn caused by hosts going offline has dropped drastically. At the time of writing there's only two hosts on `arequipa` that churned because...

I opened this a `DRAFT` because I'm not sure whether we should change it. I encountered it when writing a test and it did feel weird at the time. It...

I have been running `dev` on my node that manages 4TB and constantly uploads/downloads and deletes data. Several TB per day. That node has pruning enabled and has been running...

unassigned so others can pick it up - feel free to reassign though if you are working on it @dbarnwal

@ChrisSchinnerl push this back to backlog?