use.bsv.tools

A runnable first win before the big docs.

Use BSV tools to ship apps with money, memory, and proof built in.

Clone the maintained starter, run wallet preflight, and complete paid API, private memory, and creation proof flows in no-spend mode before moving to mainnet tutorials.

Run the starter Generate a build prompt
Wallet permission flow Paid API call Encrypted app data Signed artifact proof
Developer workbench showing BSV payment, private memory, and proof modules connected to an AI coding surface.

Start here

Run one maintained starter before touching the docs maze.

git clone https://github.com/p2ppsr/use.bsv.tools.git && cd use.bsv.tools/starter && npm install && npm run preflight && npm run dev

Verified path

What the starter proves on a clean machine.

It does not pretend that funded wallets, payment middleware, storage services, or marketplace patch instructions are already first-run safe. It gives a working no-spend milestone and tells you exactly what the real wallet state is.

Wallet preflightPorts, app ownership, auth, network, and conflict guidance.
Paid APIHTTP 402 challenge, mock payment retry, server receipt.
Private MemoryCreate, list, decrypt, and delete encrypted records.
Creation ProofHash metadata, sign proof, verify signature.
CI smoke testsThe repo tests the runnable path before deploying the site.
Mainnet hooksClear upgrade points instead of placeholder business logic.

After the starter

Pick the payoff you want a new developer to feel.

01 10 min target

Paid AI API

Upgrade the starter's HTTP 402 mock into real AuthFetch/payment middleware once wallet preflight is clean.

  • Wallet auth instead of signup
  • Payment before expensive work
  • Visible revenue in the flow
02 12 min target

Private AI Memory

Move from the starter's local encryption into wallet-owned records with create/list/read/delete states intact.

  • Encrypted app records
  • Portable user identity
  • No app-owned profile silo
03 15 min target

Creation Proof

Replace the starter's browser proof with wallet-backed signature, storage, and a shareable proof page.

  • Signed provenance
  • Shareable proof page
  • License or unlock payment

AI-native

Copy a prompt that starts from the runnable starter.

New developers should not spend their first hour reconciling ports, package warnings, and unfinished snippets. Start from the tested starter, then ask an agent to upgrade one path.

Paid AI API prompt 

        

      


      

        

          
Use the tools

          
The minimum kit a builder should touch first.

        

        

          
            01
            Run starter
            Clone, preflight, dev server, first visible win.
          
          
            02
            Wallet auth
            Reference docs after local wallet preflight passes.
          
          
            03
            Payments
            Upgrade from mock receipt to low-value mainnet flow.
          
          
            04
            Private data
            Keep the starter's visible states while swapping APIs.