Peergos integration

[ianopolous]

This is here to keep track of the requirements on IPFS for full integration into Peergos (http://github.com/ianopolous/Peergos -- https://demo.peergos.net)
These are in decreasing urgency:

1. Transactions for spanning multiple writes relative to GC, see: idea: support for transactional groups of writes #106, Add pinning option to all write commands kubo#3544 NO LONGER NEEDED
2. Ed25519 support in IPNS DONE
3. Support for multiple IPNS keys in a single node DONE
4. IPNS with a crypto CAS on the current hash. i.e. a publish which must be a signed(current hash + new hash) NO LONGER NEEDED
5. API to publish a pre-signed IPNS entry (where the daemon doesn't have the private key) This means a cbor based record format. NO LONGER NEEDED
6. Authenticated PubSub which doesn't require giving private keys to ipfs (external signing in application) NO LONGER NEEDED

[ianopolous]

We've got a new one:
5.5 Erasure code support in combination with ipfs clustering. I'm assuming this will have to wait until FileCoin. NO LONGER NEEDED

[ianopolous]

7. Agree on a multi-publickey format, see: Linked-Data Key (Previously Multikey) specs#58

[ianopolous]

We now have ipfs-nucleus which reimplements the core of ipfs that we need, including post-quantum capability-based block level authed bitwap, so closing this.