IPFS consortium meeting 1

[sponnet]

IPFS consortium meeting 1

Meeting date/time : Sunday oct 15 2017 at 16:00 CEST ( 10:00 EST )

Duration : 43 minutes

Watch the meeting : https://www.youtube.com/watch?v=-BqXzpSaV78

Agenda

1. Voting / governance: we want to to add multisignature modifiers to the addMember and removeMember functions, so the IPFS consortium members can actually vote for adding or removing members. (SP)
2. Instructions on setting up your node (SP)
3. Pitch ideas on how to run and monitor your node (SP)
4. How to promote and reach out to other members that would be interested in joining the consortium.

[gr0kchain]

Possible that you could share the link for this if it is to be attended remotely?

[sponnet]

Here's the link to watch the livestream : http://youtu.be/-BqXzpSaV78

[sponnet]

Meeting notes

Current state

• Scope of the IPFS consortium is currently to have a (mostly Ethereum-focused) participation between projects to persist each other's data.
• Members will discuss additions or removal of members mostly off-chain - but it will require a to-be-defined number signatures from members to actually execute the addition/removal of a member.

Suggested improvements

• implement the Multisig methods for addMember / removeMember ( Eduardo )

• Whisper integration would be a nice addon, because it would not involve doing a transaction. Downside would be that you have no record / replay possibilities for spinning up a new node. Possibly for low-TTL content this might be a good addition. ( sponnet )

• Possibility to add a addHashList(<IPFSHash>,<TTL>) method, where the IPFSHash would contain a list of IPFS hashes ( manifest ) - in the same format as the current IPFS persistence consortium: ( Thomas )

// manifest1.json
[
    "QmYwxuzozCBSD3FLP5Rg1pAXA4qjDtNrdGjyNzqEtr8TKu",
    "QmTrXyK24CAymWj5eATjxrisc8QaJocnGSY11BFFDEvqtH"
]

• possibility to have non-ethereum projects participate in the consortium (TBD by Thomas), maybe inherit some of the manifest techniques of https://github.com/pipermerriam/ipfs-persistence-consortium ? This might require publishing of the IPFS id, which reveals the IP address of your node. Having the IPFSProxy script fetch the manifest directory and essentially do the same as the IPFS persistence consortium would be trivial to add.