Back to HomeDeployer 0xbf82a4...bb0469 Deployment Block 3,888,798 Deployment Date Jun 17, 2017, 06:41 PM Code Size 131.0 B
Exact Bytecode MatchEdit this contract
Deployed June 17, 2017 (9 years ago)Block 3,888,798
Delegatecall forwarder with a literal failure-jump offset, second implementation.
Verified Source
Historical Significance
Shows the same proxy template being redeployed against a fresh implementation address, with the jump-offset quirk carried along unchanged.
Key Facts
Deployment Transaction: 0x0d04b4c5248a3047...304c5bfe36911288
Description
The same forwarder pattern as the other 0.4.11 proxy groups, pointing at a different hardcoded implementation, and carrying the same literal jump target on the delegatecall-failure path. The runtime code matches the deployed bytecode byte for byte; only the trailing swarm metadata hash differs, because the EthereumHistory attribution comment changes the source text. Sourcify records this as a partial match and Etherscan shows it as verified.
Source Verified
Bytecode Overview
Opcodes131
Unique Opcodes79
Jump Instructions9
Storage Operations2
Verified Source Available
Source verified through compiler archaeology and exact bytecode matching.
View Verification ProofShow source code (Solidity)
// Submitted by EthereumHistory (ethereumhistory.com)
pragma solidity ^0.4.11;
contract Proxy {
function implementation() internal constant returns (address) {
return 0xa229469fd1eb571d53dea6c7d34f25712f881902;
}
function () payable {
address target = implementation();
assembly {
let ptr := msize()
mstore(0x40, add(ptr, calldatasize))
calldatacopy(ptr, 0, calldatasize)
jumpi(0x54, iszero(delegatecall(div(mul(gas, 0x3f), 0x40), target, ptr, calldatasize, 0, 0x20)))
return(0, 0x20)
fail:
invalid
}
}
}