Back to Home

Wallet

Unclassified
0x00693b5a4333...9e7cca81913d
ByzantiumSource VerifiedEdit this contract

Bytecode verified via sibling

This contract shares identical runtime bytecode with a verified contract (0xbe12bf3e...) which has been verified through compiler archaeology.

Deployed April 3, 2018 (8 years ago)Block 5,371,371

Wallet that asks a controller to authorise each call, passing the sender, target, value and payload before executing it.

Byzantium Era

Historical Significance

Most wallets of this period reduced authorisation to an owner comparison. Passing the whole intended call to an external policy contract instead moves the rules off the wallet, so a policy can be tightened or relaxed without redeploying any of the wallets that follow it. That separation is the idea later account abstraction designs formalised.

Key Facts
Deployment Block
5,371,371
Deployment Date
Apr 3, 2018, 05:46 AM
Code Size
926.0 B
Gas at Deploy
325,609

Description

One storage slot holds a readable controller. execute passes the caller, the destination, the value and the full payload to the controller's isAuthorized function and requires a true answer before proceeding. It then makes the call with value and payload, without checking the result.

The payable fallback is empty and accepts ether. Because the authorisation covers the entire call including its data, the controller can enforce rules as specific as a particular function on a particular contract, rather than only checking who the caller is.

Heuristic Analysis

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

Detected Type: Unclassified

Bytecode Overview

Opcodes926
Unique Opcodes104
Jump Instructions34
Storage Operations6

External Links

Related contracts