USDT on Bitcoin is coming to MASKED.
private. native. no bridge.
we're testing it on Signet right now.
want in first?
1. install MASKED
2. tap Shielded -> Receive
3. reply with your sp1 address 👇
first 100 get the beta before anyone else.
no airdrop. just first access.
posting your Shielded address is safe. that's the whole point. 🎭
https://t.co/ysCSvChQHh
Lightning in. Silent out. 🎭
Soon in MASKED: get paid from any Lightning wallet, and it lands in your Shielded balance as a silent payment on Bitcoin.
The payer doesn’t need MASKED.
Nobody can link it to you.
Your keys, no custody.
Follow so you don’t miss the drop 👇
sp1 (BIP 352): payments are normal Bitcoin transactions, valid by Bitcoin itself. No indexer is needed, and only your wallet knows they’re yours. Amounts are visible.
shord1 (SHORD): a metaprotocol like Ordinals and BRC-20. Bitcoin carries the data, but who owns what is decided by SHORD indexers checking ZK proofs, not by Bitcoin consensus. It hides NFT ownership, not BTC amounts.
USDT on Bitcoin is coming to MASKED.
private. native. no bridge.
we're testing it on Signet right now.
want in first?
1. install MASKED
2. tap Shielded -> Receive
3. reply with your sp1 address 👇
first 100 get the beta before anyone else.
no airdrop. just first access.
posting your Shielded address is safe. that's the whole point. 🎭
https://t.co/ysCSvChQHh
Good question they’re two different things:
sp1… is a Silent Payments address (BIP 352). It’s live on Bitcoin today. You share one address, every payment lands on a fresh one-time address, and nobody can link those payments to you. Amounts are still visible on-chain. This is what MASKED uses; we just call that balance “Shielded”.
shord… is from the new Shielded Bitcoin proposal ([alloc] init, Sept 2026). It’s Zcash style, with encrypted amounts and zero knowledge proofs checked by indexers. It’s still a proposal and not live yet.
Same word, different tech. MASKED = sp1 silent payments.
@boss_venture89@ratsonchain@chompzeth Chrome shows this because MASKED injects content.js and inpage.js on HTTP/HTTPS sites to expose its wallet provider for dApp connections. Those broad match patterns trigger the warning. It describes granted access
🎭 What’s next for MASKED?
We’re building RGB asset support with the @utexocom Web SDK inside the wallet you already know
🔸 RGB assets alongside your Public and Shielded BTC balances
🔸 Send and receive through familiar wallet screens
🔸 Encrypted RGB backups and recovery
🔸 Your keys stay on your device
Development starts on Utexo Signet with test assets
Mainnet and USDT support are future goals, pending integration and testing.
Follow the build 👇
https://t.co/ayGPKpLfYu
#Bitcoin #RGB #MASKED
@posetcibasi that’s the idea your Public side still works like any bitcoin wallet for marketplaces, but anything you mint or receive on the Shielded side lands on a fresh address nobody can tie back to you
every time you mint a BRC-20, the bots see it
they copy your mints. they track your bags. they know when you sell
MASKED mints straight into a Shielded address
no wallet to follow. no history to scrape. the mint happens, nobody knows it was you
your bags. unseen 🎭
https://t.co/ysCSvChQHh