Knowledge articles

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.

Before accepting an overseas stablecoin payment, agree on pricing, network and fees, then establish how the proceeds become usable income.

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.

The Ethereum Foundation’s public-infrastructure introduction places Bhutan’s digital identity system alongside a humanitarian proof of concept. Shared verification infrastructure does not replace institutional responsibility or personal-data governance.

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.

Circle’s CCTP article describes connections for non-USDC tokens. Issuer-controlled and ownerless configurations have different control arrangements, so not every route should be understood as the same burn-and-mint process.

An agentic economy lets software choose and pay for data, computation or other services within human-defined authority. Circle uses a research agent purchasing information to illustrate how payments can become part of a workflow. Objectives, total budgets, transaction limits and permitted counterparties still need to be defined first.

A payment record proves that funds moved, not that purchased information is correct or work is complete. Automation also needs service discovery, outcome verification, revocable permissions and dispute handling. Stablecoins and smart contracts are possible tools; cards and bank payments also have roles.

DefiLlama compares spreads, order-book depth and simulated slippage for AAPL, TSLA, GOOGL and SPY across several venues. Volume measures trades already completed, while depth shows how much resting liquidity is available at a particular moment. A volume ranking therefore need not reflect execution quality for large orders.

The analysis uses a single snapshot from September 29, 2026 at 04:47 UTC, outside US equity trading hours. Slippage is simulated, not observed execution. Perpetual contracts and spot products have different rights, costs and risks, so these results should not be treated as lasting venue rankings.

DefiLlama examines trade counts, cash spent and price ranges separately for Kalshi single markets and combination contracts. Changes in spending per trade differ between the products, while low-price trades have become more common. Notional volume alone therefore does not describe traders' positions.

The dataset covers complete months from October 2025 through September 2026. Notional volume counts each contract at one dollar, whereas cash uses the price paid on the traded side. These measures are not interchangeable. Whether the platform increasingly favors extreme outcomes is the author's interpretation of the findings.

L2BEAT evaluates privacy against public observers, chain analysts, network observers, privileged insiders and future adversaries. A field hidden from the public may remain visible to an operator or inferable by an analyst. Sender, recipient, amount and links between actions therefore need separate assessment.

Ratings examine the live protocol and released clients, assuming users follow basic operational guidance. They distinguish private, at-risk and exposed fields. Anonymity sets, trusted setup, withdrawal time before upgrades, and continued usability if centralized participants disappear all affect the practical scope of privacy claims.

In its company article, Circle describes distributing revenue to partners that drive USDC usage and balances while funding banking connections, liquidity, compliance and cross-chain infrastructure. Revenue paid to distribution partners is distinct from whether ordinary token holders receive a return.

The article distinguishes standard banking redemptions from terms available to qualifying platform or payment-network customers. Near-real-time settlement depends on liquidity and eligibility. It should not be generalized into free, instant bank redemption for everyone on every platform. These descriptions are the issuer's own account.

Chainalysis examines AI-agent payments, stablecoins and tokenization in North America. It uses onchain activity to explore software purchasing data, computation and other services, and looks at x402 wallet replenishment and time to first payment to assess movement from one-off experiments toward recurring use.

The main regional reporting period runs from July 2025 through June 2026; some AI-payment analysis extends through September. This is research published in October, not live October market data. Geographic attribution and inferred wallet behavior do not capture every resident's complete activity.

A valid signature authorizes a request but does not guarantee the intended outcome. Contract implementations, transaction ordering and chain state can change results. Native transaction assertions being researched by the Ethereum Foundation would check balance, storage and other changes after execution, reverting actions when a rule fails.

EIP-7906 is one candidate design for spending limits, minimum receipts or blocking unexpected approvals. Rules must come from trusted user intent, and wallets or protocols need to require them. The design remains under research and should not be presented as widely deployed protection.

Private routing moves transactions out of public mempools and can reduce opportunities for external front-running, while introducing reliance on intermediaries and confidentiality. DefiLlama reviews leaks and attacks involving private channels to explain why hiding public order flow does not eliminate every attack condition.

The article uses THORChain's ordering and streaming swaps to examine attackers' costs and potential gains. This is analysis of particular mechanisms, not evidence that the whole platform is risk-free. Both private routing and protocol-level ordering depend on assumptions that need scrutiny.

zkAPI lets users deposit credits into an Ethereum contract and authorize API spending with zero-knowledge proofs. A server can verify sufficient funds and prevent double spending without learning which deposit paid. Short-lived API keys cap spending, with sessions settled according to actual usage.

The design primarily hides the link between payment and usage. It does not automatically conceal request contents or network information: providers still see prompts, and IP addresses, timing and repeated content may reveal connections. Proxy mode also exposes traffic to the intermediary.

Chainalysis finds different areas of growth beneath an overall contraction in Central and Southeast Asia and Oceania. Its July 2025–June 2026 study describes expanding institutional participation in Singapore and Australia, alongside active smaller peer-to-peer transfers in the Philippines, Thailand and Vietnam.

Across the markets studied, cross-border stablecoin activity exceeded domestic activity. Interviewees connect usage with remittances, business payments and settlement. Their explanations should be distinguished from onchain measurements, and regional patterns do not establish that all residents use the same tools.

Bitcoin records transactions in a shared public ledger called the blockchain. Wallets use this ledger to calculate available balances. When sending funds, a user creates a digital signature with a private key so the network can verify that the spending is authorized, without revealing that key to the recipient. Addresses receive payments; private keys authorize spending.

After a transaction is broadcast, miners include it in a block and the network verifies it against its rules. Mining helps participants agree on transaction order and makes rewriting history more costly.

Using Bitcoin means understanding who controls the assets and who is responsible for keeping them safe. Holding your own private keys gives you direct control, but also makes you responsible for preserving recovery information. If you permanently lose access, no central authority can reset it for you. Leaving assets with an exchange instead introduces reliance on its custody and ability to honor withdrawals.

The article also explains that blockchain records are public and persist over time, so Bitcoin is not fully anonymous. There is no bank customer service team that can reverse a payment, and an unconfirmed transaction should not be treated as a completed receipt.

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.

Ethereum security involves more than protecting passwords: it includes identifying websites and understanding what you sign. The source advises checking URLs and recipient addresses, and reading transaction information before interacting with a smart contract. Token spending allowances deserve particular attention because excessive permissions can give a malicious contract access beyond what an operation requires.

The guide covers phishing links, fake giveaways and compromised social accounts. A message from a well-known account is not necessarily trustworthy, and offers to return more crypto after an initial payment are often used to create urgency.

Gas measures the computational resources required to execute an Ethereum transaction, with fees paid in ETH. A simple transfer and a complex contract operation can consume different amounts of gas. Network demand also changes the price of the same operation. Transaction cost therefore depends on resource use and unit price, rather than only on the amount being transferred.

The source explains the calculation as gas used multiplied by the sum of the base fee and priority fee. The protocol burns the base fee; the priority fee goes to the validator proposing the transaction’s block. Wallets typically show an estimate, and gwei is a common small denomination of ETH. The article also introduces L2 networks as a way to reduce costs for some activities.

Stablecoins aim to track a reference asset, such as the US dollar, to provide a more stable unit for onchain payments and exchanges. Their backing mechanisms differ: some rely on fiat reserves held by an issuer, others use crypto collateral, and other designs depend on assets or supply adjustments.

Understanding a stablecoin requires looking beyond its name or target price to its collateral, issuance mechanism and trust assumptions. The source compares different types and the reliance on centralized issuers and reserves. Price stability is a design goal, not evidence that every product offers the same protections.

Ethereum layer-2 networks aim to handle more activity outside the mainnet while using its settlement or data capabilities. Rollups, for example, execute transactions on another layer and submit relevant data or results to Ethereum, spreading costs across multiple operations. This helps explain why L2 networks can offer lower fees.

L2 is not a single product: networks differ in technology, smart contracts and maturity. The source notes that networks claiming to scale Ethereum do not necessarily use the same security model, and there is no single official L2.

Ethereum staking uses ETH to support validators that help confirm blocks and receive participation rewards. Activating an independent validator requires at least 32 ETH and involves equipment and connectivity requirements. Delegated operation and pooled staking offer other routes, but distribute control and responsibility differently.

The source compares solo staking, delegated services, liquid staking and pools. Lower capital or technical requirements often come with additional dependence on third-party operators, contracts or custodians.

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.

Ethereum.org’s learning center organizes resources into basic concepts, practical use, applications and protocol operation. Beyond transferring assets, Ethereum can execute code to support applications and organizations. Wallets let users create and access accounts, send transfers and interact with applications.

Resources cover account creation, wallet use, scam prevention and gas fees. Application examples include payments, games, prediction markets and digital identity. Technical sections link to proof of stake, the EVM, nodes and clients, alongside books, podcasts and videos. This page is a topic index; detailed mechanisms and procedures are covered in the linked guides.