Search the guide
Search the guide
Design decisions for wallets, payments and connected apps. Read the guide, work through a checklist, or give your agent the skills to build from it.
For designers, researchers, founders, and the agents working with them.
The everyday issue
A few minutes of reading. A fresh way to see things.
A place to begin
Three ways in, depending on the work you do. Each one is a short reading list.
The principles, then the patterns for connecting, paying and charging, then reference designs you can borrow screens from.
The designer's route
What real money adds to ordinary research, five personas to recruit for, and the published studies worth reading first.
The researcher's route
The business models small payments make possible, pricing, who holds the keys, and the numbers worth measuring.
The founder's routeWorking examples, not just words
Try the decisions behind a good BSV interface. Each example links to the page that explains it.
Make every permission specific, understandable and easy to take back.
The Satoshi Vision
satoshivision.example.com
Know who you are
Required to connect
Small payments
Up to 100 sats a day
Small payments need approval each time.
Say who gets paid, what it costs and when the recipient has accepted it.
Maya Chen
maya@example.com
25sats
One article · The Satoshi Vision
This can't be undone.
A Pass can answer a question without handing over someone's whole identity.
Example Bar asks
Are you over 18?
Name, date of birth and address stay private.
Recovery words restore your keys. A wallet backup restores your records: which money is yours and how to spend it. Design for both.
Recovery words
Your key recovery material
Wallet backup
Your wallet's records, encrypted
Save both parts to try the recovery check.
Fictional interfaces. These controls only change the examples.
A reference with room to go deeper
Every page written for BSV. Free to read. Published under the Open BSV License Version 6.
Some teams ship a BSV product with nobody whose job is the interface. The guide is published for them too: the same decisions, in forms an agent can follow.
Your agent
Review the receive flow before shipping.
From the guide
Procedures your agent can load, with a router that picks the right one: payments, wallet connection, micropayments, agent spending, tokens, backup and a design review. Each ships the guide's own rules, those that can cost a user money first, every one linked to the sentence it came from.
See the skillsRead-only. Search every page, read one in full, list the sections, or pull the rules that apply to what is being built in one round trip, mid-task, without guessing at a URL.
Use the MCP serverA map of every page at /llms.txt and the whole text at /llms-full.txt, so a model quotes the guide with a source instead of paraphrasing it from memory.
Read /llms.txtA reference you work from needs more than pages.
Press / or Ctrl K (⌘K on a Mac). Titles and headings answer as you type, the full text follows a moment later, and every search has an address you can send someone.
Every do and don't becomes a checklist. Choose what you are building to get one list from every page that applies, then export a report that links each rule.
Reading progress and saved pages, kept in your browser. No account, nothing sent anywhere.
All 1022 rules have their own address. Link one in a pull request and anyone can open the sentence it came from.
The guide has the decisions behind it. The checklist has the rules, ready to tick.
