Implement w3-aggregation client package #773
Comments
1 task
vasco-santos
added a commit
that referenced
this issue
Jun 7, 2023
This PR is a first iteration for w3 aggregate client and API implementations. It follows same patterns we identified while working on `upload-api` and `upload-client` and is agnostic from the deployment service. `aggregate-api` exposes a lib and a set of tests that implementers with infra should follow, as well as the needed interfaces that must be fulfilled. It also includes `fx` usage for `aggregate/offer` return value It follows spec https://github.com/web3-storage/specs/blob/feat/filecoin-spec/w3-aggregation.md There are two interfaces defined in this service: - `offerStore` - responsible for receiving offers to be queued. Implementer receives `commD` of aggregate together with Offer content. These will be used to give SPs. Note that implementer should keep track of the offer's `commD` so that it can query over time when a deal is done (or failures), so that the `fx` invocation can be executed and a receipt generated - `aggregateStore` - store of aggregates already places with SPs (implementor like `spade-proxy` will have this store hooked with spade DB) New detailed issues for above will be created before this PR gets merged. Part of storacha/w3filecoin-infra#19 Closes #772 and #773
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Per storacha/specs#51
The text was updated successfully, but these errors were encountered: