DEV Community: Emil

Immutable settlement protocols for real-world assets: deployed, ownerless, open templates

Emil — Sat, 02 May 2026 18:16:56 +0000

I have deployed a collection of independent smart contract protocols on Ethereum mainnet. Each one is finished infrastructure:
Immutable, ownerless, no upgrade path. This post is a technical introduction to what they are, how they are structured, and how to build on them.

The pattern

Every protocol follows the same two-component structure:

An ERC primitive that represents a physical or digital asset on-chain
Immutable smart contracts that handle neutral, deterministic settlement

That is the complete structure. No governance hooks. No admin functions. No upgradeability. Ownership renounced on all contracts at deployment.

Each protocol also has a quick-start templates repository:
Minimal, auditable reference implementation that shows the direct path to building on the protocol without going through any platform or intermediary.

The protocols

DeDe: parcel delivery settlement
ERC-721 parcel primitive. Pickup, dropoff, finalize lifecycle. Automatic finalization after 72 hours. Immutable 0.5% protocol fee. Permissionless finalization with finalizer tip. Signer registry with mandatory stake and slashing.

DROP: physical storage settlement
ERC-721 storage session primitive. Drop, pick, finalize lifecycle. Optional escrow. Immutable 0.3% protocol fee. Storage node registration via DROPSpaceRegistry with coarse location commitment and hash commitment to off-chain terms.

CUT: digital ownership and rights settlement
ERC-1155 media primitive. Fractional or full ownership of any digital medium. Scene registry for content anchoring. Direct purchase from minter.

KEY: vehicle ownership and sale settlement
ERC-721 vehicle identity anchor. Immutable VIN and spec hash commitments. Atomic sale settlement with buyer-funded escrow. Fixed 5-day finalization and dispute windows, protocol constants, not adjustable. 0.3% protocol fee. In jurisdictions where vehicle registries expose APIs, platforms can initiate legally recognized ownership transfers triggered from the decentralized side.

STAY: commodity settlement
ERC-721 commodity primitive. Access rights and transfer settlement for commodity assets.

ACT: physical service settlement
ERC-721 service primitive. Agree, deliver, confirm, finalize lifecycle. Protocol-neutral about service type and scale.

Architecture: blockchain microservices

The closest analogy is microservices. Each protocol is a self-contained service with a single responsibility. It exposes a deterministic interface. It has no opinion about what surrounds it.

No protocol knows the others exist. There is no shared state, no internal coupling, no common coordinator. Each one lives and fully function in complete isolation.

Platforms orchestrate them at the layer above, the same way a system orchestrates independent services without modifying the services themselves. A logistics platform might combine DeDe and DROP. A vehicle marketplace might use KEY alone. A media platform might use CUT alone. None of these require any other protocol.

The difference from conventional microservices is permanence. These cannot be taken down, modified, or redeployed by their operator. The behavior defined at deployment is the behavior forever.

Templates

Every protocol has a separate quick-start templates repository. The templates are minimal reference implementations. Not SDKs, not frameworks. They are the correct, direct way to interact with the protocol. Readable, forkable, deployable by anyone.

The template path is always open. No platform can close it.

Deployed contracts

All contracts are verified on Etherscan. Ownership renounced. Contract addresses are in the individual protocol repositories.

DeDe: deployed November 2025
DROP: deployed April 2025
CUT, KEY, STAY, ACT: deployed May 2026

Where to start

The Substrate is a documentation index for all the protocols. Protocol repositories, template repositories, contract addresses, and orchestration examples are all in one place.

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

pablo-chacon-ai@proton.me

DeDe Protocol: Trustless Settlement Layer for Physical Delivery

Emil — Wed, 10 Dec 2025 15:11:33 +0000

TL;DR
DeDe is a minimal Ethereum-based protocol for decentralized physical delivery.
It handles settlement, not logistics: No fleet, no terminal, no app, no routing, no identity.
Just trustless escrow, deterministic parcel lifecycle, and immutable protocol fees.

Motivation

We have decentralized infrastructure for:

Money (Bitcoin)
Communication (Matrix)
Compute (Ethereum)
Privacy (Tor)

But physical delivery still a key part of human coordination remains centralized, fragile, and opaque.

Postal systems are slow, expensive, often fail to deliver, and structurally incompatible with privacy.
Meanwhile, enormous underutilized capacity exists in everyday human movement:
people walk, bike, drive, and commute along routes that could carry parcels.

DeDe lets anyone tap into that movement.
It enables real-world delivery as a trustless, peer-to-peer settlement flow, not a logistics monopoly.
What It Is

DeDe is not an app, not a marketplace, and not a company.
It is a small Ethereum smart contract protocol that allows:

Senders to register a parcel NFT + escrow
Carriers to voluntarily pick it up
Delivery to be confirmed (opt-in)
Settlement to be finalized without trusted intermediaries

The protocol governs:

Who gets paid
Under what conditions
How funds are held and released
Immutable protocol fee routing
Minimal incentive alignment

All logistics, routing, and app-specific behavior happens off-chain.
Architecture

Core contracts:

ParcelCore

ERC-721 parcels with deterministic lifecycle states
Immutable protocol fee (e.g. 0.5%)
Support for platform-level BPS fee schedules
Finalization window (e.g. 72h after pickup)

Escrow

Holds ETH/ERC-20 funds keyed by parcelId
Releases funds to carrier, protocol treasury, platform treasury, and finalizer tip
Enforces deterministic payout logic

AStarSignerRegistryStaked

(Optional) registers routing signers with stake
Ties dropoff event to a verifiable off-chain route hash
Allows eventual zkRoute integrations

All state transitions are public and auditable.
DeDe does not include any GPS, KYC, login systems, or metadata on-chain.
On-chain Privacy Model

On-chain: only tokenId, state enum, and lifecycle timestamps
Off-chain: pickup/dropoff locations, photo proofs, routing paths
Metadata is stored in NFT, encrypted, or referenced via IPFS hashes
Ethereum only sees a hash

What Makes DeDe Unique

It’s a protocol, not a platform
No centralized operator, job board, or trusted intermediary
Anyone can build an app, mint a parcel, or pick one up
Payments settle only if both sides confirm (or finalize automatically)
Protocol fee is immutable, finalizer tip is capped, all logic is deterministic

No pricing engine.
No identity layer.
No assignment logic.
Just neutral rails.
Use Cases

P2P delivery during commutes (side income for regular people)
Local business delivery without contracts or apps
Decentralized logistics experiments (DAOs, disaster relief, rural mobility)
Trust-minimized gig networks in low-trust regions

Economics

Protocol fee: immutable (e.g. 0.5%)
Platform fee: configurable, set by each integrator
Finalizer tip: small % (e.g. 0.05%), capped
DeDe does not reduce escrow value over time (no built-in decay)
Settlement is voluntary; payment is conditional on mutual confirmation

Why Ethereum?

DeDe works best when:

The settlement layer is public, neutral, auditable
Applications are permissionless and forkable
The infrastructure isn’t subject to any central actor’s control

Deployed to Ethereum Mainnet

ParcelCore: 0xeF1D4970c3B988840B13761Ec4FBb85106d789F8
Escrow: 0x834317eFB2E6eE362a63474837398086cC302934
AStarSignerRegistryStaked: 0x311A4c3Ed79D4467C55dd7CEE0C731501DF3f161
protocolTreasury: 0x9C34d6a6BF1257A9e36758583cDC36F4cE2fA78F

Related Work / Inspiration

Matrix (as infra for decentralized messaging)
Monero (for privacy guarantees in adversarial environments)
Tor / IPFS / Nostr (for neutrality under pressure)
Ethereum itself (as settlement infrastructure)

Future Directions

zkDeliveryProofs (optional: SNARKs for delivery receipt)
L2 deployment for micropayments
Local delivery DAO coordination
Indexers / GraphQL APIs / “DeDeScan” explorer
Mobile UX kits and white-label apps
Monero bridge / atomic swaps for cross-chain delivery privacy

Repository

DeDe-Protocol Repository