Technically: yes. The ERC primitive can act as a verification key. All identity data stays off-chain at the platform layer. The protocol anchors the proof, not the data. That said it’s possible if done with discipline and no PII on-chain. Similar like in the CUT protocol, the token isn’t access to the files, it’s authorization to access the decryption key of the files. 👍
As your joke about github vs privacy, I fully agree. But I did this a certain way of several reasons, all design choices has a explanation if you read the docs. And one is the transparency, it’s like 3 clicks then you could verify. It wasn’t about my privacy in relation to the code, it’s privacy regarding real world/“titts-for-tatts”/seller-buyer transactions. But in general my imposter syndrome doesn’t like to much discussions in forums. So I’m pretty good at “post&run” to quietly watch on a distance like a creep. And that’s pretty much what you could expect from me.
Before dismiss anything based on assumptions it is actually possible to verify that this isn’t a AI account. Knowing is better then assuming. 😉 In opposite to a “AI-account” I’m not good at human interaction. Always same result: they’re looking at me, nod their head like they understand. But I see in their eyes they don’t. I just hope that others understand what I’m trying to communicate. But on the other hand the “good catch” is very AI-suspicious. How can I know you’re not 2 AI-accounts that want this dismissed?
Thanks for the link fix, and the appreciation.
Existing platforms settle real-world transactions too, but the rails they run on are owned and operated by someone. That operator can raise fees, gate access, extract data, be acquired, be regulated into compliance, or be pressured by any sufficiently motivated actor. The settlement behavior is only as neutral as the operator chooses to be. These protocols have no operator. The fee is immutable at the protocol layer. The contracts are deployed with renounced ownership. There is no entity that can modify the behavior, no platform that can be captured, and no intermediary between the user and the settlement rail.
Thanks I’ll check it out. 😀
I understand the skepticism and it’s justified, NFTs have gotten a bad rep. =) Personally, I never speculated on NFTs. It’s never been my thing. But the tech itself? Solid. It’s just been misused.
Just because a technology gets applied poorly doesn’t make it inherently bad. This is why I think they’re perfect for this use case:
An NFT is just a digital record of ownership for something non-fungible (i.e., unique and indivisible). Unlike fungible tokens like ETH or BTC (which you can split or mix), an NFT always refers to one unique thing.
In the case of DeDe, the NFT represents a parcel, not a jpg, not art. The NFT holds metadata like:
Parcel ID
Lifecycle state (e.g. Created, PickedUp, Delivered)
Reference to encrypted pickup/dropoff info
It’s not trying to “put the package on-chain,” just anchor its identity and state in a verifiable, tamper-proof way. If someone tries to fake a parcel NFT, the metadata won’t match, you’ll instantly detect it as invalid. This is way harder to spoof than a PDF shipping label or a database entry.
Same tech could be used for:
Title deeds
Car ownership
Event tickets
Access credentials
So yeah, NFT hype was a mess, but the primitive itself is useful when applied to real-world logistics, ownership, and transfer.
Thanks for the thoughtful critique. Some clarification to help:
DeDe isn’t trying to replace FedEx/UPS/USPS.
DeDe is not a platform or an app. It’s a protocol, closer to TCP/IP than Uber.
It handles one function only:
escrow -> pickup -> dropoff -> finalize
Everything else (matching, identity, trust, messaging, routing) is off-chain, by design. That separation is what preserves privacy and prevents metadata leakage.
What problem DeDe actually solves
Not postal logistics, those require fleets, warehouses, and fixed infrastructure.
DeDe addresses the centralized crowdshipping model used by Uber/Doordash/Amazon Flex:
• zero privacy • centralized control • data extraction and surveillance • wage manipulation • platform lock-in • mandatory identity • opaque matching
DeDe gives communities the same underlying mechanics of crowdshipping without a corporation in the middle collecting or exploiting sender/carrier/destination data.
No tracking, no identity, no metadata
Parcel NFTs only encode:
• parcel ID • escrow amount • lifecycle state
No names, addresses, routes, timestamps, or identities. All sensitive information stays off-chain.
DeDe doesn’t broadcast parcels, seek couriers, or coordinate delivery. It only settles funds trustlessly.
No token, no speculation
• no governance token • no staking token • no inflation • no “earn crypto for nothing” • no VC angle
Ethereum is used strictly as a neutral, permissionless escrow layer.
In short
DeDe is a tiny, open, neutral settlement rail for P2P delivery, just infrastructure communities can use or ignore as they like.
Regarding environmental footprint:
Blockchain environmental impact depends on how electricity is produced, not on the existence of computation itself. Electricity demand has been rising for decades, long before blockchains or AI, and will continue to do so.
If critical economic infrastructure depended on abundant, cheap green power, it would create a strong incentive for energy producers to scale sustainable sources faster. The largest investors in green energy today are still heavily tied to fossil fuels, so shifting economic incentives can help accelerate the transition.
deleted by creator
Actually I never thought about it. That’s a good idea. Thanks. =) But all the data about the project needed is in:
Here is a clearer explanation. DeDe is not a courier service and not a gig app. It is only infrastructure, a smart contract protocol.
DeDe is not an app, not a marketplace and not a company. It is a tiny delivery settlement rail that sits on Ethereum, similar to how Bitcoin sits under money transfers and Matrix sits under messaging. Those systems do not provide apps or account systems, they provide rails. DeDe works the same way but for physical delivery.
This is what the protocol actually does. Anyone can register a parcel on chain as an NFT. The sender deposits the parcel value into escrow, because the escrow amount represents the value of the item/parcel/delivery. Anyone who wants to can pick up a parcel and deliver it. It is completely voluntary and there are no assignments, no scheduling and no forced routes. The smart contract holds the escrow until both sides confirm that the parcel arrived. When they agree, the contract releases the payment to the carrier and takes a 0.5 percent transaction fee from the escrow. It is a transaction fee, NOT a parcel fee. The remaining 99.5 percent goes to the carrier.
If someone builds an app or a marketplace on top of DeDe and decides to charge an additional service fee, that fee belongs to that external service. It is outside the protocol, outside the smart contract and outside DeDe entirely. For example, if a carrier receives 95 percent of the parcel value, DeDe still only took 0.5 percent as the transaction fee, while the other 4.5 percent would be the fee of that particular app or marketplace. DeDe does not define or control those business models.
There is no app, no login system, no surveillance layer, no tracking and no central operator baked into DeDe. Those things, if anyone wants them, are built by others. A future marketplace built on top of DeDe becomes a kind of free for all UPS or DHL where senders and carriers meet, but all settlement still flows through the trustless contract. That part is the only responsibility of DeDe.
Carriers can choose any parcel they want. If a parcel matches their daily route, it is efficient and reduces the number of trucks in cities, but they can also deliver completely unrelated parcels if that is what they prefer. with what kind of transport they prefer. Everything is voluntary.
The trust comes from the smart contract. It does not track or identify anyone. It simply releases money when both sides confirm delivery. That is the entire mechanism, a neutral settlement layer for physical logistics. Everything above that, including apps, marketplaces and business logic, belongs to the people who build on top of it.
If anything is unclear I can explain more.
I recently added a cwtch-sidecar implementation template in the substrate repo. Hope it’s interesting.