Bitcoin Ecosystem News

November 21, 2026


1. UniSat Wallet extension updated to 1.8.4; users who installed it manually need to check their version

Popularity: ★★☆☆☆


The @unisat_wallet Chrome extension has been updated to 1.8.4. The Chrome Web Store lists November 19 as the update date. Extensions installed from the Chrome Web Store usually update automatically; manually installed packages do not. Open “Manage extensions” to check which version you’re using. The store does not list specific changes in this release, so it’s not yet possible to determine what new features, if any, were added.


2. Bisq users must upgrade to continue trading; USD markets add 18 stablecoin payment options

Popularity: ★★★☆☆


@bisq_network released 1.10.12, and users on older versions must upgrade to continue trading. The new version supports buying BTC with stablecoins in USD markets: the 18 options refer to combinations of currency and network, and trades have a 24-hour time limit. When accepting a trade, don’t just check whether the currency is USDT or USDC—also check which network the other party will use.


3. Bitcoin Core fixes node stalls; users on 29.x shouldn’t wait for a patch

Popularity: ★★★☆☆


If you run a full node, check your version: versions 29.0–29.5, 30.0–30.4, and 31.0–31.2 may temporarily stop processing blocks and transactions. Fixes are included in 30.5, 31.3, and 32.1; 29.x is no longer maintained, so move to a branch that includes the fix. You need to upgrade the node software; there’s no need to move your Bitcoin to another address.


4. LNbits discloses a risk involving sats-claim QR codes; advisory lists no fixed version

Popularity: ★★☆☆☆


LNbits maintainer @motorina0 (GitHub) disclosed that versions 1.6.2-rc1 and earlier are affected. If you’re still logged into your wallet in a browser, opening a malicious payment-claim link or scanning its QR code could let someone use your login session to view wallet records or create API keys. The advisory still lists the fixed version as None. If you use a wallet hosted by someone else, confirm the version with the operator first, and don’t scan unfamiliar payment-claim codes.


5. EXILE engraving transaction records 21 million premined units, with no public mint parameters

Popularity: ★☆☆☆☆


According to Written in Bitcoin’s decoding of the transaction in block 976710, EXILE’s Rune ID is 976710:2389. The transaction records 21 million premined units, with no public minting parameters. The page also notes that it has not verified whether the name commitment is valid or whether the name is available. If you see a mint page with the same name, don’t pay a miner fee based on this transaction record.


6. BitBox updates its passphrase instructions; check your wallet fingerprint before receiving funds

Popularity: ★★☆☆☆


BitBox has updated its instructions: with BitBoxApp 4.53.0 or later and device firmware 9.28.0 or later, you can enter an optional passphrase in the app after authorizing it on the device. Entering the wrong passphrase may still open another valid wallet, so check the root fingerprint before receiving funds. The device unlock password must still be entered on the hardware device; do not enter your recovery words in the app.


7. NodeGuard adds a Spark wallet page; viewing details and withdrawing everything are separate actions

Popularity: ★☆☆☆☆


@Jossec101 (GitHub) released NodeGuard 0.35.1. Operators using remote signers can go to Wallets → Spark to view the corresponding wallet and its details. The page also adds Withdraw all, meaning a full withdrawal. If you only want to check the wallet, just open its details.


───


If you’ve installed UniSat, first check whether you installed it from the store or loaded it manually—the update methods differ.

Bisq users: check one more thing before accepting a trade—the payment network. And if you’re watching the Rune mint, don’t rush: this EXILE transaction did not leave any minting allocation open to the public.


#Bitcoin #Ordinals #Runes #BRC20 #Alkanes