Skip to content
This repository has been archived by the owner on Aug 2, 2021. It is now read-only.

Low balance mode #1996

Closed
Eknir opened this issue Nov 29, 2019 · 2 comments
Closed

Low balance mode #1996

Eknir opened this issue Nov 29, 2019 · 2 comments

Comments

@Eknir
Copy link
Contributor

Eknir commented Nov 29, 2019

A low balance mode for SWAP is might be used for:

  • zero-eth entry
  • boot up while synching
  • blockchain backend now working during operation
  • Out of balance during operation
  • Not depositing during deployment

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.

@mortelli
Copy link
Contributor

mortelli commented Dec 19, 2019

related, possibly duplicate: #1948

@mortelli
Copy link
Contributor

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.

related work on this will be continued on #1948.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants