ipfs-nucleus VS SecureValueRecovery

The 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

[1] https://github.com/peergos/ipfs-nucleus/

I love this part: https://github.com/Peergos/ipfs-nucleus

I've tried IPFS before but I hit a bug when using it so gave up on my idea for a side project. Might give this a go!

Yep, we built a super minimal ipfs replacement - ipfs-nucleus (https://github.com/peergos/ipfs-nucleus) with added block level access control, which is also post-quantum.

It's actually a mixture of Java, Go, and JS. E.g. all the P2P stuff is handled by ipfs-nucleus: https://github.com/peergos/ipfs-nucleus/

No one needs to install IPFS. Peergos automatically installs and manages it's own IPFS instance. It's actually a super minimal drop-in IPFS replacement - ipfs-nucleus (https://github.com/peergos/ipfs-nucleus) with extended access control. Self hosting instructions are here: https://github.com/peergos/peergos#usage---self-hosting

There are other services out there; sailing past our own purpose-built datastores like the secure value recovery system and contact-discovery system, though, DynamoDB, Redis, and Bigtable are the main things we use that somebody might call a "database."

Consider writing some small-ish tasks (e.g. here: https://github.com/signalapp/SecureValueRecovery/issues) that interested folks could look at to see if the work is interesting.