Locker Dashboard

Save every time you interact or get paid on-chain.

Modular, and non-custodial smart accounts, called Lockers, that automate the allocation of cryptocurrency payments after they've been deposited. Lockers solve the problem of cumbersome, manual distribution of crypto-native salaries and contract payments into channels such as savings, fiat off-ramps, and crypto investments.

app.locker.money

Why Locker

Whether you currently accept payments with your EOA, CEX, or multisig, there are a bunch of cumbersome steps you have to take to get money where you want after the money lands. With Locker, you set up your preferences once and get notified when your tokens automatically do what you want within 30 seconds of deposit.

Here's one example: when a user gets paid in USDC, 5% is swapped for ETH, 15% is saved in an on-chain, yield-bearing savings account, 10% is sent to an on-chain hot wallet, and 70% is off-ramped into their off-chain bank account–all entirely automated.

We hope hackers at ETH Global can use Locker for accepting their winnings and their next web3 contract.

Further justification

Locker is based on a similar concept we explored at ETH Denver - Auto HODL. In the last few weeks, we have been comparing saving mechanisms based on when you pay or get paid. We used historic ETH Global bounty payment data to help clarify things. By looking at the most recent 1,000 transactions from winners at 7 past ETH Globals, we discovered that the average hackathon winner only executes about 2-3 on-chain transactions per month. If Locker only helps you save when you transact, then we will be missing a lot of savings.

This is why for this hackathon we explored the strategy of saving when you get paid instead.

Getting started

Prerequisites:

• NeonDB
• WalletConnect
• Clerk
• ZeroDev
• Moralis

# setup environment
cp .env.example .env.development.local

# install dependencies
yarn install

# Generate stream ID
yarn stream:gen

# Run migrations on DB
yarn drizzle:push

# run
yarn dev

Details

Moralis Stream ID

Moralis Streams are used for getting realtime updates about deposits into Lockers. A single stream is used for processing updates across all chains and addresses. That stream must be created manually and added to your .env as MORALIS_STREAM_ID. To generate the stream id, yarn stream:gen.

Drizzle Studio

Use yarn drizzle:studio then visit local.drizzle.studio for

---

How it's made

• NextJS
• ZeroDev kernels for Lockers
• Moralis for on-chain tx webhooks
• Basic authentication with Clerk .
• Tailwind CSS for utility class styling.
• Shadcn UI for UI components.
• Postgres database on Neon .
• Drizzle ORM for managing and interacting with data.
• Zephyr template

Here's a diagram detailing how all these pieces come together.