search

ethersphere / user-stories

Repository for maintaining user stories
5 stars 32 forks source link

[User-Story] SWAP-only network #64

Open Eknir opened 4 years ago

Eknir commented 4 years ago

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

Eknir commented 4 years ago

Comment from Ralph: https://github.com/ethersphere/swarm/issues/1917#issuecomment-582866222

Eknir commented 4 years ago

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 .