Is it possible to store a person’s personal documents on IPFS, essentially acting as online document storage.
Furthermore, how would it integrate with a system of document authentication built on NEM’s technology, i.e.
multisig and apostille.
And is all this scalable up to an enterprise level?
Unfortunately, there’s currently no mechanism for private content so I don’t recommend putting private documents on ipfs
unless you use a private network:
This file has been truncated.
# Experimental features of go-ipfs
This document contains a list of experimental features in go-ipfs.
These features, commands, and APIs aren't mature, and you shouldn't rely on them.
Once they reach maturity, there's going to be mention in the changelog and
release posts. If they don't reach maturity, the same applies, and their code is
Subscribe to https://github.com/ipfs/go-ipfs/issues/3397 to get updates.
When you add a new experimental feature to go-ipfs, or change an experimental
feature, you MUST please make a PR updating this document, and link the PR in
the above issue.
- [ipfs pubsub](#ipfs-pubsub)
- [Client mode DHT routing](#client-mode-dht-routing)
- [go-multiplex stream muxer](#go-multiplex-stream-muxer)
- [Raw leaves for unixfs files](#raw-leaves-for-unixfs-files)
- [ipfs filestore](#ipfs-filestore)
- [ipfs urlstore](#ipfs-urlstore)
It’s not ideal, but it is possible to encrypt your files before storing them in IPFS. I’m not familiar with NEM, but you could then in theory use a blockchain to store pointers and pubkeys for those encrypted files