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 Aug 2, 2021. It is now read-only.
Such a low balance mode will ensure that the node does not cross the payment threshold with any node, thus disabling requesting of chunks and limiting routing of chunks (when near the payment threshold with a node from whom you buy a chunk for the purpose of routing).
per discussion during the weekly research call on 19/12:
we shouldn't have this as a mode, as this should be the regular behavior of the nodes.
if we are processing messages which would put our node above (our version of) the payment threshold, we should stop processing those messages until either: a payment is made, or: messages are exchanged in a way that this debt is reduced. then, we'd resume processing messages until we are at this point again.
we are still keeping the disconnect threshold for the purposes of dropping nodes which don't play nice, i.e. by this rule precisely.
A low balance mode for SWAP is might be used for:
Such a low balance mode will ensure that the node does not cross the payment threshold with any node, thus disabling requesting of chunks and limiting routing of chunks (when near the payment threshold with a node from whom you buy a chunk for the purpose of routing).
On October 24, we spoke about this during the research office hours
I propose to make a SWIP to describe the behavior of a node when he has a low balance and subsequently implement it.
The text was updated successfully, but these errors were encountered: