Irakli Gozalishvili

Here is how I think we could solve this problem: 1. When you call `w3 access claim` program should invoke `access/claim` for own agent and all active `account`s. 2. Once...

Had a chat with @travis and we came up with a hybrid option which I think we should go with, specifically: 1. Extend `access/confirm` capability handler so that `with` field...

> I assume we are opting on the implementation to invoke blob/add second time when bytes were written to presigned URL. Can you confirm my assumption? In terms of implementing...

> In the meantime I suggest we go with blob/* for new capabilities until invocation spec given the current implementation limitation with task/delegations. Just not sure if we also want...

> I think we have a similar pattern as w3-filecoin. Here is where my mind is: a. blob/add queues for allocation if content is not already allocated in given space...

> 3\. We store in our store/table (counterpart of allocationStore) this [input](https://github.com/web3-storage/w3up/blob/main/packages/upload-api/src/types.ts#L513-L519). Looking at blob/allocate we are missing issuer and size in the args. > We have the taskCid though,...

I did little bit of archeological digging to try to find out where the issuer is coming from and it looks like it came from this PR https://github.com/web3-storage/w3infra/pull/48 Which in...

> car/multihash checks on migration path a. we currently have carpark-prod-0 in R2/S3. When we perform a store/add we check bytes are there so that we ask users to write...

I think larger underlaying problem is there is no simple way for user to track which shards they can remove and which they probably shouldn't. Only way to this for...

> why does the delegation we already have not accomplish this? eg nft storage would have a paid space on web3-storage. nft storage would run a lambda that delegates UCAN...