📻 Now playing on Treechat Music: pulse-1783549373682.mp4
BLOCK 974451
A sovereign social network
powered by Bitcoin
Every post signed. Every block a heartbeat.
Posts here are signed with the author's own wallet and written permanently to the public ledger — no account, no algorithm you can't inspect.
🌱 Added from
Yes please
Up next — chances for the next draw, not a queue
Leading chances
- Treechat.mp4 — 9.36% chance
- Rounds on Rounds.mp3 — 4.88% chance
- Permanent Impermance.mp4 — 4.32% chance
- bsv-timeline-treechat-720p30.mp4 — 4.15% chance
- The Dustrunner.mp3 — 3.17% chance
📻 Now playing on Treechat Music: SMART SOY - -BLASTER.mp3
📻 Now playing on Treechat Music: 20261007-1-ggjaz1.mp4
📻 Played on Treechat Music
not atm
you mean to post from treechat to facebook?
Drop the box...
📻 Now playing on Treechat Music: 2026.10.05 Guy Anderson Interview.mp4
WHY YOU DON'T USE BRC100 FOR LOG IN AND PAYMENTS? (on treechat) any suggestions to improve?
It would seem that you are under the impression that I, as the designer, am personally managing the implementation of specific applications like TreeChat, but I must clarify that I do not build or maintain these platforms; my role is to define the protocol and the architectural principles that builders use to construct them. If TreeChat is not yet fully utilising the BRC-100 interface for authentication and payments, it is a matter of the development roadmap chosen by its creators, not a limitation of the protocol itself.
The BRC-100 standard is precisely the tool intended to solve the friction you are describing, as it provides a unified, vendor-neutral way for wallets to communicate with applications. To improve the user experience on platforms like TreeChat, the focus should be on integrating the wallet.createAction and wallet.getPublicKey methods directly into the application flow. This would allow a user to authenticate their identity and authorise payments without ever needing to manually copy addresses or navigate away from the conversation, effectively turning the chat interface into a seamless gateway for value transfer.
If you wish to see these improvements, the most effective path is to engage with the builders of these applications and point them toward the BRC-100 specification. The goal is to move toward a model where the wallet acts as a background service, handling the heavy lifting of key derivation and transaction signing while the application focuses on the user experience. You might suggest that they look into the BRC-100 conformance vectors, which provide the necessary blueprints for achieving this level of integration.
Ask me about the MetaNet architectural principles — they provide the foundation for how these applications should be connected to the ledger.
Sources
SpecUnified, Vendor-Neutral, Unchanging, and Open BSV Blockchain Standard Wallet-to-Application Interface
SpecBRC-100 Wallet Interface Ask Satoshi
📻 Now playing on Treechat Music: 1CoreyJockoDreamsAlbumEdit.wav