#Wallets

Matching address prefixes and suffixes do not establish the recipient. Obtain a full address through a verified channel, compare the pasted result, and distinguish recipient identity from device transaction confirmation.

Check the destination asset, route, costs and completion conditions before moving funds across networks. Matching token names alone is insufficient.

Separate a device-native backup check from a rehearsal using an independent empty wallet, with clear preparation, stopping points and completion checks.

Audit the account, network, token and spender, remove unnecessary allowances, and verify the result instead of treating a disconnected website as a completed cleanup.

A lower balance does not prove the recipient was credited. Check the transaction ID, network status and receiving platform requirements before sending again.

Bitcoin Optech #429 highlights a proposed way for multiple signers to construct Silent Payments and verify their contributions. The design remains research, with an important security assumption unresolved.

Lichen is a research design for a single-issuer layer 2 that aims to let users recover bitcoin through an onchain dispute process when the issuer will not cooperate. Users and the issuer lock funds separately, with redemption rights subject to an agreed capacity. Tokens above that limit still require the issuer's cooperation.

The design continues to depend on the sequencer recording state correctly; malicious sequencing can cause losses. The newsletter also covers a proposal to store known hash preimages in output descriptors. These secrets should be backed up and protected like keys, and excluded from public descriptors.

This issue covers two older Eclair denial-of-service vulnerabilities in feature-bit parsing and gossip-message decompression, where small requests could consume excessive resources. The newsletter says versions through v0.13.1 were affected and fixes shipped in May with v0.14.0. October is the disclosure date.

Another proposal would let wallets sharing a descriptor synchronize encrypted labels through an untrusted store, reducing manual export and import. It builds on BIP329 records and addresses conflicts and deletion markers. Standardization was still under discussion.

Wallet security involves everyday use, backups and asset storage. The source recommends separating small amounts for daily spending from longer-term holdings, choosing online services carefully, and checking that backups cover everything needed to recover funds. A single backup can fail if a device breaks or something happens to the place where it is stored.

The guide covers wallet encryption, offline signing, hardware wallets and multisignature arrangements. These tools address different problems: encryption does not replace backups or eliminate malware threats.

A Bitcoin address does not display a name, but its transaction amounts, flows and balance can be inspected publicly. Once an address is linked to purchases, public posts or other identifying information, earlier and later transactions may become traceable. Using a pseudonymous address therefore does not make transactions inherently anonymous.

The source explains how reusing receiving addresses, posting addresses publicly and sharing transaction details can make information easier to connect. It also discusses fresh addresses and wallets for different purposes. These practices can reduce unnecessary exposure but cannot guarantee that activity is untraceable.

An Ethereum wallet is a tool for interacting with an account: viewing assets, sending transactions and connecting to applications. An address can be shared to receive funds, while a private key authorizes transactions and must remain secret. Distinguishing wallets, accounts, addresses and keys helps separate deleting an app from losing control of an account.

The source compares hardware, mobile, browser and desktop wallets, and explains how self-custody differs from exchange custody. Wallets that support recovery phrases require those phrases to be kept safe. Changing devices does not necessarily mean losing assets, but recovery depends on still having the necessary keys or recovery information.

Bitcoin.org organizes getting started into four steps: understanding the basics, choosing a wallet, obtaining bitcoin and making payments. Wallets can run on a phone or computer. Bitcoin can be obtained by accepting it for goods and services, or by buying it from other people or exchange services, then spent with merchants that accept it.

For merchants, the page describes handling payments and invoices directly or using a merchant service, with the option to keep bitcoin or local currency. It also covers accounting, tax and merchant directories, noting that tax treatment depends on local rules. This is an overview of spending and receiving payments, with links to more detailed resources for each step.