Proxy / Bridge node using swarm.key

[0zAND1z]

Following up on our conversation from IPFS Discourse here.

How about creating a Layer-2 alike key management for an IPFS node to bridge the contents between two heterogeneous IPFS cluster having their own respective swarm.keys?

All thoughts & approaches are welcome.

[0zAND1z]

@Kubuxu, any time slots available to discuss more on this??

[machawk1]

Here is a scenario that would make this ability useful to me:

In ipwb I anticipate using IPFS swarms to allow sharing of web archives between a select set of peers. These captures may contain personal/private information that necessitates these capture not being accessible to the whole IPFS network.

The continued privacy of the network's contents relies on protection of this key. However, in the situation where a group (A) wants to proactively share the contents with another private network (B), being able to manage and propagate multiple keys (peers in B become aware of A) for multiple networks from a single perspective (peers in A do not become of B peers) may be useful.

This may facilitate not just a hierarchy of a peer network with respect to privacy but a directional graph. B may know of {A,B} and C maybe just {C,B} then D can be made aware of any permutation/combination of networks based on a network's members sharing of keys. This may also work on the micro level of having select accessibility within an organization, e.g., Alice, Bob, and Carol are all part of network A and the above is applied.

I am not familiar enough with inner working of IPFS to know how much of this ability already exists in the core protocol.

[chiragg6]

Can we use https://github.com/ipfs/js-ipfs/tree/master/examples/circuit-relaying for this purpose?

[0zAND1z]

@Kubuxu , any thoughts on using the Circuit Relay for bridging two different IPFS swarm clusters?
https://github.com/libp2p/js-libp2p-circuit/blob/master/README.md

[Kubuxu]

It is not possible at the time. I fully understand this would be useful, please raise this issue in https://github.com/libp2p/go-libp2p .

[0zAND1z]

This issue will be moved to libp2p. Thanks for all the inputs!