Optional hashOptional incomingAn incoming stream must resolve within this number of seconds
30000
Optional maxThis is the maximum number of concurrent inbound bitswap streams that are allowed
32
Optional maxThe maximum size in bytes of an incoming message that we will process.
Messages larger than this will cause the incoming stream to be reset.
Defaults to maxOutgoingMessageSize
2097152
Optional maxThis is the maximum number of concurrent outbound bitswap streams that are allowed
128
Optional maxThe maximum size in bytes of a message that we will send. If a message is larger than this (due to lots of blocks or wantlist entries) it will be broken up into several smaller messages that are under this size.
Optional maxIf the client sends a want-have, and we have the corresponding block, we check the size of the block and if it's small enough we send the block itself, rather than sending a HAVE.
This defines the maximum size up to which we replace a HAVE with a block.
1024
Optional messageWhen sending want list updates to peers, how many messages to send at once
50
Optional protocolThe protocol that we speak
'/ipfs/bitswap/1.2.0'
Optional runWhether to run on transient (e.g. time/data limited) connections
false
Optional sendWhen sending blocks to peers, how many messages to send at once
50
Optional sendWhen a block is added to the blockstore and we are about to send that block to peers who have it in their wantlist, wait this many milliseconds before queueing the send job in case more blocks are added that they want
10
Optional sendWhen sending blocks to peers, timeout after this many milliseconds. This is useful for preventing slow/large peer-connections from consuming your bandwidth/streams.
10000
Enables loading esoteric hash functions