Back to Home

Invoice

0x0090e694a5eb...f51965c56f90
HomesteadSource VerifiedEdit this contract
Deployed May 13, 2016 (10 years ago)Block 1,510,739

One-off payment address that logs every incoming transaction and forwards the balance to a fixed payout address.

Homestead EraVerified Source

Historical Significance

This is accounting infrastructure rather than a protocol. The events are the product, and the contract exists to make a payment addressable and attributable without a database entry per customer. Its weak points are the same ones every payment forwarder of the period had: an unchecked send, and an event that records intent rather than outcome.

Key Facts
Deployment Block
1,510,739
Deployment Date
May 13, 2016, 04:14 PM
Code Size
768.0 B

Description

The contract is an invoice in the literal sense: a merchant hands out a fresh address per bill, and anything sent to it is recorded and swept onward. The fallback emits IncomingTx with the block number indexed, plus the sender, the value and the timestamp, then forwards the contract's whole balance to the payout address stored at construction.

Indexing the block number rather than the sender is a deliberate choice. A back end reconciling payments scans by block range, not by payer, and the payer of an invoice is rarely known in advance.

The forward uses send and ignores the result, so a payout address that rejects the transfer leaves the funds sitting in the invoice while the event still claims the payment arrived. refund is owner-only and emits RefundInvoice, but moves nothing: the refund itself happens off chain, and the event is the receipt.

Source Verified

Solidityeh_crack_source_verified
Compiler: v0.3.6+

Bytecode Overview

Opcodes768
Unique Opcodes116
Jump Instructions22
Storage Operations7

External Links