# bitcoinsv.design > The design guide for BSV wallets, payments and apps. How wallet connection, payments, identity and keys work, and what each one means for the screen you are drawing. Published by BSV Association under the Open BSV License Version 6. Last updated 2026-10-25. Canonical home: https://www.bitcoinsv.design/ This guide is about designing BSV products: wallets, payments, identity, keys and the screens around them. It is written for the person drawing the interface rather than the person writing the node. Throughout, **bitcoin** means BSV, the original protocol as described in the 2008 white paper. Where a difference from another chain matters to a design decision, the page says so explicitly. ## Getting started Why BSV is different, the design principles, the visual language, and the software and hardware you design for. - [Getting started](https://www.bitcoinsv.design/guide/getting-started/introduction/): What BSV is, the five things to know before drawing anything, and where to start if you design products, research them or found them. - [The hard parts](https://www.bitcoinsv.design/guide/getting-started/the-hard-parts/): The problems that stay hard when you design a BSV product, each framed as the questions users ask and the decisions you have to make, before any answer. - [Why BSV is different](https://www.bitcoinsv.design/guide/getting-started/why-bitcoin-is-unique/): The properties BSV shares with all bitcoin, the ones that come from its own choices, and the honest limits of both. - [Why design for BSV](https://www.bitcoinsv.design/guide/getting-started/why-design-for-bitcoin/): What the work is actually like, which problems are genuinely open, and who it suits. - [Design principles](https://www.bitcoinsv.design/guide/getting-started/principles/): Seven commitments this guide holds BSV products to, what each one costs, and the rules that follow from them. - [Visual language](https://www.bitcoinsv.design/guide/getting-started/visual-language/): The bitcoin symbol, the satoshi, and the imagery BSV inherits: which pieces to use in a product, which to avoid, and why. - [Technology primer](https://www.bitcoinsv.design/guide/getting-started/technology-primer/): Enough of how BSV works to make good design decisions, in the order the pieces actually depend on each other. - [Software categories](https://www.bitcoinsv.design/guide/getting-started/software/): The kinds of BSV software that exist, what each is for, and which of them you are most likely to be designing. - [Hardware categories](https://www.bitcoinsv.design/guide/getting-started/hardware/): The physical objects in a BSV product's picture, from a sheet of paper to a till, and which of them a designer actually has to account for. - [Open design](https://www.bitcoinsv.design/guide/getting-started/open-design/): Designing in public: what changes about the process, what it costs, and how licensing actually works here. ## Designing BSV products The design process: knowing your users, the usage life cycle, personal finance, accessibility and common flows. - [Personal finance](https://www.bitcoinsv.design/guide/designing-products/personal-finance/): The money jobs people already have, which ones BSV suits and which it does not, and the wallet that fits each. - [Spending, saving and delegating](https://www.bitcoinsv.design/guide/designing-products/spending-saving-delegating/): Three ways people relate to the money in a BSV product, why each screen should serve one of them, and the bridges to build between them. - [Designing BSV products](https://www.bitcoinsv.design/guide/designing-products/introduction/): The design method, and the four places where designing for BSV changes the method rather than just the examples. - [Getting to know your users](https://www.bitcoinsv.design/guide/designing-products/getting-to-know-your-users/): What moves people towards a BSV product, what stops them, and which barriers to design against first. - [Common user flows](https://www.bitcoinsv.design/guide/designing-products/common-user-flows/): The flows nearly every BSV product needs, what each must get right, and the ones you do not need to build. - [Usage life cycle](https://www.bitcoinsv.design/guide/designing-products/usage-life-cycle/): From never having heard of it to using it without thinking, what each stage needs, and where people actually drop out. - [Interoperability](https://www.bitcoinsv.design/guide/designing-products/interoperability/): Letting people take their money, their identity and their data somewhere else, and why on BSV the connection standard does most of the work. - [Accessibility](https://www.bitcoinsv.design/guide/designing-products/accessibility/): The accessibility work every product needs, and the handful of places where an irreversible payment raises the stakes. ## Patterns What to design, by task: connecting a wallet, showing amounts, paying by handle, charging per use, letting an agent spend, tokens, data and conditions. - [Patterns](https://www.bitcoinsv.design/guide/patterns/): What to design, by task: connecting and signing in, amounts and payments, errors, agents, tokens, stored data and spending conditions. - [Connecting a wallet](https://www.bitcoinsv.design/guide/patterns/connecting-a-wallet/): How an app connects to a person's BSV wallet: what it can ask for, how little to ask for, and how the wallet knows who is asking. - [Permissions and allowances](https://www.bitcoinsv.design/guide/patterns/permissions-and-allowances/): What an app can do after it connects: the permission prompt, spending allowances, the wallet's permissions dashboard, revoking, and the capabilities that stay off by default. - [Signing in](https://www.bitcoinsv.design/guide/patterns/signing-in/): Signing somebody in with their wallet when there are no accounts or passwords: the first visit, returning visits, signing out, and asking for one fact from a Pass. - [Paying by handle](https://www.bitcoinsv.design/guide/patterns/paying-by-handle/): Paying somebody by a readable name: how a handle becomes a payment, what to show before the confirm button, and the risk a readable name brings. - [Amounts and units](https://www.bitcoinsv.design/guide/patterns/amounts-and-units/): How to show BSV amounts: satoshis as the unit, which figure leads, what to do about the missing symbol, and the rules that stop a number being misread. - [Charging per use](https://www.bitcoinsv.design/guide/patterns/charging-per-use/): Charging a few satoshis many times: the patterns that work, the prompt problem, and how to show hundreds of payments without making somebody anxious. - [Wrong-network payments](https://www.bitcoinsv.design/guide/patterns/wrong-network-payments/): Why a BSV address and a BTC legacy address are indistinguishable, what that costs a user, and the four defences in the order they are worth building. - [Errors and failed payments](https://www.bitcoinsv.design/guide/patterns/errors-and-failed-payments/): The model for every failure in a BSV product: plain words first, whether money moved, what to do next, and the code underneath for support. - [Letting an agent spend](https://www.bitcoinsv.design/guide/patterns/letting-an-agent-spend/): Software spending on somebody's behalf: what to grant it, how to bound it, and the review screen a person needs when they were not the one who decided. - [Holding tokens](https://www.bitcoinsv.design/guide/patterns/holding-tokens/): What a token is on BSV, how one reaches a wallet, and the four things a product has to show before somebody can trust what they are holding. - [Spending conditions](https://www.bitcoinsv.design/guide/patterns/spending-conditions/): Rules written into money about when and how it can be spent: what BSV supports, how to explain a lock nobody can undo, and why the setup is part of the backup. - [Storing data on chain](https://www.bitcoinsv.design/guide/patterns/storing-data-on-chain/): Putting data on the chain: what it is good for, what permanence means for a consent screen, and the four things to settle before you write anything. - [Web apps and native apps](https://www.bitcoinsv.design/guide/patterns/web-and-native-apps/): How a website, a phone app and a desktop app each reach a person's BSV wallet, and what changes for the connect prompt, the no-wallet case and who the wallet can say is asking. ## Daily spending wallet A mobile wallet for everyday use: first use, connecting to apps, paying, receiving, contacts, activity, backup, security and settings. - [Daily spending wallet](https://www.bitcoinsv.design/guide/daily-spending-wallet/): A reference design for a BSV wallet people use every day: what it is for, what it is deliberately not for, and the nine flows it is made of. - [First use](https://www.bitcoinsv.design/guide/daily-spending-wallet/first-use/): From finding the app to holding money, without a wall of warnings: what to ask, what to defer, and when to ask for a backup. - [Requesting](https://www.bitcoinsv.design/guide/daily-spending-wallet/requesting/): Asking to be paid on BSV: the handle, the QR code, the amount, and why there is no invoice to expire. - [Receiving](https://www.bitcoinsv.design/guide/daily-spending-wallet/requesting/receiving/): What happens when money arrives, how the wallet knows, and the three cases that are not the happy path. - [Sending](https://www.bitcoinsv.design/guide/daily-spending-wallet/sending/): Paying a person, a shop or an app on BSV, and the review screen that is the only chance to catch a mistake. - [Send fees](https://www.bitcoinsv.design/guide/daily-spending-wallet/sending/send-fees/): Why a BSV wallet has no fee picker, what to show instead, and the one place a fee still deserves a line. - [Activity](https://www.bitcoinsv.design/guide/daily-spending-wallet/activity/): What happened, including the hundreds of tiny app payments a BSV wallet has to show, grouped so the list stays readable. - [Contacts](https://www.bitcoinsv.design/guide/daily-spending-wallet/contacts/): People and apps the user pays more than once. The feature that stops them typing handles, and the one that warns them when a key changes. - [Security](https://www.bitcoinsv.design/guide/daily-spending-wallet/security/): Locking the app, approving payments, and managing what connected apps are allowed to do, which is where the real risk in a connected wallet lives. - [Privacy](https://www.bitcoinsv.design/guide/daily-spending-wallet/privacy/): What a BSV wallet gets for free, what the user still controls, and the one leak that is a coin selection decision. - [Settings](https://www.bitcoinsv.design/guide/daily-spending-wallet/settings/): What belongs in settings, what belongs in the main interface, and the four sections this wallet needs. - [Automatic cloud backup](https://www.bitcoinsv.design/guide/daily-spending-wallet/backup-and-recovery/cloud-backup/): The wallet backup: the records half of a BSV backup, encrypted on the device, kept continuously, and the reason a restored wallet can find its money. - [Backup and recovery](https://www.bitcoinsv.design/guide/daily-spending-wallet/backup-and-recovery/landing-page/): Why a BSV wallet backup has two parts, what each one restores, and how to design a flow that tells users the truth about it. - [Manual backup](https://www.bitcoinsv.design/guide/daily-spending-wallet/backup-and-recovery/manual-backup/): The screen-by-screen flow for getting recovery words onto paper, and the parts of it that decide whether a user keeps them. - [Recovery](https://www.bitcoinsv.design/guide/daily-spending-wallet/backup-and-recovery/recovery/): Putting a wallet back on a new device: both parts of the backup, in order, with honest reporting of anything that did not come back. ## Savings wallet A wallet for larger amounts that never connects to apps, with multi-key protection and deliberate top-ups. - [Savings wallet](https://www.bitcoinsv.design/guide/savings-wallet/): A wallet for money that moves rarely: several keys, no app connections, and deliberate top-ups to the wallet that does the spending. - [Time-based recovery](https://www.bitcoinsv.design/guide/savings-wallet/time-based-recovery/): A recovery path that opens after a period of inactivity, how BSV builds it without CHECKLOCKTIMEVERIFY, and the maintenance that keeps it from firing by accident. ## Inheritance wallet Long-term savings with a plan for passing funds on. - [Inheritance wallet](https://www.bitcoinsv.design/guide/inheritance-wallet/): Long-term savings with a plan for passing them on: what the arrangement is, who it is for, and the five flows it needs. - [Overview](https://www.bitcoinsv.design/guide/inheritance-wallet/overview/): The people, the keys and the rules: how an inheritance arrangement is shaped, and what each participant can and cannot do. - [Wallet creation](https://www.bitcoinsv.design/guide/inheritance-wallet/wallet-creation/): Setting up an inheritance arrangement so the owner finishes it: deferring what can wait, saving progress, and building the recovery path last. - [Onboarding cosigners](https://www.bitcoinsv.design/guide/inheritance-wallet/onboarding-cosigners/): Getting the configuration and a key to each person who will need one, and making sure they understand what they are holding. - [Backup](https://www.bitcoinsv.design/guide/inheritance-wallet/backup/): What an inheritance arrangement has to keep, who keeps each part, and the document that makes it recoverable by somebody who has never used the app. - [Making changes](https://www.bitcoinsv.design/guide/inheritance-wallet/making-changes/): Replacing a lost device, changing who is involved, and moving the funds. The routine work that decides whether the arrangement is still real in ten years. - [Succession](https://www.bitcoinsv.design/guide/inheritance-wallet/succession/): What the beneficiaries do, designed for the worst circumstances anybody uses this product in. ## Wallet patterns Several wallets at once, one shared between people, and one that grows. - [Wallet patterns](https://www.bitcoinsv.design/guide/wallet-patterns/): Three ways of structuring wallets that are not a wallet design in themselves: several at once, one shared between people, and one that grows. - [Multiple wallets](https://www.bitcoinsv.design/guide/wallet-patterns/multiple-wallets/): Running everyday, savings and agent wallets side by side: how separate they need to be, and how to keep that from feeling like admin. - [Shared wallet](https://www.bitcoinsv.design/guide/wallet-patterns/shared-wallet/): Money more than one person controls: how the approval rule is enforced by the script rather than by policy, and what that costs. - [Upgradeable wallet](https://www.bitcoinsv.design/guide/wallet-patterns/upgradeable-wallet/): Start on one key, move to several when the balance justifies it, without the user having to understand key schemes on day one. ## Pay-per-use reader A reading app that charges by the article: first visit, connecting, an allowance, the meter, receipts and refunds. - [Pay-per-use reader](https://www.bitcoinsv.design/guide/pay-per-use-reader/): A reference design for a reading app that charges by the article, with no subscription and no account: who it is for, its three flows, and the patterns it applies. - [First visit and connecting](https://www.bitcoinsv.design/guide/pay-per-use-reader/first-visit/): How The Satoshi Vision gets a new reader from a free front page to a first 20 sat article and an allowance, asking for each thing only when it is needed. - [Reading and the meter](https://www.bitcoinsv.design/guide/pay-per-use-reader/reading/): How The Satoshi Vision charges inside an allowance without a prompt, shows the running total and a stop control on every paid article, and handles a used-up allowance and a failed payment. - [Receipts, refunds and leaving](https://www.bitcoinsv.design/guide/pay-per-use-reader/receipts-and-leaving/): What Anna sees afterwards: grouped payments in her wallet, a receipt page in The Satoshi Vision, a refund paid as a new payment, a price change, and what the app shows once she revokes it. ## Connected web app A ticketing site with no accounts: signing in with a wallet, proving an age with a Pass, buying, coming back and leaving. - [Connected web app](https://www.bitcoinsv.design/guide/connected-web-app/): A reference design for a ticketing website with no accounts and no passwords: signing in with a wallet, proving an age with a Pass, buying a ticket, coming back and leaving. - [Signing in](https://www.bitcoinsv.design/guide/connected-web-app/signing-in/): How Example Tickets signs Anna in with her wallet: one button for every visit, the wallet's prompt, what the site says it received, a returning visit with no prompt, and a second device. - [Proving an age](https://www.bitcoinsv.design/guide/connected-web-app/proving-an-age/): How Example Tickets asks for proof that Anna is over 18 at checkout for an over-18 gig: one field from a Pass, the wallet's prompt, what happens when she has no Pass, and a refusal that is not an error. - [Buying a ticket](https://www.bitcoinsv.design/guide/connected-web-app/buying-a-ticket/): How Anna buys a ticket on Example Tickets: the review screen, the wallet's payment prompt, the ticket arriving in her wallet as something she holds, and the ticket on the night. - [Coming back and leaving](https://www.bitcoinsv.design/guide/connected-web-app/coming-back-and-leaving/): How Anna signs out of Example Tickets, disconnects it from her wallet, sees what the site keeps about her, and keeps her ticket when she leaves. ## Agent with a budget An AI assistant that buys data for somebody: setting it up, its limits, approvals, the activity trail and stopping it. - [Agent with a budget](https://www.bitcoinsv.design/guide/agent-with-a-budget/): A reference design for an AI research assistant that buys data and articles on somebody's behalf: its own wallet, four limits, approvals, the activity trail, and stopping it. - [Setting it up](https://www.bitcoinsv.design/guide/agent-with-a-budget/setting-it-up/): Giving Scout its own wallet, choosing its four limits, funding it from Bitcoin SV Wallet, and the one review of the whole delegation before it starts. - [While it works](https://www.bitcoinsv.design/guide/agent-with-a-budget/while-it-works/): What Scout does with nobody watching: paying inside its limits without prompts, asking Anna about anything outside them, reaching its budget, and handling a service that fails or asks for too much. - [Reviewing what it did](https://www.bitcoinsv.design/guide/agent-with-a-budget/reviewing-what-it-did/): How Anna finds out what Scout spent while she was away: the daily summary, the activity trail by task and service, the record behind each purchase, and what to do when something looks wrong. - [Stopping it](https://www.bitcoinsv.design/guide/agent-with-a-budget/stopping-it/): Pausing Scout at once, revoking its delegation, sending what is left back to Bitcoin SV Wallet, and what Scout tells Anna about the task it was in the middle of. ## Research How to run studies on BSV products, the five personas, and the published research worth reading. - [Research](https://www.bitcoinsv.design/guide/research/): Running studies on BSV products: the constraints money adds, who to recruit, interview guides and test plans to copy, vocabulary methods, five personas, and how to write up what you find. - [Conducting research](https://www.bitcoinsv.design/guide/research/conducting-research/): Where to start a study of a BSV product: the three constraints money adds, the questions worth asking, what to test, and how to keep participants' finances private. - [Recruiting participants](https://www.bitcoinsv.design/guide/research/recruiting-participants/): Who to recruit for a study of a BSV product, how to screen for them, how to pay them, and how to keep their financial details out of your notes. - [Interview guides](https://www.bitcoinsv.design/guide/research/interview-guides/): Two discussion guides you can copy, one about a first wallet and one about paying inside an app, plus what not to ask and how to talk about money without asking for amounts. - [Usability test plans](https://www.bitcoinsv.design/guide/research/usability-test-plans/): Three test plans you can run: connecting a wallet and granting a permission, paying per use inside an allowance, and recovering a wallet from its backup. - [What people call things](https://www.bitcoinsv.design/guide/research/what-people-call-things/): Four methods for testing a product's words with the people who will read them, and a template for testing the guide's own vocabulary: handle, Pass, allowance, recovery words, connect and sats. - [User personas](https://www.bitcoinsv.design/guide/research/personas/): Five people to design against, what each needs from a BSV product, and where each one is lost. - [Writing up findings](https://www.bitcoinsv.design/guide/research/writing-up-findings/): A template for writing up a study so others can judge it, how to anonymise it, and how to contribute a finding to this guide by citing the rule it tests. - [Published research](https://www.bitcoinsv.design/guide/research/published-research/): Published research on how people use wallets, with a note on which findings transfer to BSV and which do not. ## Product and business Business models small payments make possible, pricing, what to measure, growth that pays, custody as a product decision, and how much to say about BSV. - [Product and business](https://www.bitcoinsv.design/guide/product/): The decisions a founder or product lead makes about a BSV product: how it earns, what it charges, what it measures, how it grows, who holds the money, and how much to say about the network. - [Business models](https://www.bitcoinsv.design/guide/product/business-models/): The ways a BSV product can earn when a payment costs less than a penny: pay per use, metering, allowances, tipping, credit to try, unbundled subscriptions and models without advertising, with what each asks of the user. - [Pricing](https://www.bitcoinsv.design/guide/product/pricing/): Setting prices for a BSV product: price in local currency and settle in satoshis, show the price before the action, round honestly, change prices without surprises, and refund with a new payment. - [Measuring a product](https://www.bitcoinsv.design/guide/product/measuring-a-product/): The metrics that mean something for a BSV product, from a first payment as activation to recovery readiness and agent budgets, the vanity numbers to ignore, and how to measure without linking people's payments to who they are. - [Growth that pays](https://www.bitcoinsv.design/guide/product/growth-that-pays/): Growing a BSV product by paying people directly: referral payouts that arrive instantly, paying for contributions, credit to try, shareable handles and payment links, and the fraud every reward attracts. - [Custody as a product decision](https://www.bitcoinsv.design/guide/product/custody/): Who holds the keys in your product: the user's own wallet, the product holding funds, or an arrangement in between, compared as onboarding, support, recovery and responsibility trade-offs. - [Talking about BSV](https://www.bitcoinsv.design/guide/product/talking-about-bsv/): How much of the network a product should show, when to name it as Bitcoin SV or BSV, how to write a store listing and a landing page, and the copy that loses people. ## How it works Transactions, payments, keys and backups, identity, privacy, nodes and what still has to work with older systems. - [How it works](https://www.bitcoinsv.design/guide/how-it-works/): The technical ideas behind BSV products, explained for the person drawing the screens rather than the person writing the node. - [Backups](https://www.bitcoinsv.design/guide/how-it-works/backups/): What a complete BSV wallet backup contains, why recovery words alone may not be enough, and how to design backup and recovery honestly. - [Transactions](https://www.bitcoinsv.design/guide/how-it-works/transactions/): What happens to a BSV transaction from signing to settlement, and what that means for status, fees and confirmation design. - [Coin selection](https://www.bitcoinsv.design/guide/how-it-works/coin-selection/): Which outputs a wallet spends, what that choice reveals, and why users should almost never see it. - [Payments](https://www.bitcoinsv.design/guide/how-it-works/payments/): How BSV payments move directly from sender to recipient, and the formats a wallet should support. - [Identity](https://www.bitcoinsv.design/guide/how-it-works/identity/): What identity means for a BSV wallet: the identity key, app-specific keys, Passes, mutual authentication, discovery, key linkage and messages. - [Wallet setups](https://www.bitcoinsv.design/guide/how-it-works/wallet-setups/): Why everyday money, long-term savings and an agent's budget belong in separate wallets, and how to design the moves between them. - [Nodes and verification](https://www.bitcoinsv.design/guide/how-it-works/nodes/): Why BSV wallets verify with block headers and merkle proofs instead of running a node, and what that means for the screens you build. - [Wallet privacy](https://www.bitcoinsv.design/guide/how-it-works/wallet-privacy/): What key derivation (BRC-42) hides by default, what it does not, and the four leaks a BSV wallet still has to design against. - [Legacy compatibility](https://www.bitcoinsv.design/guide/how-it-works/legacy-compatibility/): Older payment and wallet methods a BSV product may still meet, how they differ from the recommended approach, and how to design for each. - [Overview](https://www.bitcoinsv.design/guide/how-it-works/private-key-management/overview/): What a BSV wallet actually holds, why one master key is not one address, and the four ways products control who can sign. - [Automatic cloud backup](https://www.bitcoinsv.design/guide/how-it-works/private-key-management/cloud-backup/): Encrypted backup to a service, what it actually protects against, and the circular-dependency trap that makes a backup fail when it is needed. - [Manual backup](https://www.bitcoinsv.design/guide/how-it-works/private-key-management/manual-backup/): Recovery words and backup shares: what BSV wallets write down, how the flow should go, and why the words alone are not the whole wallet. - [External signers](https://www.bitcoinsv.design/guide/how-it-works/private-key-management/external-signers/): Keeping the key on a device that never goes online, how transactions cross the gap on BSV, and what the user has to check for it to be worth anything. - [Multi-key](https://www.bitcoinsv.design/guide/how-it-works/private-key-management/multi-key/): Several keys, a set number of which must sign: how it works on BSV without P2SH, and the three jobs it is good at. - [Private key management](https://www.bitcoinsv.design/guide/how-it-works/private-key-management/introduction/): How BSV wallets protect and back up the master key, and which page to read for what you are building. ## Glossary BSV terms, from Action to UTXO. - [Glossary](https://www.bitcoinsv.design/guide/glossary/): BSV terms a designer will meet, what they mean, and which ones belong in an interface rather than in documentation. - [Address](https://www.bitcoinsv.design/guide/glossary/address/): What a BSV address is, why users should rarely see one, and the rules for showing one when they must. - [Wallet](https://www.bitcoinsv.design/guide/glossary/wallet/): One word for several different things. Which one you mean decides what the screen has to say. ## Resources BSV Academy, developer documentation, the BRC standards and design files. - [Resources](https://www.bitcoinsv.design/guide/resources/): Where to go next: the specifications, the libraries, the research that transfers, and practice work. - [Design files](https://www.bitcoinsv.design/guide/resources/design-files/): Source files worth reusing, what each one gets wrong for BSV, and what nobody has made yet. - [Design challenges](https://www.bitcoinsv.design/guide/resources/design-challenges/): Ten take-home problems, each a real BSV design question with no settled answer. Four to six hours each. - [Learning bootcamp](https://www.bitcoinsv.design/guide/resources/learning-bootcamp/): A four-week self-guided route through this guide, from knowing nothing to designing a BSV wallet flow. - [Code resources](https://www.bitcoinsv.design/guide/resources/code-resources/): The libraries, services and reference implementations a BSV product is built from. ## Case studies Write-ups of BSV products by the teams that built them: the five we most want, and how to contribute one. - [Case studies](https://www.bitcoinsv.design/guide/case-studies/): Real BSV products and the design decisions behind them. This section is empty, and this page says what it is waiting for. ## Contribute The guide is open. How to suggest a change and add to it. - [Contribute](https://www.bitcoinsv.design/guide/contribute/): How to correct, review, illustrate or add to this guide, and where the open work is. - [Propose a change](https://www.bitcoinsv.design/guide/contribute/propose-a-change/): The mechanics of changing a page, from a one-line typo fix in the browser to a larger change on your own machine. - [Review](https://www.bitcoinsv.design/guide/contribute/review/): Reviewing a proposed change: the easiest way to start contributing, and the check this guide needs most. - [Content guidelines](https://www.bitcoinsv.design/guide/contribute/content-guidelines/): How this guide is written: who it is for, the rules the build enforces, and the vocabulary that is not negotiable. - [Illustration guidelines](https://www.bitcoinsv.design/guide/contribute/illustration-guidelines/): Making and preparing the guide's artwork: what to draw, where to put it, and how it gets onto the page. - [Formatting](https://www.bitcoinsv.design/guide/contribute/formatting/): Everything a page can do: front matter, callouts, open questions and ladders, tables, code, images and placeholders, each shown as it renders. - [Media](https://www.bitcoinsv.design/guide/contribute/formatting/media/): Images, grids and animations: what the page can do with artwork, shown as source and as it renders. - [Case studies](https://www.bitcoinsv.design/guide/contribute/case-studies/): How to write up a BSV product you worked on, and what makes one worth reading. ## Common questions Short answers to the questions people arrive with. Each links to the page it summarises. ### New to digital money No prior knowledge needed. Start with what BSV is and how a wallet works. - What is BSV? See https://www.bitcoinsv.design/guide/getting-started/introduction/ - What can I use it for? See https://www.bitcoinsv.design/guide/how-it-works/payments/ - What is a blockchain? See https://www.bitcoinsv.design/guide/getting-started/technology-primer/ - What is a wallet? See https://www.bitcoinsv.design/guide/glossary/ - Do I need a whole coin to use BSV? See https://www.bitcoinsv.design/guide/patterns/amounts-and-units/ - How do I send or receive a payment? See https://www.bitcoinsv.design/guide/how-it-works/payments/ - Does connecting a wallet let an app spend my money? See https://www.bitcoinsv.design/guide/patterns/connecting-a-wallet/ - What happens if I lose my phone? See https://www.bitcoinsv.design/guide/how-it-works/backups/ ### Building a BSV app The connection, language and spending decisions your interface needs to explain. - How does an app get permission to use somebody's BSV wallet? See https://www.bitcoinsv.design/guide/patterns/connecting-a-wallet/ - Should an interface say bitcoin, Bitcoin SV, or BSV? See https://www.bitcoinsv.design/guide/glossary/ - Should amounts be shown in BSV or in satoshis? See https://www.bitcoinsv.design/guide/patterns/amounts-and-units/ - Can an AI agent spend from a wallet on someone's behalf? See https://www.bitcoinsv.design/guide/patterns/letting-an-agent-spend/ ### Answers for your users Short answers in your users' words, for your app's help screens, tooltips and support replies. The guide's text is under the Open BSV License, so copy them into your BSV product. - What happens when I connect my wallet to an app? See https://www.bitcoinsv.design/guide/patterns/connecting-a-wallet/ - What is an allowance? See https://www.bitcoinsv.design/guide/patterns/permissions-and-allowances/ - Can I cancel or reverse a payment? See https://www.bitcoinsv.design/guide/how-it-works/transactions/ - Why is the fee so small? See https://www.bitcoinsv.design/guide/daily-spending-wallet/sending/send-fees/ - What is a handle? See https://www.bitcoinsv.design/guide/patterns/paying-by-handle/ - What are recovery words? See https://www.bitcoinsv.design/guide/daily-spending-wallet/backup-and-recovery/manual-backup/ - Why do I need a wallet backup as well as recovery words? See https://www.bitcoinsv.design/guide/how-it-works/backups/ - What is a Pass? See https://www.bitcoinsv.design/guide/how-it-works/identity/ - My payment failed. Did I lose money? See https://www.bitcoinsv.design/guide/daily-spending-wallet/sending/ ### Coming from another chain Assumptions from other chains to check before they reach your screens: fees, payments, recovery and infrastructure. - Does a BSV wallet need a fee picker? See https://www.bitcoinsv.design/guide/daily-spending-wallet/sending/send-fees/ - Can a payment be accepted before it is mined? See https://www.bitcoinsv.design/guide/how-it-works/transactions/ - What stops someone sending BSV to a BTC address by mistake? See https://www.bitcoinsv.design/guide/patterns/wrong-network-payments/ - Are recovery words enough to back up a BSV wallet? See https://www.bitcoinsv.design/guide/how-it-works/backups/ - How is a token on BSV different from one on a smart-contract chain? See https://www.bitcoinsv.design/guide/patterns/holding-tokens/ - Do people have to run a node to use BSV safely? See https://www.bitcoinsv.design/guide/how-it-works/nodes/ ## Optional - [Everything, in full](https://www.bitcoinsv.design/llms-full.txt): all 123 pages as one markdown file - [Search](https://www.bitcoinsv.design/search/?q=): full-text search, one page per query string - [Checklists](https://www.bitcoinsv.design/checklist/): every do and don't in the guide, assembled by what is being built - [Skill router](https://www.bitcoinsv.design/SKILL.md): start here; routes to the right agent skill by user action or BRC standard - [Skills](https://www.bitcoinsv.design/skills.txt): the guide as agent skills, each shipping the rules it enforces, most costly first - [Every rule as JSON](https://www.bitcoinsv.design/api/rules.json): each do and don't with a citation URL and a severity, most costly first - [MCP server](https://www.bitcoinsv.design/mcp/): search_guide, read_page, list_sections, list_rules - [Common questions](https://www.bitcoinsv.design/faq/): the same answers as above, in full - [About](https://www.bitcoinsv.design/about/): what this guide is and what it recommends - [Contribute](https://www.bitcoinsv.design/guide/contribute/): how to propose a change - [Licence](https://github.com/bsv-blockchain/teranode/blob/main/LICENSE): Open BSV License Version 6