distributed RMB

[muhamadazmy]

Introduction

The idea behind this story is to move away from the yggdrasil network by running distributed rmb relies. The rmb-peers now establish a connection to a near by rely, and update it's information on tfchain with which public rely it's using plus it's public key used for encryption.

Once connection is established, relies then can receive messages from their clients, to forward them to either a directly connected client or to another rely.

Specs

New specs can found here. Specs are still work in progress and not final, but shows the general idea.

Estimation

While there are still a lot of parts that will be used from current implementation (specially local process to local rmb peer), there are still new parts to be developed, specially the federation and rely to rely communication, hence I give initial estimation of 7 man days.

Docs

https://github.com/threefoldtech/rmb-rs/tree/main/docs

[muhamadazmy]

For encryption we going to use https://docs.rs/k256/latest/k256/index.html

[muhamadazmy]

Changes

• [x] relay (proxy) implementation
• [x] rmb-peer implementation
• [x] message signating/verification
• [x] end to end encryption
  • [x] (depends on: https://github.com/threefoldtech/tfchain/issues/569)
  • [x] Actual message encryption #113
• [x] deployment on devnet
  • [x] Helm chart for relay (depends on: https://github.com/threefoldtech/rmb-rs/issues/97)
  • [x] Update zos to use new peer
• [x] Federation #106

[muhamadazmy]

BLOCKED:

• This story is now blocked on devnet update.
  • We need to update both tfchain with https://github.com/threefoldtech/tfchain/issues/569
  • Update zos node to use new rmb

UPDATE: Not blocked anymore, rmb is already on devnet