Peperium Series 2 Token — Near-Exact Bytecode Match

Factory: 0xb4e34890034a13325363b3226dce8eeec292d626
Token example: 0x5921f43985a027ba74ee110b77dce09b96de943e
Deployed: Block 4,210,431 (August 2017)
Siblings: 13 identical token contracts created by the factory
Compiler: solc 0.4.14+commit.c2215d46, NO optimizer

Verification Status: Near-Exact Bytecode Match

All 21 functions, storage layout, events, and control flow have been verified. The compiled output matches the on-chain bytecode in structure, dispatch table, and function sizes.

One unknown remains: A bool public variable at storage slot 8 with:

• Getter selector: 0xea76f7d8
• Setter selector: 0x8675c3e8 (set<Name>(bool))
• Event hash: 0xb185c7412ee472ad78a25d052b83bdff6ea2e5e35eb9b18339209e3b82a017ff

This identifier is not in any known signature database (4byte.directory, OpenChain, samczsun). The setter was never called on-chain. Brute force has exhausted all names up to 7 characters.

Source

See src/PeperiumToken.sol — the mystery variable is marked as xVar / XEvent as placeholders.

Background

Peperium was a RARE Pepe card token platform on Ethereum. Series 1 tokens were compiled with solc 0.4.10 + optimizer (source confirmed via peperium-2017/contract-verification). Series 2 added:

1. Transfer event emission in the transfer() function
2. A mystery bool public variable with setter and event
3. Compiled with solc 0.4.14, optimizer OFF

Links

• Ethereum History
• Series 1 Source