[{"data":1,"prerenderedAt":161},["ShallowReactive",2],{"stories-index":3},[4],{"id":5,"title":6,"body":7,"category":148,"date":149,"description":13,"extension":150,"featured":151,"locale":152,"meta":153,"navigation":151,"path":154,"readingTime":155,"seo":156,"slug":157,"stem":158,"summary":159,"__hash__":160},"stories\u002Fstories\u002Fthe-launch-wallet.md","The launch wallet: why Asylia starts with less",{"type":8,"value":9,"toc":138},"minimark",[10,14,17,20,25,32,35,38,42,45,61,68,71,75,78,81,84,103,106,110,113,116,119,123,126,129,132,135],[11,12,13],"p",{},"A launch wallet should not be judged by how much it tries to contain. It should\nbe judged by how clearly it defines what it will not compromise.",[11,15,16],{},"Asylia begins from that position. It is a Bitcoin multisig wallet built for\npeople who do not want their custody model to depend on one seed phrase, one\ndevice, one company, or one moment of perfect memory. The first public surface is\ndeliberately narrow: create a vault, keep private keys on hardware devices,\ncompose a PSBT, review intent, collect quorum, broadcast only when the policy is\nsatisfied, and leave with a portable backup if the user ever wants to move.",[11,18,19],{},"That may sound modest beside the usual language of wallet launches. It is not.\nFor custody software, restraint is a product feature.",[21,22,24],"h2",{"id":23},"the-smallest-surface-that-can-be-taken-seriously","The smallest surface that can be taken seriously",[11,26,27,28],{},"The industry has trained users to expect wallets that announce themselves with\nmore networks, more swaps, more dashboards, and more motion. Asylia is taking\nthe opposite path. The launch wallet is not trying to become a financial\nsuper-app. It is trying to make one custody decision legible: ",[29,30,31],"strong",{},"Bitcoin should\nnot move unless the required signers agree.",[11,33,34],{},"That decision shapes everything around it. The interface keeps the policy\nvisible. The signing flow treats hardware devices as the boundary for private\nkeys. The transaction path stays explicit enough that a user can understand what\nis being prepared before a signature exists. The export model keeps the vault\nportable instead of trapping it inside one interface.",[11,36,37],{},"This is not minimalism as decoration. It is minimalism as operational discipline.",[21,39,41],{"id":40},"from-wallet-prototype-to-final-public-surface","From wallet prototype to final public surface",[11,43,44],{},"Asylia started as a single Vue wallet application at the root of the project. It\nwas direct, focused, and close to the product problem: how to make serious\nself-custody feel understandable without weakening the custody model.",[11,46,47,48,52,53,56,57,60],{},"The work then moved into a broader architecture. The wallet became\n",[49,50,51],"code",{},"apps\u002Fwallet",". Shared interface foundations moved into ",[49,54,55],{},"@asylia\u002Fui",". Bitcoin\nlogic was separated into reviewable packages for descriptors, PSBT construction,\nchain data, and hardware-wallet integration. The public narrative moved into\n",[49,58,59],{},"apps\u002Fmarketing",". Capacitor shells were added for the future mobile surface.",[11,62,63,64,67],{},"That history matters because it shows the product did not become bigger for its\nown sake. It became more organized. The current ",[49,65,66],{},"asylia.io"," repository is the\nfinal public home for that structure: wallet, marketing site, design system,\nstatus surface, security documentation, and the auditable Bitcoin packages that\nsit beneath the interface.",[11,69,70],{},"A launch wallet should be able to explain where it came from. Asylia can: it\nstarted as a working wallet, then separated the parts that deserve separate\naccountability.",[21,72,74],{"id":73},"the-promise-is-not-convenience-the-promise-is-control","The promise is not convenience. The promise is control.",[11,76,77],{},"Convenience alone is a weak foundation for custody. It can make the first five\nminutes easier while making the next five years more fragile. Asylia is built\naround a different promise: the user should understand the rules before the\nsoftware asks them to trust the result.",[11,79,80],{},"That means no vague security theatre. No decorative confidence. No hidden\ncustody claim that cannot be tied back to code, policy, a device boundary, or a\ndocumented limitation.",[11,82,83],{},"The launch wallet focuses on the moments that matter:",[85,86,87,91,94,97,100],"ul",{},[88,89,90],"li",{},"Can the user see the vault policy before relying on it?",[88,92,93],{},"Can the user keep signing authority on hardware devices?",[88,95,96],{},"Can the user review transaction intent before signatures are collected?",[88,98,99],{},"Can the user export the policy and recover outside Asylia if needed?",[88,101,102],{},"Can an outside reviewer understand the Bitcoin surface without reading a\nmarketing slogan as a security proof?",[11,104,105],{},"Those questions are the product.",[21,107,109],{"id":108},"serious-custody-should-feel-calm","Serious custody should feel calm",[11,111,112],{},"Asylia is designed to feel quiet because the underlying rules are strict. Calm\ndoes not mean hiding risk. Calm means reducing surprise. It means fewer surfaces\ncompeting for attention when the user is making an irreversible decision. It\nmeans copy that names the boundary instead of selling around it. It means a\nwallet that can be attractive without becoming theatrical.",[11,114,115],{},"The launch wallet exists for people who want Bitcoin custody to feel mature:\nfounders protecting operating reserves, families planning redundancy, long-term\nholders replacing a single seed with a quorum, and technical users who care\nabout portable policy more than platform lock-in.",[11,117,118],{},"Those users do not need a louder wallet. They need one that respects the weight\nof the action.",[21,120,122],{"id":121},"launch-is-a-beginning-not-a-performance","Launch is a beginning, not a performance",[11,124,125],{},"Asylia is not launching as a claim that the work is finished. It is launching as\na public standard for how the work will continue: narrow policy, hardware-first\nsigning, explicit transaction intent, portable backups, public security posture,\nand a codebase organized so important boundaries can be reviewed.",[11,127,128],{},"More features can come later. The launch standard has to be right from day one.",[11,130,131],{},"Because the first version of a serious wallet should not ask for applause. It\nshould ask the harder question:",[11,133,134],{},"Can this product be trusted with less noise, more evidence, and a custody model\nthat remains understandable after the launch page is closed?",[11,136,137],{},"That is the bar Asylia is choosing.",{"title":139,"searchDepth":140,"depth":140,"links":141},"",3,[142,144,145,146,147],{"id":23,"depth":143,"text":24},2,{"id":40,"depth":143,"text":41},{"id":73,"depth":143,"text":74},{"id":108,"depth":143,"text":109},{"id":121,"depth":143,"text":122},"Launch story","2026-05-04","md",true,"en",{},"\u002Fstories\u002Fthe-launch-wallet",5,{"title":6,"description":13},"the-launch-wallet","stories\u002Fthe-launch-wallet","Asylia is not launching by trying to look finished. It is launching by making the custody surface narrow, reviewable, and serious enough for real Bitcoin self-custody.","3jHU6NW9TrOtNMTF-WP4GNJcFhLjI8nm0YP-n23BZPU",1777975502127]