You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the mm-retrieve branch there is a new config param called StorageAccessApiInfo. The param is at the top level of config. It stores a list of RPC APIs of each miner that boost can read data from. This allows a boost instance that stores data to miner A to also serve data from miner B (because LID stores the indexing information for both miner A and miner B).
In practice the StorageAccessApiInfo parameter is only relevant for graphsync retrievals (booster-http and booster-bitswap have their own mechanisms for specifying the list of miners to serve data from). It would be more appropriate to put it inside the DealMaking section of config where the other retrieval config params are.
The text was updated successfully, but these errors were encountered:
On the
mm-retrieve
branch there is a new config param calledStorageAccessApiInfo
. The param is at the top level of config. It stores a list of RPC APIs of each miner that boost can read data from. This allows a boost instance that stores data to miner A to also serve data from miner B (because LID stores the indexing information for both miner A and miner B).In practice the
StorageAccessApiInfo
parameter is only relevant for graphsync retrievals (booster-http and booster-bitswap have their own mechanisms for specifying the list of miners to serve data from). It would be more appropriate to put it inside the DealMaking section of config where the other retrieval config params are.The text was updated successfully, but these errors were encountered: