A marketplace store record: it holds an owner, a metadata blob and the address of the comment board its listings are discussed on.
Historical Significance
A marketplace split across three contracts, one per store, one per comment board, and a type flag so that an index can be walked without a registry saying what each address is. Composing an application out of small contracts that point at each other, rather than one contract holding everything, is the structure that later became normal, adopted here because a single contract holding a whole marketplace would not have fit in the gas limits of the day.
Context
Deployed in December 2015, when a dapp meant a set of contracts and a web page that knew their addresses. There was no indexer, no subgraph and no standard for discovering related contracts, so an isStore flag answered directly by the contract was how a client identified what it was looking at.
Key Facts
Description
The store half of an onchain marketplace. It keeps an owner, a bytes field of metadata that the owner can rewrite through setMeta, and the address of a separate forum contract, and answers isStore() so that a reader walking a list of addresses can tell what kind of record it has found.
addComment(address, bytes32, bytes) passes a comment through to the forum rather than storing it here, which keeps the store's own state small. The forum it points at is 0x3c05353b135e90fefb262218d35dc2827f1049fe, a comment board that keeps nothing in storage and emits every comment as a log entry instead.
The Solidity source has not been recovered; the interface above is read from the deployed bytecode and the stored values from the chain.
Heuristic Analysis
The following characteristics were detected through bytecode analysis and may not be accurate.
Frontier Era
The initial release of Ethereum. A bare-bones implementation for technical users.
Bytecode Overview
External Links
Related contracts
Contract 0x928fd6...a394a2
Same deployerA first come first served name registry from November 2015: claim a bytes32 alias for your address, and it can never be released.
0x928fd6...a394a2November 23, 2015Contract 0xdfe162...689c7a
Same deployerA contract with no storage at all that exists only to write three indexed addresses into the log.
0xdfe162...689c7aNovember 23, 2015Contract 0x33bf61...f98a64
Same deployerA first come first served name registry from November 2015: claim a bytes32 alias for your address, and it can never be released.
0x33bf61...f98a64November 23, 2015Contract 0x5cdb3c...662fd1
Same deployerA contract with no storage at all that exists only to write three indexed addresses into the log.
0x5cdb3c...662fd1November 23, 2015Contract 0x2e9450...a2b844
Same deployerA first come first served name registry from November 2015: claim a bytes32 alias for your address, and it can never be released.
0x2e9450...a2b844November 23, 2015Contract 0x565c13...07833d
Same deployerA first come first served name registry from November 2015: claim a bytes32 alias for your address, and it can never be released.
0x565c13...07833dNovember 23, 2015