3
submitted 1 week ago by pablochacon@lemmy.ml to c/activism@lemmy.ml

The tool applies a structured analytical framework to user-provided source material. Such as: official statistics, government documents, verified news reporting. Outputs findings in three explicit layers: documented facts, observed patterns, and probability assessments. The layers are always kept distinct. Core methodology: refuse the isolated incident framing by default, distinguish formal institutional existence from functional performance, cross-reference government narrative against primary data from those same institutions, weight institutional response to exposure as data equal to the event itself. The reference implementation covers Sweden 2019–2026 and is in the docs directory. The system prompt encoding the methodology is visible in src/App.jsx. Bring your own Anthropic API key. No backend, no data collection. Remember to use good quality data. Better data = Better result.

Repo: github.com/pablo-chacon/pattern-analyzer Tool: https://pattern-analyzer-delta.vercel.app/

[-] pablochacon@lemmy.ml 2 points 2 weeks ago* (last edited 2 weeks ago)

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. 👍

[-] pablochacon@lemmy.ml 1 points 2 weeks ago* (last edited 2 weeks ago)

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.

[-] pablochacon@lemmy.ml 2 points 2 weeks ago* (last edited 2 weeks ago)

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?

[-] pablochacon@lemmy.ml 2 points 2 weeks ago

Thanks for the link fix, and the appreciation.

[-] pablochacon@lemmy.ml 1 points 2 weeks ago

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.

9
submitted 2 weeks ago* (last edited 2 weeks ago) by pablochacon@lemmy.ml to c/privacy@lemmy.ml

I have deployed a collection of independent smart contract protocols on Ethereum mainnet. Each one is finished infrastructure. No governance, no upgrade path, no owner. Ownership is renounced on all contracts. The contracts are deployed and the keys are gone.

This post is for the privacy angle. The full technical documentation is in the repo linked at the bottom.


Minimal data, by architecture

No protocol stores personally identifiable information. On-chain data is limited to cryptographic commitments, timestamps, addresses, and amounts. All sensitive data stays off-chain with the parties involved.

This is GDPR compliant by architecture, not by policy. There is no personal data to protect because the system is not designed to collect it. The deployer controls their own data. The user controls their own disclosure.


No operator, no capture

The contracts are deployed with renounced ownership. There is no entity that can be subpoenaed, pressured, or acquired. The privacy is structural, it holds regardless of what any individual, platform, or authority wants.

Most privacy tools rely on the trustworthiness of an operator. These protocols have no operator to make promises and no operator to break them.


Currency agnostic

Every protocol settles on Ethereum mainnet. What currency a user pays in is a platform decision. A platform can accept XMR, BTC, ETH, fiat, or any combination and convert to ETH at the platform layer before interacting with the protocol.

Combined with the atomic, hop-by-hop settlement structure, this means the payment trail fragments naturally across chains without any privacy feature being explicitly designed in. It is a structural consequence of currency agnosticism and independent atomic settlements.


Human rights and legal grounding

The right to private correspondence is not a crypto argument. It is a human rights argument.

Universal Declaration of Human Rights, Article 12 covers it. ECHR Article 8 covers it. GDPR covers it. A parcel dispatched between two parties with no central record of who sent what to whom is functionally identical to a sealed letter. The legal and moral precedent for protecting that is centuries old.

These protocols are built in that direction. Anyone arguing against this privacy model is arguing against the existing human rights framework.


Documentation, protocol repositories, template repositories, and orchestration examples:

https://github.com/pablo-chacon/the-substrate

[-] pablochacon@lemmy.ml 1 points 5 months ago

Thanks I'll check it out. 😀

[-] pablochacon@lemmy.ml 0 points 5 months ago

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.

[-] pablochacon@lemmy.ml 1 points 5 months ago

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.

[-] pablochacon@lemmy.ml 1 points 5 months ago

Actually I never thought about it. That's a good idea. Thanks. =) But all the data about the project needed is in:

  1. README.md
  2. WHITEPAPER.md
  3. DeDe-FAQ.md
[-] pablochacon@lemmy.ml 1 points 6 months ago

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.

11
submitted 6 months ago by pablochacon@lemmy.ml to c/privacy@lemmy.ml

This is DeDe (Decentralized Delivery) Protocol:

Not a token, not speculation. It’s infrastructure, deployed on Ethereum mainnet.

We’re watching the same pattern everywhere: Postal systems collapsing. Parcels lost, broken, stolen or seized. Increased surveillance, ID requirements, more decay. Less reliability, less privacy, less dignity.

The institutions that were supposed to protect our right to communication are failing, even though privacy of correspondence is guaranteed under UN Article 12 and ICCPR Article 17.

So instead of being stuck in surveillance and Inefficiency-As-A-Service, we have to build parallel systems immune to centralized control. Systems by us for us, in the spirit of the Fediverse:

community-powered

decentralized

permissionless

protocol, not platform

no corporations

no bosses

no surveillance

no extraction

DeDe (Decentralized Delivery) is not a token, not a scam, not a VC product, not a walled garden. It’s a rail, an open delivery settlement layer anyone can build on.

What it does:

Every parcel is an NFT with a lifecycle

Escrow is automatic, trustless, and transparent

Anyone can create an NFT-Parcel

Anyone can carry parcels while they’re already on the move

No fleets, no gig exploitation, no “shadow wages”

Zero extra CO₂, use the movement people already make

Protocol fee is immutable (0.5%), so nobody can rug / extract

Privacy is natively built in.

Fully MIT-licensed & open-source

It’s not a startup. It’s not a marketplace. It’s not a company.

It’s the peoples infrastructure for physical logistics.

Because if we want a free world, we can’t outsource critical communication infrastructure to decaying governments, surveillance corps, or gig economy parasites.

If you want to understand the philosophy behind it, here’s the full manifesto + artwork:

Medium: https://medium.com/@ekarlsson66/dede-the-delivery-rail-for-a-free-world-e7be944b90fc

If you want to poke around the contracts:

DeDe Protocol GitHub (MIT): https://github.com/pablo-chacon/dede-protocol

DeDe Quik-Start Templates GitHub (MIT): https://github.com/pablo-chacon/dede-templates

No pressure to “like crypto.” DeDe is just a tool. Use it, fork it, ignore it. All up to you. More decentralized civilizational fundamentals, means less dependency of collapsing control systems. We must have working alternatives when the centralized systems break down.

Against decay, we build. That’s the spirit of the fediverse. That’s the spirit of DeDe.

pablochacon

0 post score
0 comment score
joined 6 months ago