Back to Home

Wallet

Unclassified
0x262752c58b96...febd6efa109c
ByzantiumSource VerifiedEdit this contract
Deployed August 31, 2018 (8 years ago)Block 6,245,848

Gavin Wood's multi-owner, daily-limited wallet from dapp-bin: the multisig design the Parity wallet was built from.

Byzantium EraVerified Source

Historical Significance

This is the source the Parity multisig wallet descends from, and through it most of the multisig wallets deployed on Ethereum in 2016 and 2017. The library-backed variant of this same code was at the centre of the two Parity wallet incidents, which makes the fully self-contained version, deployed here without any external library, a useful counterpoint: the logic is identical, but nothing about it can be deleted from underneath the wallet.

Key Facts
Deployment Block
6,245,848
Deployment Date
Aug 31, 2018, 09:40 AM
Code Size
6.9 KB
Gas at Deploy
2,060,404

Description

Three contracts are layered. multiowned holds the owner set and the confirmation logic: any action wrapped in onlymanyowners records a per-operation bitmap of which owners have signed and only runs once the required count is reached, so a pending operation costs one storage slot rather than a queue entry. daylimit adds a rolling twenty-four hour spending allowance, reset lazily by comparing the stored day number against today. Wallet combines them.

A send under the daily limit executes immediately with one owner's signature. Anything above it becomes a pending transaction identified by the hash of the call, which other owners confirm by hash. Owners can be added, removed and swapped, and the required-signature count changed, each of those itself an onlymanyowners action.

The confirmation bitmap is the part that repays reading. Each owner has an index, and pending operations store the outstanding count alongside a bitmask, which is why revoking a confirmation is cheap and why changing the owner set clears every pending operation.

Source Verified

Solidityeh_crack_source_verified
Compiler: v0.4.23
Heuristic Analysis

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

Detected Type: Unclassified

Bytecode Overview

Opcodes7,062
Unique Opcodes242
Jump Instructions351
Storage Operations162

External Links

Related contracts