🗂️ Infra to bill users for egress

[travis]

• Implement rate limiting middleware in Freeway #136
• Implement "accounting" service that tracks user egress and updates Stripe #137
• figure out where we should store gateway-assigned content commitments (and implement it) #138
• Client should authorize Gateway to space/content/serve Spaces by default #158
• Freeway can learn about space/content/serve/* delegations #160
• Update w3link to proxy POST requests to the Freeway UCAN handler #212
• Update web3.storage docs (createSpace) #218
• Update the CLIs & Console to support the new content serve authorization flow #207

Additionally, ensure that the implementation leaves the door open for "private CIDs"

[fforbeck]

Blocked: waiting for Prod deployment of the Indexer Service to continue the release of the other packages.

[fforbeck]

Indexer Service was deployed. The blocker now is the Console App & storacha/client.

About 3 months ago, the console project was updated to use client.capability.blob.get(shard.multihash) from the @storacha/client.

As a result, the w3ui was also updated to use @storacha/client instead of w3up-client.

Additionally, a fallback strategy was added to the Console App to call client.capability.store.get(shard) if blob.get fails for any reason.

However, I recently released a new version of the @storacha/client and noticed that the store capability is no longer present in it — meaning the fallback strategy in the Console App won’t work anymore.

To unblock this task we need to add the store.get back to the @storacha/client.

[fforbeck]

@Peeja I believe we can remove the #140 from this ticket, and close this one. WDYT? I remember we discussed about shipping the v1 without the token authorization stuff because that would required some additional work, etc.

[fforbeck]

@Peeja, I just synced with @travis and we are good to remove the #140 and close this one.
So this is done.