Back to Home

ShippingEscrow

program
0x50fb8066db65...b534a2edbb59
FrontierContract #6,187Exact Bytecode MatchEdit this contract
Deployed January 9, 2016 (10 years ago)Block 821,894

A shipping escrow contract with buyer/seller structs, late delivery penalties, and IPFS cargo documentation.

Frontier EraVerified Source

Historical Significance

An early example of smart contract escrow for physical goods shipping on Ethereum, demonstrating how developers experimented with real-world commerce applications during the Frontier era. The contract includes features like IPFS integration for cargo documentation and time-based penalty calculations.

Context

Deployed in January 2016 during the Frontier era when Solidity was at version 0.1.5. Developers were exploring how smart contracts could facilitate trust in international trade, with escrow being one of the most discussed use cases for blockchain technology at the time.

Key Facts
Deployment Block
821,894
Deployment Date
Jan 9, 2016, 01:22 PM
Code Size
2.5 KB
Gas at Deploy
692,900

Description

A shipping escrow contract deployed during the Frontier era. The contract manages a transaction between a seller and buyer for physical goods shipment. The seller creates the escrow with cargo details (name, description, origin/destination countries, quantity), a penalty rate for late delivery, and an IPFS hash for documentation.

A buyer enters the agreement by calling Agreement() with ETH payment. After a 3-day waiting period (259,200 seconds), the escrowed payment can be released to the seller via ReleasePayment(). The Arrival() function calculates late delivery penalties based on the number of days past the shipped date.

The contract was deployed with test data: seller Dom of Dom Inc., shipping Shoes from China to Germany, with a penalty rate of 15 per day and a maximum of 15 penalty days. The deployer created several sibling escrow contracts on the same day, iterating on the design with different configurations including versions with public getters and a ship() function.

Source Verified

SolidityExact bytecode match(2,531 bytes)
Compiler: soljson

Exact bytecode match (init + runtime). 1955 bytes creation code + 576 bytes constructor args. soljson v0.1.5-v0.1.7 all produce identical output.

Heuristic Analysis

The following characteristics were detected through bytecode analysis and may not be accurate.

Detected Type: program

Bytecode Overview

Opcodes2,531
Unique Opcodes175
Jump Instructions80
Storage Operations54

External Links