TL;DR: CARs are a great way to ensure end-to-end integrity for user uploads, but working with them is hard and they aren’t broadly supported. Why CAR uploads matter? As part of the Dapps Working Group, we spend a lot of time thinking and providing tooling to make verified retrieval the norm. Howev…

@danieln we’re currently working on a client refactor that will make using it significantly more enjoyable than it is right now. It’ll be out VERY soon! We went through a number of iterations of the service before we finally settled where we are today and an unfortunate artifact of that is that the…

To add one more thing to what @alanshaw just said. DIDs and UCANs are what allows delegated uploads and allows end user and not a server in the middle to be in charge, so part of what you found appealing about web3.storage in comparison is the cause of the complexity. That said if that is not the r…

The market doesn’t seem to care about CAR uploads. We’ll have an end to end CAR go mirror soon-ish that has two features: synch faster than re-uploading — because it uses bloom filters to negotiate what blocks need to get transferred over HTTPs I’ll bug Philipp to drop some links here. Note tha…

Will be the first to admit that I have limited experience with UCANs, but can you help me understand a bit more what’s going on here? Why would you need to keep anything secret? Perhaps I’m misunderstanding but right now you have a GraphQL-like API where the request data is in the body like specs/w…

FWIW I agree that this seems sensible. However, I think there’s room for both. In particular, some storage providers (e.g. web3.storage) have built their infra to optimize around storage of CARs including to the point of handing users back proofs that will allow them to see their CARs being provabl…

My point was not to diss CAR. As I said, we’ve implemented CAR go mirror over https transport because it solves the problem of being performant and being reliable on all clients, including having low battery usage on mobile. My observation is that commercial operators tend to be pretty far away fr…

I’m misunderstanding but right now you have a GraphQL-like API where the request data is in the body So, the body IS the signed UCAN invocation. It includes the capability (can), resource (with) and parameters (nb). There’s no need to split these things out and put them in the URL - you’d lose ve…

[image] alanshaw: There’s no need to split these things out and put them in the URL - you’d lose verifiability of the requested invocation (unless you can repeat them in the UCAN). Sure you can repeat the information or it can be implied from the path (i.e. before you compute the hash used fo…

Back on topic: @danieln shared some feedback and wants to be able to confidently point developers at an approach to uploading to IPFS. And: that multiple commercial providers had different approaches. I think that product teams are going to pick what works for them for a variety of reasons. I’d lo…

Uploading CARs and user generated CIDs

boris February 21, 2024, 7:22pm 4

Ah this might be interesting for wovin team to integrate All-in-one Docker image with IPFS node best practices

cc @gotjoshua @tennox

Topic		Replies	Views
IPFS for publishing research data: CAR files? Ecosystem and Usage research , archive	13	895	July 20, 2022
All-in-one Docker image with IPFS node best practices Ecosystem and Usage kubo , docker	41	4197	December 12, 2024
How to upload file to IPFS with only front-end	31	7668	May 5, 2022
Work-plans for kubo, helia, & other Shipyard IPFS projects in 2025 kubo , helia	12	611	December 12, 2024
How to retrieve content uploaded via Helia using the IPFS gateway? Helia	16	6310	October 28, 2023

Uploading CARs and user generated CIDs

Related topics