The launch wallet: why Asylia starts with less

A launch wallet should not be judged by how much it tries to contain. It should be judged by how clearly it defines what it will not compromise.

Asylia begins from that position. It is a Bitcoin multisig wallet built for people who do not want their custody model to depend on one seed phrase, one device, one company, or one moment of perfect memory. The first public surface is deliberately narrow: create a vault, keep private keys on hardware devices, compose a PSBT, review intent, collect quorum, broadcast only when the policy is satisfied, and leave with a portable backup if the user ever wants to move.

That may sound modest beside the usual language of wallet launches. It is not. For custody software, restraint is a product feature.

The smallest surface that can be taken seriously

The industry has trained users to expect wallets that announce themselves with more networks, more swaps, more dashboards, and more motion. Asylia is taking the opposite path. The launch wallet is not trying to become a financial super-app. It is trying to make one custody decision legible: Bitcoin should not move unless the required signers agree.

That decision shapes everything around it. The interface keeps the policy visible. The signing flow treats hardware devices as the boundary for private keys. The transaction path stays explicit enough that a user can understand what is being prepared before a signature exists. The export model keeps the vault portable instead of trapping it inside one interface.

This is not minimalism as decoration. It is minimalism as operational discipline.

From wallet prototype to final public surface

Asylia started as a single Vue wallet application at the root of the project. It was direct, focused, and close to the product problem: how to make serious self-custody feel understandable without weakening the custody model.

The work then moved into a broader architecture. The wallet became apps/wallet. Shared interface foundations moved into @asylia/ui. Bitcoin logic was separated into reviewable packages for descriptors, PSBT construction, chain data, and hardware-wallet integration. The public narrative moved into apps/marketing. Capacitor shells were added for the future mobile surface.

That history matters because it shows the product did not become bigger for its own sake. It became more organized. The current asylia.io repository is the final public home for that structure: wallet, marketing site, design system, status surface, security documentation, and the auditable Bitcoin packages that sit beneath the interface.

A launch wallet should be able to explain where it came from. Asylia can: it started as a working wallet, then separated the parts that deserve separate accountability.

The promise is not convenience. The promise is control.

Convenience alone is a weak foundation for custody. It can make the first five minutes easier while making the next five years more fragile. Asylia is built around a different promise: the user should understand the rules before the software asks them to trust the result.

That means no vague security theatre. No decorative confidence. No hidden custody claim that cannot be tied back to code, policy, a device boundary, or a documented limitation.

The launch wallet focuses on the moments that matter:

• Can the user see the vault policy before relying on it?
• Can the user keep signing authority on hardware devices?
• Can the user review transaction intent before signatures are collected?
• Can the user export the policy and recover outside Asylia if needed?
• Can an outside reviewer understand the Bitcoin surface without reading a marketing slogan as a security proof?

Those questions are the product.

Serious custody should feel calm

Asylia is designed to feel quiet because the underlying rules are strict. Calm does not mean hiding risk. Calm means reducing surprise. It means fewer surfaces competing for attention when the user is making an irreversible decision. It means copy that names the boundary instead of selling around it. It means a wallet that can be attractive without becoming theatrical.

The launch wallet exists for people who want Bitcoin custody to feel mature: founders protecting operating reserves, families planning redundancy, long-term holders replacing a single seed with a quorum, and technical users who care about portable policy more than platform lock-in.

Those users do not need a louder wallet. They need one that respects the weight of the action.

Launch is a beginning, not a performance

Asylia is not launching as a claim that the work is finished. It is launching as a public standard for how the work will continue: narrow policy, hardware-first signing, explicit transaction intent, portable backups, public security posture, and a codebase organized so important boundaries can be reviewed.

More features can come later. The launch standard has to be right from day one.

Because the first version of a serious wallet should not ask for applause. It should ask the harder question:

Can this product be trusted with less noise, more evidence, and a custody model that remains understandable after the launch page is closed?

That is the bar Asylia is choosing.