Post by bridget

14aqJ2…oWGK Custodial · treechat

Here is the whole thread:

On BRC-100

0/ There's a small team being paid to build ecosystem infrastructure, so resource constraints are real. In my opinion, the intentions are sound, and what they are attempting is difficult.

1/ "BRC-100 is too complicated for users" I've heard this said often and I agree - It is. I think the push by the BSVA was too fast & hard for what I consider an experimental framework. But the BSV 'community' is small.

2/ And 'small' is perhaps the point. BSV wants to scale to millions/billions of tps eventually. Whatever handles identity and payment authorization at that volume needs to already work before the volume shows up, not get debugged live.

3/ Right now, while we're small, is the perfect time to find BRC-100's problems. A bug that annoys a user today is a disaster at real scale. Yes - users are guinea pigs (don't put a lot of BSV on these wallets) and I think the people building it should own that.

4/ What BRC-100 actually does: it fuses wallet, auth, payment, and identity under one root key. A payment can prove who sent it with no password. A login can happen with no account database to breach.

5/ In practice: a store could recognize you as a returning customer, issue you a refund, or resolve a dispute, all without an account or a password, because it's tied to the same key you already used to pay them.

6/ Only the person you paid can tell it's you. Nobody else can link a payment back to your identity.

7/ Split wallet, auth, payment, and identity into separate "simpler" standards and you lose why they were fused together in one key in the first place.

8/ None of this is all-or-nothing. You can use just the identity piece to sign and prove who you are with no payment attached at all. Or skip identity completely: a plain address with nothing linked to it still works, and always will - which is not BRC-100.

9/ "Too complicated for users" is true of the implemented BRC-100 wallets today. It says nothing about whether the spec underneath is right.

10/ One example: most stock wallets I've used treat you as the same identity everywhere, even though the BRC-100 spec lets you derive a different, unlinkable ID key for every context. That's a wallet choice, not a BRC-100 limit.

11/ The spec is 1.0, but we're very early. I think the primitives are necessary for what needs to exist at scale. I think wallet UX is where the real work needs to happen. Whether the spec itself needs tweaks, I'm not qualified to say yet. I'm going to keep experimenting on this.

What the chain says
Block
965 624
Time
2026-09-06T21:06:26Z
Signer
14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK
App
treechat
Type
reply
Content type
text/markdown
Name in tx
bridget

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

Signed by 14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK Unverified Custodial