Misha (Mikhail) Krasovitskiy, Senior/Lead Product Designer. AI-first wallet for the Waves ecosystem, Units.Network (Mar – Jun 2026).
Image: Video: Aura in use: the user types Swap 200 USDT to WAVES and lease them, Aura prepares two transactions, the user reviews and confirms with Face ID, History shows the swap and the new lease
Aura AI Wallet
AI-first wallet for the Waves ecosystem
Users type what they want, Aura prepares the transactions and explains each one before they sign
- Role: Lead Product Designer
- Company: Units.Network
- Timeline: Mar – Jun 2026
- Platform: iOS, Android
- Team: PM, 2 engineers, me
Problem
Aura v1 handled balance, transfers and dApps, but every task expected the user to know which network operation they needed and where it lived in the app. Leasing took 5 steps on 5 screens, plus a separate system screen for signing
- 62% of users who started leasing did not finish
- 76% of active users had not leased once in 90 days
6–9
support tickets per 1,000 MAU a month about unclear or failed transactions
Leasing funnel in v1: opened 100%, entered amount 72%, reached confirmation 51%, opened signing 44%, completed 38%. Most tickets were about an unclear status after confirming, signing errors and rejected dApp transactions, and leasing terms and unlock timing
The balance has no context
One number, no change for the day, no reason
Every task starts with a form
Send, Swap and Receive with equal weight, fields filled one by one
Leasing is hard to find
The main way to earn on WAVES sits in the third tab
Image: Annotated audit of Aura v1 with six issues
Audit of the first version
Users
4,000 MAU and 1,400 WAU in three groups. The groups overlap
68% OF MAU
Holders
Check what changed, receive, send now and then
24% OF MAU
Leasers
Keep WAVES earning without watching nodes
18% OF MAU
dApp users
Swap and sign on Puzzle Swap, WX and Units without fear
Solution
Three home screens were tested with 14 existing users in 6 moderated interviews and 8 prototype tests: balance and assets first, quick actions first, and AI-first with the Aura request bar on home. The tests checked whether people understood the request bar, found the main actions, trusted Aura’s suggestions and knew when they were signing a real transaction. The AI-first layout kept the balance on top and was the only one that explained a transaction before signing
Image: Three home screen options compared on four criteria, option C chosen
Three options for the home screen, option C chosen
AI layer
A request goes through six steps: input, parse, plan, check, sign, result. The model only turns text into a structured request and writes the explanations. Transactions are built by the same wallet code as the manual forms and are test-run against the current network state before the user sees them. When the request is unclear Aura asks one question, when it cannot build a plan it opens a prefilled form, and when the check finds a risk it stops and explains
Image: Flow from a request to a signed transaction with three fallback branches
From a request to a signed transaction
Image: Review transactions screen with two prepared transactions
One request, two prepared transactions, one confirmation
Image: dApp signing screen with a plain-language explanation and a risk check
Before any dApp signature Aura explains in plain words what the transaction does, what leaves the wallet and what permissions the app gets
Leasing
Aura notices idle WAVES and offers to lease them, recommends a node by return after fees and uptime, and can reinvest rewards weekly. It always asks before switching nodes
Image: Leasing screen with a recommended node and weekly reinvesting
Image: Home screen with the balance, an Aura suggestion and the request bar
Design system
The colors and the ring motif come from the original Aura screens. Bright blue marks only what Aura says or suggests, so assistant content is never confused with wallet data. Risk levels differ in icon, word and color, never color alone. The new logo is the letter A drawn as one stroke, with a rhombus as the crossbar in reference to the Waves logo
Image: Interface system: palette, type, Aura states and risk levels
Image: Aura logo: icon, construction, lockups and Waves co-brand
First results
The AI layer shipped as v2 of the live wallet. Below is v1 over the 8 weeks before the release against v2 over the first 8 weeks after it
Swap time
v1
95 s
v2
55 s
Leased share of WAVES
v1
- 28% v2
- 35% Risky dApp signatures rejected
v1
- 5% v2
- 15% Support tickets per 1,000 MAU
v1
- 8 v2
5
Process
The whole design process in one canvas: audit, problem framing, flow, concepts, final screens and system
Image: The whole Aura design process on one canvas
Image: dApp signing, Leasing and History screens