You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 9, 2023. It is now read-only.
I don't see an option to configure maxcollateral. It seems to be the only way to limit the size (in Bytes) of a contract - which is important to me as a big contract saturates my internet connection for a month.
For some reason, if I set maxcollateral with ´siac host config maxcollateral´, it is soon changed back to the earlier value - possibly by the running host-manager. So is there a field for maxcollateral which I just haven't noticed?
The text was updated successfully, but these errors were encountered:
There is not, it was pruned when the screen was redone since it's a little confusing with how it works. It's now calculated to allow a maximum of 2TB per contract based on your max duration and collateral. The plan is to simplify the base settings even further and offer an "advanced" mode for power users, I just created #52 to track it.
maxcollateral won't do much to limit your bandwidth usage, renters will just form multiple contracts with your host. If you're having bandwidth issues you should look at setting a rate limit with siac ratelimit.
Are you sure the bandwidth is coming from the host module and not syncing traffic from the gateway? There was a bug in the gateway module in v1.5.5 that caused excessive peer bandwidth usage, updating to v1.5.6 dramatically dropped my bandwidth usage
Thanks! Does host-manager still incidentally configure maxcollateral even though it is removed from the front-end?
What I was trying to solve with maxcollateral wasn't bandwidth, but that one single big contract sets the price for a whole month, because it saturates my capacity. But yes, maxcollateral won't solve the problem as the peer can simply do the same by making many contracts.
I don't see an option to configure maxcollateral. It seems to be the only way to limit the size (in Bytes) of a contract - which is important to me as a big contract saturates my internet connection for a month.
For some reason, if I set maxcollateral with ´siac host config maxcollateral´, it is soon changed back to the earlier value - possibly by the running host-manager. So is there a field for maxcollateral which I just haven't noticed?
The text was updated successfully, but these errors were encountered: