New λPrize: LP-0021, LEZ Wallet and Provider SDK ($20,000)
We’re opening LP-0021: LEZ Wallet and Provider SDK, a new λPrize and the first of the Logos wallet prizes. This one is big, and it’s the piece that lets people actually start using LEZ.
The problem
A zone can’t have users until it has a wallet. The Logos Execution Zone (LEZ) has a wallet today, but it’s deliberately basic: enough to get started, not something a dApp can build on. There’s no standard way for a dApp to ask a user for an account or a signature. If nothing changes, every dApp team will build its own key management, asset display, and approval screens. That’s wasted effort, users get an inconsistent experience, and every one of those one-off signing flows is a security risk.
What we’re looking for
LP-0021 funds a complete wallet for a single LEZ zone, plus a Wallet Provider SDK that any Logos app can plug into:
- Own, send, and receive native and token-program assets, from both public and private accounts
- Multiple accounts, public and private, with easy switching between them
- A documented Wallet Provider SDK so third-party dApps can request account access, read balances and state, and propose transactions
- A connect → account selection → approval flow where the user sees the requesting dApp, the target account, and exactly what’s being signed. For contract calls, that means a human-readable summary of what moves where, not raw calldata
- Program source verification shown in the approval prompt, using a program registry along the lines of LP-0023
- Two reference mini-apps built on the SDK: a faucet app for funding accounts on testnet, and a testimonial app that writes testimonials on-chain to the official Logos zone
- A Logos Basecamp app GUI plus a CLI, running end-to-end against Logos testnet 0.3 (
https://testnet.lez.logos.co)
Privacy is part of the requirements. Beyond the user’s own sequencer and LEZ node, the wallet can’t depend on any third-party service. Analytics must be strictly opt-in, and if anything is backed up remotely, it goes to Logos Storage and is encrypted client-side first.
Adoption criteria
Like LP-0023, this prize is judged on real use as well as the build:
- 10 independent third-party developers each ship a Basecamp app that uses the Wallet Provider SDK
- 150 on-chain testimonials from at least 150 distinct accounts, submitted through the testimonial mini-app
- Testimonials spread over at least 2 months, with at least 30 new ones each month (no single burst)
- 30 testimonials on Discord and 30 on Twitter/X from people describing what they actually used the wallet for
The two-month window means you can’t qualify by finishing the build first and chasing adoption afterwards. Ship early, get the wallet into people’s hands, and keep building as usage grows.
Talking with potential users is part of the work, and it doesn’t stop after launch day. Builders, keep coming back to this thread throughout the build: share previews, ask what’s missing, and use the feedback to shape the wallet. The wallet that wins will be the one people are already using by the time it’s finished.
Details
- Total prize: $20,000
- Effort: X-Large
- Evaluation: first-come-first-served against all success criteria; the first submission to meet everything wins
- Full spec:
prizes/LP-0021.md
This wallet and SDK will be the entry point for most people’s first experience of LEZ, and the base that every other LEZ dApp builds on.
Users: what would you want from a LEZ wallet? Which dApps would you connect it to first? Let us know below.
Builders: if you’re working toward LP-0021, or planning a Basecamp app on top of the SDK, post your progress in this thread and keep checking in with users as you go.
Discord discussion