Warden by drinkerlabs in development

Warden · a smart-account wallet for Solana

A wallet that shows its work.

Most wallets ask you to trust a green checkmark. Warden is being built so you don't have to: it is designed so that a passkey holds root authority, day-to-day signing runs on scoped session keys, and the rules that protect your funds will live in an on-chain program — not just in the interface that asks you to click.

building in the open· not live· not externally audited· nothing to download yet

WARDEN RECEIPT design study
origin
app.example-dex.xyz
tab 4 · account main · mainnet
intent
Swap 12.5 USDC → SOL
decoded from signed bytes
changes now
− 12.5 USDC · + ~0.0612 SOL
authority later
none created
cost · timing
fee 0.000012 SOL · executes after hold

evidence — read independently

origin
associated
decode
full
simulation
stale · 41 s old
policy
passkey + hold required

four axes, no combined verdict — one green never speaks for the others

printed · this page, not a chain

A design study rendered in HTML — not a screenshot of shipping software. States are deliberately mixed: a current decode does not vouch for a stale simulation.

Why build another wallet

A default keypair wallet is one signature from empty.

One hot key signs everything, every approval is all-or-nothing, and the only thing standing between a dApp and your balance is a popup you've learned to click through. Warden's premise is that custody should be structural — enforced where the funds actually live — and that an approval should be something you can read.

Policy belongs on-chain

A UI can promise anything. Warden's vault program is being built so the chain itself refuses transfers the policy forbids — the interface describes the rules, it doesn't enforce them alone.

Evidence stays unbundled

Origin, decode, simulation, and policy are independent facts. Warden is designed to render them separately, never compressing them into a single "safe" score.

Unknown is a first-class state

Missing data will be shown as missing — never silently treated as safe, and never dressed up as dangerous to look thorough.

The flagship surface

Approvals, redesigned as a receipt.

Instead of a generic "sign request," Warden's approval surface is designed to answer the questions you'd actually ask before moving money — in a fixed reading order, derived from the exact bytes to be signed. The order is the design:

01

Who is asking?

The exact origin, tab, account, and network — not a logo the requester chose for itself.

02

What does it decode to?

The operation Warden read from the serialized bytes — with partial and unknown decodes labeled as exactly that.

03

What changes now?

Assets, fees, rent, and balances that move the moment this executes.

04

What authority persists?

Any delegate, session, allowance, or ongoing permission created or changed — the part most wallets bury.

05

What does the evidence say?

Decode, simulation, origin, and on-chain policy report independently. Green on one axis never bleeds into another.

06

What does it cost, and when?

Total fee, quote freshness where relevant, and whether execution is immediate, queued, or timelocked.

07

The decision

A button that names its consequence — "Queue swap · 12 h hold," not "Confirm" — and a stop path that stays visible.

Why no overall score? Because the axes really are independent: a transaction can be fully decoded yet blocked by policy, or simulate cleanly from an origin you've never seen. Collapsing that into one green shield is exactly how people get trained to stop reading.

The architecture

Structure over vigilance.

Warden is a smart account: your funds will live in an on-chain vault governed by a program, not behind a single hot key. Each piece below is a design commitment currently being built and reviewed — not a shipped guarantee.

root authority

A passkey, not a pasted phrase

Root control is designed around WebAuthn passkeys — hardware-backed, phishing-resistant credentials — rather than a seed phrase typed into a text box that any page can imitate.

session keys

Scoped signing for the everyday

Day-to-day activity is designed to run on session keys with per-mint spend caps and expiries — so a compromised session is a bounded loss with an expiry date, not a drained account.

conservation

The chain checks the math

The vault program's core rule is conservation: value cannot leave except along a path the policy allows. The check is designed to run on-chain, enforced by the program itself — where a compromised interface can't skip it.

stop paths

Freeze, recovery, guardians

Being able to stop matters as much as being able to sign: freeze the vault, recover through a timelocked ceremony, and lean on guardians — designed so that losing a device isn't losing the account.

Address poisoning

A partial match is never identity.

Wallets that show the first and last four characters of an address taught attackers to manufacture lookalikes with matching ends — then seed your history with dust so the fake looks familiar. Warden's design treats matching fragments as attention friction at most: they never turn a flow green, and never establish trust.

ADDRESS CHECK design study

saved recipient provenance: added by you · 2026-08-02

7Kpv9xQmDrTfUeWzHnB4cSgY6NahXJ2M8wRtEuCdB3wS

lookalike provenance: unsolicited dust · first seen today

7KpvZc5mRnAy7DqzbUvGxWmYHsKf8PjT8eNwLuQaB3wS

Same first four. Same last four. Five middle characters even coincide — but the 31 marked characters differ: a different account entirely. Warden's design: blocked by default — full-address comparison with the differing characters marked, dust-borne history never becomes trusted, and overriding requires a fresh, fully-verified entry. Illustrative addresses — not real accounts.

Where it stands

Honest status, kept current.

This page describes design intent for software that is mid-build. Here is exactly what exists and what doesn't:

not live not externally audited nothing to download yet

Warden component status — what exists today and what does not
componentstatuswhat that means
Vault program built · not deployed Smart-account execute, Jupiter swaps, scoped session keys, and an on-chain deploy-governance gate — written, not yet deployed on-chain, and not externally audited.
Browser extension design The receipt surface and evidence model are in design; a TypeScript signing client exists. There is no shipped extension.
Mobile research Native authentication and link handoff are open research questions, not promised features.
Security audit not yet Program code has undergone internal, AI-assisted adversarial review. It has not had an independent external security audit — that comes before any release that touches real funds.
Download none There is nothing to install today — and no waitlist theater either.

Warden is built in the open by drinkerlabs. When there is something real to try, it will be announced there — not before.