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 13, 2021. It is now read-only.
Currently, a non-swap-enabled Peer can connect to other protocols like retrieval on a swap-enabled Peer. The accounting hook will cause an error when a message is sent from the swap-enabled peer blocking the send but not disconnecting the peer. This will cause most retrieve requests to always fail if there is a non-swap Peer connected on retrieval (this was encountered during Devcon when nodes connected to nodes from the previous (non-swap) workshop).
User-Story
As a swap-enabled peer, I don't want to be connected to non-swap enabled peers, such that interactions with accounted protocols don't fail
Acceptance criteria
It is impossible for a swap-enabled node to be connected to a non-swap enabled node
Work estimate
t.b.d.
Related Issues
2069: can we already enforce SWAP-only networks by this user-story?
We spoke about this in the research office hour of 13/2. For now, the suggestion as proposed by @ralph-pichler is sufficient (although edge-cases still persist). This needs to be solved properly in the new BEE Stack @janos .
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Rationale
Currently, a non-swap-enabled Peer can connect to other protocols like retrieval on a swap-enabled Peer. The accounting hook will cause an error when a message is sent from the swap-enabled peer blocking the send but not disconnecting the peer. This will cause most retrieve requests to always fail if there is a non-swap Peer connected on retrieval (this was encountered during Devcon when nodes connected to nodes from the previous (non-swap) workshop).
User-Story
As a swap-enabled peer, I don't want to be connected to non-swap enabled peers, such that interactions with accounted protocols don't fail
Acceptance criteria
It is impossible for a swap-enabled node to be connected to a non-swap enabled node
Work estimate
t.b.d.
Related Issues
2069: can we already enforce SWAP-only networks by this user-story?
Epic Link
Stable SWAP
The text was updated successfully, but these errors were encountered: