Using IPFS in a private test-network.

[bevensteven]

There's an experimental feature that enables private IPFS networks.

ipfs/kubo#3397 (comment)

This might be helpful for building a proof-of-concept network of 2+ nodes. With 2+ nodes we can easily show how a user can use ddash to access information on other nodes through IPFS iff he/she has the permission to (check via Ethereum contract).

[osmode]

nice catch. this emerging feature could be a good way to add another layer of security.

…

On Wed, Aug 30, 2017 at 10:49 PM, bevensteven ***@***.***> wrote: There's an experimental feature that enables private IPFS networks. ipfs/kubo#3397 (comment) <ipfs/kubo#3397 (comment)> This might be helpful for building a proof-of-concept network of 2+ nodes. With 2+ nodes we can easily show how a user can use *ddash* to access information on other nodes through IPFS iff he/she has the permission to (check via Ethereum contract). — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADWp9s62c0mU_8Hqs035M9OL0vJnHKTXks5sdkllgaJpZM4PIVdV> .

[osmode]

IPFS integration has been disabled by default. This allows use of MD5 checksums to prove integrity and authenticity of locally hosted data without requiring that data are hosting a distributed network (undesirable in many cases). Future releases will make it easier to decide which files are shared on IPFS and which files stay local.