-
### Description
#3125 upgraded go-filecoin to use `go-libp2pv0.2.1` this caused `go-cidv0.0.1` to be upgraded to `go-cidv0.0.3.` This change has broken the repo migration test `TestMigrateSomeRepo#Ha…
-
### Description
An interface that supports fetching contiguous sets of blocks (e.g. block `B` and 10 of `B`'s parents) must be added to the Fetcher in order for more robust forms of network syncing (…
-
### Description
Currently we consider the initial bootstrapping of a chain to be done after the syncer has synchronously processed the chain up to the head reported by the first peer to respond to a …
-
### Description
When I use a GraphsyncFetcher to fetch tipsets, if the peer I am initially given fails to return the tipsets, I want to use the PeerTracker to failover to a different peer, so that …
-
# Goals
This is a meta issue to track and discuss improving the Bitswap implementation
. Currently, what we have is:
- Bitswap w/o Sessions (https://github.com/ipfs/go-bitswap/blob/master/bitsw…
-
**Describe the bug**:
fatal error: runtime: out of memory
**Expected behavior**:
Min hardware for storage mining
**Diagnostic information:**
OS: Ubuntu 18.04.2 LTS / 8 GB Memory +8 GB Swap …
-
### Description
Messages and their receipts are intended to be separated from the block header (which is all the block data except for those items) and represented in a merkle tree (see [spec](https:/…
-
### Description
Currently the only way to understand what is happening during chain syncing is to read through log messages.
This is difficult and not ideal for users, it's also not convenient f…
-
I thought we agreed on making the Graphsync protocol as simple as possible, with a way to extend it for future needs.
The current proposal that are floating around are not what I had in mind. For m…
-
### Description
Our design should not be storing chain data once in a bitswap datastore and then copying it all over to a chain datastore. Originally I enforced this separation to reason about secur…