Blog

Notes on building a more professional wallet

Notes on cross-chain execution, wallet security, and what a more professional swap experience looks like.

Diagram showing one wallet approval opening a bounded payment channel for many agent payments, with limits and revocation controls.

One Approval Can Hide a Thousand Payments: What Agent Wallets Must Explain

Payment channels can remove thousands of repetitive prompts. They also make the first approval more important. A clear wallet must show the actor, asset, limit, duration, settlement and revocation path before signing.

Lower Cost # Clearer UX

Cheaper Onchain Costs Won’t Fix Confusing Wallet UX

Solana is reducing account-storage costs in phases. Here is what cheaper onboarding changes — and what wallets still need to explain before users sign.

Biti.pro visual explaining that a transaction marked “Done” can represent different user outcomes such as completed, partial, or refunded.

DONE is not a user outcome

A transaction can be technically complete while still leaving the user unsure about what actually happened. Good wallet UX should explain the outcome, not just the system state.

Diagram comparing simulated transaction effects with enforced spending permissions for an onchain AI agent.

Transaction Simulation vs Spending Permissions: What Actually Limits an Onchain AI Agent?

Simulation forecasts an action under current conditions. Permissions define the authority an agent can exercise. Treating them as interchangeable leaves a dangerous gap.

Four evidence layers before signing: decoded, simulated, asserted and unknown

What Transaction Simulation Can—and Cannot—Tell You Before You Sign

A simulation is evidence produced against a specific state. It can forecast likely effects, but it cannot prove intent, finality or downstream completion.

A Biti.pro permission receipt showing who can act, the authority limit, expiry and revoke controls before an agent can act.

What Should a Wallet Show Before a Smart Account or AI Agent Can Act?

A transaction is a moment. A permission is a time window. As smart accounts, delegated execution and agent-assisted workflows become more capable, wallets need to explain who can act, what they can do, for how long and how the user can stop them.

Transaction lifecycle showing submitted, confirmed, finalized and arrived states after sending crypto.

How to Read a Block Explorer After Sending Crypto

A wallet saying “Sent” is only the beginning. Learn how to verify what actually happened onchain and when the recipient can treat the transfer as complete.

A technical diagram separating visible wallet balance from network, native gas and spendable balance requirements.

Your Wallet Balance Is Not Your Spendable Balance

A wallet balance shows ownership. It does not prove that the full amount can be sent on the selected network under current fee conditions.

A cross-chain wallet pre-sign checklist showing route, estimated cost, minimum received and permissions.

What Should a Cross-Chain Wallet Show Before You Sign?

Learn the route, estimated cost, minimum received, permissions and status details a cross-chain wallet should explain before you sign.

Diagram explaining that a private key stays on the device while a signed transaction is prepared for broadcast

What Self-Custody Actually Means: The Security Boundary of a Crypto Wallet

Self-custody gives you control of the keys that authorize activity from your wallet. It does not make every transaction safe or understandable by default.