Practical overview
When it fits
Use the repository when studying or developing around an Ethereum smart contract wallet whose transfers and key administration can require cosigner authorization, and whose recovery flow replaces existing device keys.
Who it is for
- Developers examining or working with an Ethereum smart contract wallet implementation.
- Readers evaluating wallet designs with additional cosigner authorization and a recovery process.
Documented uses
- Review how wallet assets are held at a contract address and transferred through contract calls.
- Understand device-key permissions and add cosigner signatures to wallet operations.
- Examine a recovery flow that replaces all device keys with a backup key.
- Set up the repository’s documented build and test sequence.
Requirements & limits
The repository is public and specifies GPL-3.0 licensing.
- Assets are associated with the wallet’s contract address; outgoing transfers require wallet contract calls.
- Device keys can manage transfers and wallet keys, but cannot perform recovery.
- Cosigners can be replaced or removed, and the README describes up to two additional signatures through invoke() methods.
- Recovery removes all existing device keys and makes the backup key the sole device key.
- The development instructions specify Node 9 and a bytecode-copy step tied to the compilation path.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Prepare the repository’s test workflow
Set up the documented development and test sequence for the Dapper smart contracts.
Before you start
- Node 9
Steps
Install dependencies with the command below.
npm installBuild with the command below.
npm run buildCopy the bytecode from
FullWallet.jsonintoWalletFactory.sol.Run the command below.
npm test
Expected outcome
The documented test command is run after the build and required bytecode-copy step.
Guide limitations
- The README says compiled bytecode depends on the path used to compile it.
- These are repository instructions, not a report of an independently executed test.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 18 October 2026
- Original website title
- dapperlabs/dapper-contracts · Official homepage title · retained in its source language

