LocationLocked Safe

Main Sending menu
Verification Required menu

✨ Inspiration

The #1 reason for crypto hacks is compromised private keys. Since 2016, over $2B has been lost because of this.

That’s why we built LocationLocked Safe—a fully trustless, non-custodial Web2.5 wallet, featuring traditional Web2 location-based security with decentralized Web3 tech.

🔐 What it does

Our hybrid wallet is a multi-sig wallet that requires the user to be at the physical location where they registered the wallet in order to confirm transactions.

Similar to Web2 login services that notify users if there’s an unusual login at a new location, LocationLocked will only enable transactions if the user is at the original IP address during sign up. This ensures hackers miles away cannot drain wallets, even if they have a private key.

In the case users genuinely want to access their wallet from a different IP address, they’ll be asked a security question (set during sign up).

🛠 How we built it

Vite and React web app using TypeScript
Safe API for multi-sig wallet
Material UI and Safe's UI kit for frontend
Firebase database for storing/comparing IP addresses

Challenges we ran into

we built this in the last 8 hours of the hackathon because our initial AI idea didn't work.

Accomplishments that we're proud of

completing our hack in the final 8 hours

What's next for LocationLocked Safe

using ZK proofs to ensure locations of users' IP addresses are kept private.
use UMA optimistic oracle as a fail-safe in case centralized server ever goes down (will ensure more accessibility, but won't sacrifice security)