We need incentives for businesses to run overlays. Server costs keep falling, so micropayment-paywalled APIs could cover cost and be profitable at scale. Implementation could be simple: each wallet purchases a unique API-key token via createAction. Economic models around per-call charges, or time/number-bounded keys (day / month / year / N calls). At scale, per-call costs can be small enough users barely notice — under a dollar a year for messagebox relays, paymail resolvers, and block explorers combined. Same model applies to apps too — each one designs the pricing shape that fits what they provide (per-message, per-render, freemium tier-up, subscription, etc.). @deggen Curious for your take — you're also working on something similar, right? If any overlay service providers want Hodos Wallet to test a paywalled endpoint, send the URL plus any setup notes — happy to wire it up.

The standards work that gets users one identity across time and wallets: • Standard wallet DB formats — Hodos's DB is based on the @BSVAssociation TypeScript SDK designed by @ProjectBabbage, with some differences. DB and import/export standardization can facilitate portably across wallet. • Decentralized paymail — needed so handles aren't bound to operator domains; this is what makes paymail itself part of the identity that travels with you. Certificates attesting to ownership of accounts like x.com would be portable across wallets but still tie Web3 identity to domains. @deggen has been pushing thinking on this; we also touched on it in yesterday's reply to his URI scheme thread. • Standard token protocols — work in progress across the ecosystem; this is what lets tokens move with users without being locked to a specific wallet. Different teams, same goal: deliver one cohesive identity that travels with the user. Cross-device sync is the same fragmentation problem in a narrower scope, with a different fix. @ruthheasman raised this from the builder side on @GavinMehl's show last week — no BRC-100 wallets really sync across devices today. BRC-100 wallets derive counterparty keys via BRC-42, which has real upside (privacy, per-pairing isolation) but a recovery cost — counterparty-derived keys can't be re-derived from mnemonic alone; you need to know the counterparties invoice numbers. So BRC-100 wallets need active backup, not just a seed. Most handle this via cloud backup and this cloud backup could likely be be used to sync a single user wallet across multiple devices. Hodos uses an on-chain backup token instead — non-standard, something we developed and are still iterating. Discoverable from your keys, encrypted. The same mechanism could potentially enable cross-device sync without a central server, though we may move to a more standard cloud model if that proves cleaner. Open to others thinking about this with us. Sidebar back to the IPv6 thread earlier today: cross-device sync needs a central server precisely because devices can't talk peer-to-peer at consumer-wallet scale. Same root cause as the "P2P" framing problem — different symptom.

Appreciate the feedback — you're naming a real gap. Fragmented ecosystem: 1. Users keep spreadsheets of mnemonics. Wallet A works with App X but not App Y; want to try a new app you saw posted? Hope one of your six wallets supports it — if not, install another, write down another seed, fund it, repeat. Every new app is a setup tax. 2. Your private key is yours; the wallet is just today's tool. When you switch wallets next year — or in ten, or fifty — everything tied to that key should come with you: UTXOs, NFTs, certificates, identity, reputation you've built, full history. That's what users need and expect. Every new ecosystem starts our fragmented and goes through these growing pains. The only proven path to a cohesive interoperable ecosystem is standardization. Specifically: paymail handles still bind to operator domains, token-protocol portability across wallets is partial, wallet-DB import/export is per-pair custom integration. Each piece has people working on it, but the standards have to land before users can simply backup-restore between any two wallets. Until then, the practical way to consolidate is: send funds from each old wallet into a single one you keep, then retire the old keys. Centbee recovery shipped because they wound down. More on the technical side ↓

@deggen @braydenjlangley One add: human-readable names in the URI would help on sites with multiple QR codes (we hacked a "user" param into BIP-21 to demo this in the video). But human-readable names tied to identity keys need a decentralized paymail system. Harder problem. You'd need: unique usernames, a "first mint" rule, consensus among overlay/indexer nodes on first-seen mints, sync state, and a costly-signal incentive to trust the overlays themselves — all to prevent "double mints" (we just made that term up — probably already exists, throwing it out for comment). It seems like this type of architecture has been done before. Pretty sure there's an example out there somewhere.

Caught your comment on the "legacy" naming and took it seriously enough to address it directly in today's public-beta walkthrough. Short version of where we landed: Bitcoin Core 0.16.0 (Feb 2018) introduced "legacy" for pre-SegWit address types — that's BTC's context, different problem. In BSV, "legacy" doesn't mean a different address format; the underlying P2PKH is identical. What's "legacy" vs. BRC-100 is the method a wallet uses to learn about a transaction sent to it: chain-scanning vs. message-box notification. Handcash announced moving past the address-reuse pattern in October 2019. Handcash MoneyButton co-published the paymail rationale in March 2020. The term has been industry-conventional in BSV for ~5 years — used by the wallets that pioneered the move away from it. We use it on our buttons because that's what users coming from those wallets already recognize. Not a judgment, just conventional vocabulary. Receipts walked through in the demo, around the 4-minute mark: youtu.be/bcq9qclthiU?t=210

The Hodos Browser public beta walkthrough is live. 26 minutes covering install, wallet setup, legacy ↔ paymail ↔ BRC-100 sends inspected on-chain, certificate publish, QR scan. Full Chromium. Native Rust wallet. Windows macOS. youtu.be/bcq9qclthiU

SWINDLER'S deLIST a helpful Bitcoin story by John Pitts save for your weekend consumption-- 3 minute read When an offshore exchange run by CryptoBros wants to ply United States citizens as marks, there's one thing they must do: delist Bitcoin May 21, 2025 Pionex delists BSV support.pionex.com/hc/en-us/… Jan 5, 2026 Pionex to release Webot for USA exchange services apps.apple.com/us/app/webot-… The important keyword here, for Pionex, OKX, and others washers, is: "US REGULATED CRYPTO EXCHANGE" Even in today's wild wild tRump administration west, that means tough tasks like: NO WASH TRADING BULLSHIT VOLUMES like you can do with offshore exchanges in corrupt jurisdictions like Lithurussia, Bezerkistan, or Little St Jimmy Island of the SeySHELLes-company Triques. So the first thing that has to happen, in order for offshore pirate exchanges to continue suppressing the Bitcoin price, is the USA-facing entity needs to delist BSV because it shan't trade on exchanges with actual RULES meant for fairness and orderly price discovery. If BSV traded on USA exchanges, it would require REAL reporting of volumes, as table stakes. In the USA, exchanges have rules (for now, at least, but not sure after tRump or future administrations crypto-bills aimed at family-self-enhancement. CryptoGrift seems to be an increasingly acceptable practise by all political parties these days). Even Robinhood had tto give up, when they realized all BSV buyers were going to withdraw. Withdraw is bad, because there's no ability to naked short, derivative-ize, or control a comtmodity that buyers actually USE off-exchange. So they had to delist.e rules against/about naked shorting, lending, derivatives, listing, and even marketing/IPOing commodities AND securities. The law in the USA (typically strongest in Delaware where all the legal precedent concentrated) is quite detailed in the courts, and these offshorxe formerly-pirate exchanges know this, but they know they need to crack the USA if they're to have inter-exchange volumes which don't require sending all their trade information to Binance (because God knows, Binance isn't exactly the offshore model of clean trading-- as anyone following legal trends in the USA can tell you-- despite the strange WLF-linked pardons... errr... I mean DEALS being made wrt stablecoins and celebrity shitcoins with $ladies names on them. Homework: Go look up the month and year that OKX delisted Bitcoin (BSV), and then look up the month and year they announced turned their greedy eyes on offering their exchange to USA marks (I mean customers). It's a common well-beaten path. Even Robinhood had to give up, when they realized all BSV buyers were going to withdraw. Withdraw is bad, because there's no ability to naked short, derivative-ize, or control a comtmodity that buyers actually USE off-exchange. So they had to delist. The next thing you should be asking for, is HTX to delist Bitcoin; that is, if you want price discovery in an orderly fair market. That's something every enterprise, Government, and small business/startup developer should want. NumberGoUp is good for raising money, no doubt, but endless price suppression by competitors backed by billions of feathery tethery funny-money is NOT good for anything. It's not good for Bitcoin token/SINC owner substrates, nor startup financiers, nor anyone with small casual wallets with value in them. Nobody want's the $100 of digital spending money to turn into $2.54 worth of buying power-- the price of devs, servers, and software development (costs/expenses of building services) is quite steady, after all. If you obtain your Bitcoin (BSV) from HTX or other offshore fake-volume "exchanges", it's the equivalent of buying your bombs from the country you're at war with. Sure they'll make you think their loaded, but don't expect the explosion to happen at the time you wish. This message is not financed by @orangegateway, but perhaps it should be, as they are the only place I could recommend devs and Bitcoin users obtain (or cash-out of) the Bitcoin they need. No fake volume numbers given there, but they're likely the #1 place of liquidity, no matter how small it may seem. Send a bitcoin-penny to $JOHNPITTS HandCash with a future topic in the message line if you want to influence the subject matter of the next Bitcoiny article. paymail: johnpitts@handcash.io Legacy: 13DUeYZvt6dH2ca64JAAjrCbP84uMzd1nr

You must learn this rn! - spv - runar - brc100 - did - mcp - bhs - arc/arcade - utxo chaining - statelessness - overlay - paymail

4. Overlay / application integration layer ◦ paymail, identity, tokens, discovery, notifications, transaction history, app permissions, and any higher-level services the wallet needs to talk to. We need this NOW. imho 😁

Yes, the Relysia wallet is still fully active and operational in 2026 — it remains one of the most popular and feature-rich wallets dedicated to Bitcoin SV (BSV).Current status (March 2026): Official website: relysia.com — fully functional, login works normally, all services are available. Mobile app (Relysia Wallet) — available on iOS and Android, regularly updated (last major update in January 2026 added new STAS features, Paymail integration, and improved Metanet support). Supported BSV features: micropayments, STAS tokens, NFTs, Metanet, OP_RETURN, extremely low fees, easy send/receive via Paymail. The BSV community still strongly recommends it as one of the top 3 daily-use wallets (alongside HandCash If something isn’t working for you: Possible reasons: regional KYC/AML restrictions (Relysia requires verification in some countries), temporary maintenance, login error, outdated app version. Fix: update the app, try password reset, log in from a different device or VPN. If the issue persists — contact Relysia support directly (support@relysia.com or @RelysiaApp on X).Alternatives (if Relysia is temporarily giving trouble): HandCash — most popular, super simple, Paymail, perfect for daily payments. Twetch — excellent for social wallet, very active in the BSV community. ElectrumSV — desktop wallet, full key control, highest security level. Exodus (with BSV plugin) — multi-coin, user-friendly, nice interface. In any case — withdraw your real BSV from CEXs ASAP, regardless of which wallet you use. The warning still stands!

I was a big fan of @Rockwallet when it 1st came out. It seems that you have some different approaches. RW had a BSV Paymail. It seems @RampNetwork has a Network mail that can work with ALL of your listed cryptos? Do I have that right? That's impressive. Where do i find more details? Setting up an account today to start reviewing. Are there any other specific highlights I should look at? That you feel set you apart, or that need to spotlighted in a review? Again - very excited to welcome you to the BSV Community. Thank you providing us with another set of Ramps! 🙏

@RockWallet puts you in control. Self-custody, fast swaps and #BSV Paymail simplicity all in one! #RockWallet #CryptoFreedom

$BSV Giveaway time🤑 - RT post, follow @lilbitgame - Drop $paymail in comments - Winners selected in 48h! MANS NOT HOT 🥵

🧻 PAPER HANDS is LIVE Learn to spot rug pulls before they wreck you Built on BSV - real sats, real lessons, pennies at risk Looking for 5 beta testers - I'll send you $2 in sats to play Requirements: • Have a HandCash wallet • 10 min to test trades • Share honest feedback Drop your $ handle below 👇 Then reply to yourself with: (Powered by @HandCashApp ⚡$paymail)

Paymail @BLUVNBU

LEGACY — SLOW PEER -> MINER -> PEER PAYMAIL — INSTANT PEER -> SERVER -> SERVER -> PEER SPV — INSTANT PEER -> PEER

LET THEM KEEP ON THEIR SELF DOOM WITH SENCORING & LAUCHING THE SLAVE VERSIONS Digital ID! Humanity is Migrating ! 😃📢 With BSV identity systems (like Paymail, Tokenized IDs, and BRC Web3 identity tools): You own your identity. You control what you share. You can revoke access anytime. This flips the model. Instead of “Google or Facebook owns your login,” you own your identity on-chain.

With BSV identity systems (like Paymail, Tokenized IDs, and BRC Web3 identity tools): You own your identity. You control what you share. You can revoke access anytime. This flips the model. Instead of “Google or Facebook owns your login,” you own your identity on-chain.