Currently work is synced like this:
- at the end of each epoch, all peers upload the entire list of work completed to IPFS
- broadcast the content address to all peers
- all peers download and merge it into their list of work
This could be made more efficient. The best solution would be to create a linked list of content that could be traversed. Once IPNS is available in js-ipfs then a well- known static root could be the starting point. in the meantime, we can design around that.
Another option that would buy some time would be for each peer to only send their latest completedWork to 1 other peer. That peer then merges that list with their completed work list and sends it to another peer. this would greatly reduce the number of lookups to IPFS
Currently work is synced like this:
This could be made more efficient. The best solution would be to create a linked list of content that could be traversed. Once IPNS is available in js-ipfs then a well- known static root could be the starting point. in the meantime, we can design around that.
Another option that would buy some time would be for each peer to only send their latest completedWork to 1 other peer. That peer then merges that list with their completed work list and sends it to another peer. this would greatly reduce the number of lookups to IPFS