Locker is a consumer DeFi framework for automatically saving a small amount of tokens as users perform their normal on-chain activity. In other words, Locker is an on-chain equivalent of Acorns and other round-up savings tools.

ETH Denver 2024 presentation

• Consumer dApp: dApp UI that the end user wants to interact with. This might be uniswap.com, the Metamask interface for transferring ERC20, or any other UI that talks to the blockchain.
• Savings Contract: The on-chain contract that all the user's transactions passes through.
• Target Contract: The on-chain component of the Consumer dApp.
• Unlock Date: The user defined date after which savings can be withdrawn.

1. Alice sets up a Savings Contract and defines how much she wants to put in to savings for every transaction and what the Lockup Period will be.
2. Alice wants to do a swap on the Target Contract, 1inch, for 100 USDC to ETH
3. Locker intercepts Alice's transaction and asks for a small amount of additional token before Alice signs the transaction.
4. The transaction is sent to the Savings Contract which deposits the extra amount into savings.
5. The Savings Contract forwards the swap request to the Target Contract (1inch) which processes the transaction normally.
6. After the Unlock Date, Alice can withdraw all her savings.

This code currently implements v1 in the diagram below. In the future, we plan on streamlining by integrating with Metamask snaps and 4337 account abstraction.

$ cd backend
$ forge build
$ HODL_DEPLOY_KEY='XXX'

# Deploy Savings Contract
$ forge create src/Factory.sol:Factory \
    --private-key $HODL_DEPLOY_KEY \
    --rpc-url https://example.com

# Deploy sample Target Contract
$ forge create src/Counter.sol:Counter \
    --private-key $HODL_DEPLOY_KEY \
    --rpc-url https://example.com

$ cd interface
$ yarn
$ yarn dev