---
# System prepended metadata

title: w3filecoin talk

---

# w3filecoin talk

> Verifiable journey of a file into a Filecoin deal

> what is the hook?

U CAN Verify!

chain of custody

TEH VERIFIABLE JOURNEY
(files => ⁂ => deals)

dont trust web3.storage (verify)

Who's aggregating YOUR data?

Did i say you can aggregate that!?

DUDE! WHERE's MY ~~UPLOAD~~ CAR`!?
_(verifiably aggreating 1 bajillion uploads)_
_(verifiably dealing 1 bajillion tiny uploads)_
(UCAN verify data aggregation!!!11)
UCAN verify we put the CARs in the shipping containers

DUDE! WHERE's MY ~~CAR~~ DEAL`!?

Did i say you can deal that!?

_user verifiable deals from 1 bajillion tiny uploads_

from grubby bytes to 

commP at the edge 
> verifiably dealing 1 bajillion tiny uploads

---
DUDE! WHERE's MY ~~UPLOAD~~ CAR`!?
> verifiably dealing 1 bajillion tiny uploads
---

_HASH YOUR OWN DAMN DATA_

**DEAL ME IN**
_(COMMP AT THE EDGE OR DIE TRYING)_
_((verifiably aggreating 1 bajillion uploads))_

VERIFY YOUR OWN DEALS

UCAN verifiably deal 1 bajillion files

Shovelling data into filecoin 

TAKE YOUR CAR TO THE DEALER


note: commp is piececid

>  Once the `StorageProvider` receives the file from the client, they calculate the Merkle root out of the hashes of the Piece (padded .car file). The resulting root of the clean binary Merkle tree is the **Piece CID**. This is also referred to as _CommP_ or _Piece Commitment_ and as mentioned earlier, has to be the same with the one included in the deal.
https://github.com/filecoin-project/specs/blob/936f07f9a444036fe86442c919940ea0e4fb0a0b/content/systems/filecoin_files/piece/_index.md?plain=1#L43

