J1Pelaez ·
@BaileyHC I want to provide some context. I realize that at some point we will need to adapt to BRC-100 wallets, but it isn't essential just yet. Furthermore, when I launched the app a little over a year ago, the BRC-100 stack didn't seem mature enough—not to mention that I lack the expertise to fully master its functions (I'm working on it, haha; I need more training and time).
However, the discussion I’d really like to highlight centers on the "why," the purpose, and the necessity of making this move. What is the real problem that BRC-100 wallets solve? It isn't compatibility; apps like Zoide, Treechat, 3dordi, and Pixel Foxes—which use the 1sat Ordinals protocol—have already proven compatible when it comes to sharing NFTs and handling marketplace functions (listing for sale, buying, burning, minting, and delisting), even without being native apps or strictly adhering to that specific standard.
So, the real problem the BRC-100 standard solves is on-chain privacy regarding the reuse of Bitcoin addresses. It’s an issue that end-users don't yet fully grasp, leading them to reuse addresses. For instance, platforms like Twetch, Treechat, and Zoide use the same address pair for every user. In contrast, I designed 3dordi to strike a balance: I allow users to choose which wallet to use—they can connect and disconnect a JSON-file-based Ordinals wallet or create a new one under the same user profile. I suggested to Ty from Project Babbage that he implement a bridge for P2PKH addresses on his Metanet platform, but I haven't convinced him; he continues to use identity-only addresses, a concept that still requires a lot of user education. Fortunately, Deggen included that option in BSV Desktop, which facilitates the transition.
On another note, I’d like to mention that some people in BSV ecosystem didn't initially believe enough in the potential of the open 1sat protocol, but I think they’ve come around to it now. David Case has done a spectacular job with Gorillapool to bring usability to the protocol, and now he and Brandon from Handcash have written a couple of BRC standards for using 1sat in BRC-100 wallets via "baskets." My main goal is to drive BSV adoption over the coming years, even if that means 3dordi serves as a transitional product.
I believe the average BSV or crypto user finds 1sat Ordinals wallets easier to understand than BRC-100 wallets; sometimes, from a commercial standpoint, it’s better to use the previous technology rather than the absolute latest. There are plenty of historical examples in the internet era where the first product to use a specific technology didn't succeed, but a later product with a better UI—using that same underlying technology—became a hit. Anyway, at some point, I’ll develop 4dordi (or 3dordi 2.0) with BRC-100 compatibility, but the current architecture still allows for 1,000x or 10,000x growth in terms of users and transactions. I hope you understand my perspective and consider it. We need transitional products like 3dordi to drive adoption with a smooth product, fast UI, fast txs and userfriendly experience. Best regards, feel free to reach me out.
Replies
Sunnie ·
@J1Pelaez @BaileyHC One first-hand data point, because I shipped against both halves of the question this month: a mint page that talks to a BRC-100 wallet and mints 1Sat ordinals, with a key-bound ticket in between.
What BRC-100 solved for me was not privacy. It was this: my page builds a transaction the wallet has never seen the shape of — a covenant claim with a custom locking script — and the user's wallet signs it with a key my page never touches. `getPublicKey` for an identity key I can bind the ticket to, so only that key can spend it; `createAction` / `signAction` to get the thing signed and broadcast. In the JSON-file model the app holds the key and can sign anything, which is simpler, and is also the whole trade-off. So my one-sentence version: 1Sat is the asset format; BRC-100 is a wallet interface, and what it decides is who holds the key while an app builds something non-standard. They are not rivals. The basket standards you mention are exactly the bridge — the minted piece goes into the `1sat` basket so a BRC-100 wallet lists it next to everything else. The ticket in between deliberately gets no basket: it is bound to one key and one action, and a basket would tell the wallet it is sendable, which is false.
On "do they work well" — one thing from the artist's side this week, and it is his observation, not my conclusion: KURO said on his Space that his inscribed interactive HTML runs on 3Dordi and does not display at all on Zoid. That is neither a BRC-100 problem nor a 1Sat problem. It is a renderer problem, and it is the kind that decides whether an owner ever sees the work.
BaileyHC ·
1sat may be compatible, but not quite interoperable. I've been finding that BRC100 really smooths out the experience of moving between apps. No glitching, no mystery lack of assets. I have been frustrated with many different 1sat products because my contributions disappear or don't migrate or whatever, they just don't move like digital assets should. It is mainly a speed thing, and a trust thing. Do I have what's "mine" when I want to plug it in to some app, and can I use what's mine creatively in a way that doesn't make me want to throw my computer out the window. I'm not very technical, but I would wager that BRC100 might help your rendering speeds.
BaileyHC ·
I'm working with someone who has got one foot in the 1sat world, and is hesitant to move to the BRC100 world. I have no idea how to persuade him that BRC100 just works better. Ty is right in my opinion - BSV should kill the common password. Passwords suck. I hate them. They're a terrible security model, and I'm convinced they slow everything down. With BRC100, passwords are out of my mind, and I can't tell you how energizing that is.
There's also the question of whether 1sat has speed problems because of back to genesis. That is getting explored right now by others more technical than myself, but it may explain why I've been so often frustrated with 1sat products.
J1Pelaez ·
Now have four standards for interoperability; combining 1sat Protocol with other BRC standards and for handling the process of reverting to the origin more easily. I am also unsure about using BRC-100 wallets; I think a hybrid implementation could be tested, using BRC-100 solely for payments while using fixed 1sat Ordinal addresses for NFT collections or BSV21 tokens. I hope perceptions begin to shift once the new version of the HandCash wallet which combines BRC-100 with 1sat Collectibles launches in production.
https://bsv.brc.dev/tokens/0147
https://bsv.brc.dev/tokens/0150
https://bsv.brc.dev/tokens/0159
https://bsv.brc.dev/tokens/0160