7- tenancy

@farhoud hm... aren't we implementing the private network (swarm key) and adding ACL to the private network?
I mean the only difference between public and private is the swarm key, right? Then what is the downside if we add swarm key to the design? Then, If I want to share a pool, I share the swarm key. If I want to keep it totally private, I don't share swarm key

@ehsan6sha
A little note on IPFS-Cluster if we will use it as Pool base:
ipfs-cluster has its own libp2p (host) and this libp2p have have its own network that protect by cluster-secret.
Cluster has state:
File with CID of etc pinned on PeerID etc.
And ipfs-cluster based on this state pin and unpin CID on the IPFS. using RPC interface.
So we can have multiple pools controlling the same instance of IPFS.

@ehsan6sha
There are other way's to create private network like:

• We can use our Identity to create private network by whitelisting and blacklisting of peerIds.

I think we have more knowledge and help like @masih and @ruffiano89 . we should get back to the requirement and concepts and refactor our designs.

Let everyone know and understand the big picture so they could help us improve.

I believe what we have on non-technical big picture is the scenarios we discussed