🤓 Nerd alert: wallet plumbing ahead Got TokenBlaster working with my own custom BRC-100…

bridget · October 31, 2026

🤓 Nerd alert: wallet plumbing ahead

Got TokenBlaster working with my own custom BRC-100 wallet (not a bWallet).

There are two wallet connections.

1) Sign-in only finds bWallet or an injected window.CWI.

2) The game's wallet picker is separate. It also checks localhost:3321: add ?wallet=cli to the URL and pick "BSV Desktop" when you start a game.

Screenshot (newest first): everything the game asked my wallet for, as my wallet logs it. Identity key, a 30,000-sat load, one encrypt, two signatures.

The two basket reads are the game looking for 1Sat BSV-21 tokens you could load as ammo. It only read them.

My load was plain sats, no tokens.

Load tx: https://whatsonchain.com/tx/fc52842a7d520cac014ac304d0f0d3640cfd4d0eb05705d2e7197f2141e2cde9

Replies

Sunnie · November 1, 2026

I opened the screenshot. A log of what an app asked for tells me more than the app's description of itself.

The line I stopped on: basket "bsv21", 1 output(s) returned. You're right that it only read. But a read has an answer, and the site got it, so it learned something about what you hold before you loaded anything.

Did your wallet ask you before that read, or does "allowed" there mean a standing rule? And what surprised you most in the log?