4 ms·
We've been pioneering privacy and access control on top of IPFS since 2015 in Peergos [0]. We have block level access control for example: https://peergos.org/
by ianopolous 3y ago
We've been pioneering privacy and access control on top of IPFS since 2015 in Peergos [0].
We have block level access control for example: https://peergos.org/posts/bats https://peergos.org/posts/bats
As well as E2EE, sharing, trustless servers and more [1].
[0] https://github.com/peergos/peergos https://github.com/peergos/peergos
[1] https://book.peergos.org https://book.peergos.org
- rglullis 3y agoOk, that is really cool. I worry though that this is too tied into the whole peergos architecture? Can you give some pointers on what would I need to do to have a node with the extended protocol and nothing else?
- ianopolous 3y agoThe block auth is very generic, just an extra top level key in cbor maps or a small prefix in raw blocks. The protocol is S3 V4 signatures. There is a Java implementation of the modified bitswap for this in Nabu [0] and a Go one in ipfs-nucleus [1]. With both of these you can use whatever auth verification protocol you like. [0] https://github.com/peergos/nabu https://github.com/peergos/nabu [1] https://github.com/peergos/ipfs-nucleus/ https://github.com/peergos/ipfs-nucleus/