DROP Protocol: A Trustless Settlement Rail for Physical Storage

, ,
1

TL;DR
DROP is a minimal Ethereum-based protocol for decentralized physical storage settlement.
It handles escrow and lifecycle, not spaces: No lockers, no warehouses, no matching, no routing, no identity.
Just trustless escrow, deterministic session lifecycle, and immutable protocol fees.

Motivation

DeDe Protocol put P2P delivery on Ethereum mainnet in November 2025.
A gap remained: what happens between the legs?

Multi-hop physical logistics requires intermediate custody.
An item handed off from a DeDe carrier may wait hours in a locker, a container, or a spare room before the next leg picks it up.
That custody handoff has no trustless settlement layer.

More broadly, the physical world has enormous unused storage capacity — spare rooms, lockers, sheds, containers — that sits inaccessible to permissionless coordination.

DROP addresses the settlement side of that gap.
It does not manage the storage. It records that it happened and releases funds when it does.

What It Is

DROP is not a storage company, locker network, or marketplace.
It is a small Ethereum smart contract protocol that allows:

  • A dropper to create a storage session and fund escrow
  • A registered space operator to attest drop and pick on-chain
  • Settlement to finalize deterministically without trusted intermediaries

The protocol governs:

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

All matching, pricing, identity, and UX happen off-chain.

Architecture

Core contracts:

1. DROPCore

  • Deterministic session lifecycle: Created → Dropped → Picked → Finalized
  • Immutable protocol fee: 0.3%
  • Permissionless finalize with a small keeper tip (0.05%)
  • Optional on-chain escrow (ETH or ERC-20) or off-chain settlement anchored by hash

2. DROPSpaceRegistry

  • Operators register spaces with capacity, availability window, coarse location hash, and a hash commitment to off-chain terms
  • Capacity reservation and release gated exclusively to DROPCore
  • No pricing, ranking, matching, or identity on-chain

3. Escrow

  • Holds ETH or ERC-20 funds keyed by storageId
  • Releases to operator, protocol treasury, and permissionless finalizer
  • Trusts only DROPCore as caller

All state transitions are public and auditable.
DROP stores no GPS coordinates, no personal data, and no pricing on-chain.

On-chain Privacy Model

  • On-chain: storageId, state enum, lifecycle timestamps, coarse location hash
  • Off-chain: precise address, photo evidence, access instructions, pricing
  • Evidence anchored via evidenceHash and optional IPFS CID
  • Ethereum only sees hashes

Session Lifecycle

createStorage() -> Created
drop()          -> Dropped   (operator attests; capacity reserved)
pick()          -> Picked    (operator attests; capacity released; finalize window opens)
finalize()      -> Finalized (escrow released to operator)

finalize() is permissionless after pick(). Anyone can call it. The caller receives a small tip.
No centralized keeper or cron server required.

What Makes DROP Unique

  • It’s a protocol, not a platform
  • Operator attests both drop and pick — no counterparty trust required between dropper and operator
  • Escrow is optional — off-chain settlement can be anchored via settlementRefHash
  • Composes naturally with DeDe Protocol for multi-hop logistics:
DeDe carrier → DROP storage operator → DeDe carrier → destination

Each leg settles independently. No protocol knows about the other.

No pricing engine.
No identity layer.
No matching logic.
Just neutral rails.

Economics

  • Protocol fee: immutable, 0.3%, hard-coded at deploy
  • Platform fee: none at protocol level — entirely off-chain concern
  • Finalizer tip: 0.05%, paid to whoever calls finalize() after pick
  • DROP does not decay escrow over time
  • Settlement is conditional on operator attestation, not counterparty confirmation

Why Ethereum?

DROP works best when:

  • The settlement layer is public, neutral, auditable
  • Space operators and integrators are permissionless
  • The infrastructure is not subject to any central actor’s decisions

Relationship to DeDe Protocol

DROP is a sibling protocol, not a dependency.
DeDe handles P2P delivery. DROP handles P2P storage.
Both are minimal settlement rails. Both are composable. Neither requires the other.

A platform combining both gets trustless multi-hop logistics without a central coordinator.

Ethereum Mainnet Deployment:

Source

MIT Licensed

github.com/pablo-chacon/drop-protocol