Back to Home

Marriage Registry

Registry
Part of The Hudson Jameson Collection
0x58641cded077...e96837cc79f4
FrontierContract #5,894Exact Bytecode MatchEdit this contract
Deployed January 2, 2016 (10 years ago)Block 784,787

Records marriages and life events on the Ethereum blockchain with partner details, dates, and status tracking.

Frontier EraVerified Source

Historical Significance

The Ethereum Marriage registry is an early example of Ethereum being used for social and civil record applications rather than purely financial or token-based purposes.

Context

In early 2016, Ethereum developers were actively experimenting with real-world use cases to explore what decentralized computation and permanent public records could enable. This contract was deployed during a period of rapid experimentation following Ethereum’s 2015 launch, before standardized token interfaces and application patterns had fully emerged.

Key Facts
Deployment Block
784,787
Deployment Date
Jan 2, 2016, 06:50 AM
Code Size
1.4 KB
Gas at Deploy
410,204
Transactions by Year
20169

Description

The first marriage recorded on the Ethereum blockchain, deployed Jan 2, 2016 by hudson.eth (Hudson Jameson). It stores two partner names, a marriage date, a status field, and image and document hashes, and emits a MajorEvent log for marriage creation and later life events. This original on-chain version was never published; the source in Souptacular/marriage-dapp is a later revised deployment. Reconstructed and compiled with soljson v0.1.5 (optimizer ON) to a 1,378-byte runtime that matches the on-chain code byte for byte. The compiler is pinned to v0.1.6 or earlier because the contract logs an indexed bytes event argument without hashing it, behavior that v0.1.7 changed.

Source Verified

SolidityExact bytecode match(1,414 bytes)
Compiler: 0.1.5+c

Runtime bytecode reproduced exactly with soljson v0.1.5+commit.23865e39, optimizer ON, via the legacy compile(source, 1) API. Output is identical across the v0.1.4-nightly to v0.1.6 window; v0.1.7 and later hash indexed bytes event arguments, which this contract does not do, pinning the compiler to v0.1.6 or earlier. External verification (2026-06-28): Sourcify verified, exact match on runtime and creation bytecode (matchId 38141663). Etherscan verified with v0.1.5+commit.23865e39, optimizer ON; the displayed source carries the EthereumHistory attribution line. Sourcify relayed the same source to Etherscan, Routescan, and Blockscout.

Heuristic Analysis

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

Detected Type: Registry

Bytecode Overview

Opcodes1,414
Unique Opcodes133
Jump Instructions69
Storage Operations36

External Links

Related contracts