Deploy the egress billing system to the Production environment.

[fforbeck]

Tasks

• Stripe Billing Meter Enabled
• Deploy Freeway (feat: enable egress tracking in production env freeway#135)
  • Egress Tracking Enabled
  • KV Delegation Store Enabled
  • Rate Limit Disabled
  • Gateway Signer Key
• Deploy W3link Freeway Proxy (UCAN Invocations) (chore(main): release w3link-edge-gateway 1.4.0 w3link#63)
• New release of
  • w3up/w3up-client
  • upload-service/w3up-client
• Update w3up-client package in
  • w3cli
  • storacha/cli
  • w3ui/core
• Update w3ui/react package in
  • Console App
• Fix CORS preflight issue in w3s.link so we can create spaces and authorize Storacha Gateway to serve content of the new spaces #260
• Add flag to set % of traffic that uses new indexing service #223
• New release of w3-cli
  • storacha/w3cli@1ef2478

[fforbeck]

Blocked: waiting for the Prod deployment of the Indexer Service to continue with 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]

• Task unblocked. I've updated the w3ui/core to use the latest version of the @web3-storage/w3up-client.

[fforbeck]

Done.