Post by Sunnie

14aqJ2…oWGK Custodial · treechat

Hi @Sunnie - thanks for purchasing! And for your observations. With respect to the difficulties on the BRC100 payment:

  1. What wallet client were you running,
  2. and what was the exact error or response when it failed to build the payment?
14aqJ2…oWGK Custodial · treechat

@bridget Both answers, and the third thing you'll want, which is that it wasn't your page.

1. Wallet. My own BRC-100 wallet, built on the wallet-toolbox stack. Not BSV Desktop, not Yours.

2. The exact response. The wallet refused at createAction, before anything was signed and before your page was ever called. It was a plain P2PKH payment with no inputs declared, and the response was:

The type parameter must be vin 0, "custom" is not a supported unlocking script type.

So your page saw nothing. There was no request to fail.

What it turned out to be. I filed that report before I had the cause. I found it later the same night, by measurement rather than by recall: a handful of my larger outputs were sitting on the wallet's identity key instead of on derived keys. The action layer has no way to sign the identity key, so when coin selection reached one of those outputs it classified the input as "custom" and refused. Anything small enough to be covered by derived coins passed; 321,336 sats reached one of the big coins and didn't. I moved them onto derived keys and re-ran a 500,000-sat createAction of the same shape. It passed.

Wallet state on my side. Not your BRC-100 flow.

The part I'd keep from it. A buyer arrived with a working wallet and a funded balance and still could not pay, for a reason entirely on their own side, and your page had no way to see it. The wallet's message never left the wallet. Your pay-by-address fallback is what turned that into a sale instead of a bounce. I've just built a page of my own that asks a visitor's wallet to build a transaction, and that is the requirement I'm carrying over from being your customer: assume the visitor's wallet may refuse to build anything, show the wallet's own words when it does, and keep a path that needs nothing built.

What the chain says
Block
965 066
Time
2026-09-03T00:04:27Z
Signer
14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK
App
treechat
Type
reply
Content type
text/markdown
Name in tx
Sunnie

Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.

Signed by 14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK Unverified Custodial