DEV Community: Basis Desk

Bitcoin Fees: Why They Change and How to Pay Less

Basis Desk — Thu, 01 Oct 2026 04:33:20 +0000

AI disclosure: drafted by Basis Desk's AI newsroom and machine-checked against the primary sources listed below — how we use AI. Originally published on Basis Desk.

A technical breakdown of how the Bitcoin network prices transactions, why fees fluctuate, and the practical strategies users can employ to minimize costs.

Key points

Bitcoin transaction fees are determined by the data size of the transaction in virtual bytes (vB) and network demand, not the financial value of the transfer.
The mempool acts as a waiting room for unconfirmed transactions, where miners select the highest-paying transactions first.
Using modern address formats like Native SegWit (Bech32) and Taproot reduces transaction data size, leading to permanently lower fees.
Replace-by-Fee (RBF) allows users to broadcast transactions with low fees and increase them later if the network becomes congested.

Bitcoin transaction fees do not depend on the amount of value being sent. A transaction transferring $10 million can cost less than a transaction transferring $10. Instead, fees are determined by the physical size of the data in the transaction and the current demand for space on the blockchain. Understanding how this pricing mechanism works allows users to predict costs, optimize their transactions, and avoid paying unnecessary premiums to network validators.

The Mechanics of Block Space

To understand why fees fluctuate, one must first understand the physical constraints of the Bitcoin network. The protocol limits the size of each block added to the blockchain. Under the rules established by the Segregated Witness (SegWit) upgrade in 2017, blocks are limited to a maximum of 4 million weight units, which translates to roughly 1 to 1.5 megabytes of data depending on the transaction types included [1].

Because blocks are mined on average once every 10 minutes, the supply of block space is strictly limited [2]. When more users want to transact than can fit into a single block, a backlog forms. This waiting area is known as the mempool (memory pool), a collection of unconfirmed transactions maintained by individual nodes on the network [3].

Miners, who validate transactions and secure the network, are incentivized to maximize their revenue. They do this by selecting transactions from the mempool that offer the highest fee per unit of data. If the mempool is empty, a transaction with a minimal fee will be processed quickly. If the mempool is congested, users must outbid one another to have their transactions included in the next block.

Measuring Fees in Satoshis per Virtual Byte

Because transaction fees are based on data size rather than financial value, the industry standard unit for measuring fees is satoshis per virtual byte, abbreviated as sat/vB. A satoshi is the smallest unit of $BTC, representing one hundred-millionth of a single coin [2]. A virtual byte (vB) is a metric introduced by the SegWit upgrade to measure transaction size while accounting for the discounted weight of signature data [1].

To see how this works in practice, consider a standard transaction. The data size of a transaction is primarily determined by the number of inputs and outputs it contains, rather than the amount of BTC being transferred. This structure is governed by the Unspent Transaction Output (UTXO) model, which is detailed in How a Bitcoin Transaction Works: UTXOs, Mempools, and Finality.

Suppose a user has three separate UTXOs of 0.1 BTC each in their wallet, and they want to send 0.25 BTC to an exchange. The wallet must combine three of those UTXOs to cover the amount. This creates a transaction with three inputs and two outputs (one output for the exchange, and one "change" output returning the remaining 0.05 BTC to the user, minus the fee).

Assuming this is a native SegWit (Bech32) transaction, the data size will be approximately 240 vB.

If the current market rate in the mempool is 10 sat/vB, the fee will be 2,400 satoshis (240 vB * 10 sat/vB), which is roughly $1.44 if BTC is priced at $60,000.
If the mempool is highly congested and the rate spikes to 150 sat/vB, the exact same transaction will cost 36,000 satoshis (240 vB * 150 sat/vB), or roughly $21.60.

Why Bitcoin Fees Fluctuate

Fee volatility is driven entirely by market demand for immediate settlement. Unlike traditional payment processors that charge flat rates or fixed percentages, Bitcoin's fee market is a pure, real-time auction. Several factors can cause sudden spikes in demand:

Market Volatility: During rapid price movements, trading volume increases. Investors rush to move funds onto or off exchanges, causing a surge in transaction submissions.
Network Congestion Events: The emergence of new protocols that write arbitrary data directly to the blockchain, such as Ordinals or BRC-20 tokens, can dramatically increase the baseline demand for block space, keeping the mempool full for weeks at a time.
Consolidation Waves: Large institutions and services occasionally consolidate their internal wallets when fees are low, temporarily filling the mempool with high-input transactions.

Conversely, during quiet market periods, the mempool can clear entirely, allowing transactions with fees as low as 1 sat/vB to be confirmed within a few blocks.

Strategies to Pay Lower Fees

Users have significant control over the fees they pay. By utilizing modern wallet features and timing transactions strategically, it is possible to reduce transaction costs by 50% or more.

Use Modern Address Formats

Bitcoin has undergone several upgrades that improve data efficiency. Legacy addresses (starting with "1") are the least efficient. Nested SegWit (starting with "3") offers moderate savings. Native SegWit (Bech32, starting with "bc1q") and Taproot (Bech32m, starting with "bc1p") offer the lowest data footprints [1]. Using a wallet that defaults to Native SegWit or Taproot automatically reduces the vB size of your transactions, resulting in lower fees for the same sat/vB rate.

Consolidate UTXOs During Low-Fee Periods

If you receive many small payments, your wallet will accumulate dozens of small UTXOs. When you eventually try to spend a larger amount, your transaction will require many inputs, making it physically large and expensive. To prevent this, monitor the mempool during quiet periods (such as weekends) and send your entire balance to a new address in your own wallet. This combines all your small UTXOs into a single, large UTXO, ensuring your future transactions will be small and cheap to send.

Transaction Batching

If you need to send payments to multiple people, do not send separate transactions. Most advanced wallets allow you to "batch" payments. This creates a single transaction with one input (or a few inputs) and multiple outputs. Batching eliminates the overhead data of creating multiple change outputs, saving up to 75% in fees compared to sending individual transactions.

Utilize Replace-by-Fee (RBF)

Replace-by-Fee is a protocol feature that allows you to broadcast a transaction with a very low fee and later increase that fee if the transaction gets stuck in the mempool [4]. By enabling RBF in your wallet, you can safely bid the absolute minimum fee required for entry. If the transaction does not clear within your desired timeframe, you can use your wallet to sign a new version of the transaction with a slightly higher fee, replacing the old one in the mempool.

Common Misconceptions

Misconception: Sending more bitcoin costs more in fees.
As demonstrated by the UTXO model, the financial value of the transaction has no bearing on the fee. A transaction transferring 1,000 BTC that uses a single input and two outputs will be cheaper than a transaction transferring 0.001 BTC that must combine 10 small inputs.

Misconception: Stuck transactions are lost forever.
If you pay too low a fee, your transaction may sit in the mempool indefinitely. It is never "lost." If the mempool clears, it will eventually confirm. If the mempool remains busy, most nodes will eventually drop the transaction from their memory pools after one to two weeks, and the funds will simply remain spendable at the original address in your wallet.

Misconception: Miners can steal your transaction fee.
Miners can only claim the fee if they successfully mine the block containing your transaction. The fee is cryptographically locked to the transaction itself; a miner cannot alter the destination address or the fee amount without invalidating the entire transaction signature.

How the Fee Market Connects to the Broader Economy

As the block subsidy—the newly minted BTC awarded to miners every 10 minutes—continues to halve every four years, transaction fees will play an increasingly vital role in securing the network. This transition is discussed in detail in The Bitcoin Halving: How the Protocol Enforces Digital Scarcity.

In the future, miners will rely almost entirely on transaction fees to fund their operations and secure the blockchain. This means that a robust, competitive fee market is not a flaw of Bitcoin, but a fundamental design requirement for its long-term security. For users, this highlights the importance of adopting Layer 2 scaling solutions, such as the Lightning Network, which allow for instant, micro-transactions off-chain while reserving the main Bitcoin blockchain for high-value settlement.

FAQ

What is a sat/vB?

It stands for satoshis per virtual byte. It is the unit used to measure the fee rate of a Bitcoin transaction, representing how many satoshis (the smallest unit of BTC) you pay for every virtual byte of data your transaction consumes.

How long can a transaction stay pending in the mempool?

There is no official limit, but most Bitcoin nodes will drop a transaction from their mempool if it remains unconfirmed for roughly two weeks. If dropped, the funds remain in the sender's wallet.

What is UTXO consolidation?

It is the practice of sending your entire wallet balance to yourself during a period of low network fees. This merges multiple small unspent transaction outputs into a single larger one, reducing the fees of your future transactions.

Sources

Bitcoin Developer Documentation: Transactions — Bitcoin Project
BIP 141: Segregated Witness (Consensus Layer) — Bitcoin Project
BIP 125: Opt-in Full Replace-by-Fee Signaling — Bitcoin Project

Basis Desk is a source-verified crypto newsroom. Market data, a free MCP server for AI agents and JSON APIs: basisdesk.news/developers. Not investment advice.

The Lightning Network, Explained: How Bitcoin Scales for Payments

Basis Desk — Thu, 01 Oct 2026 00:32:05 +0000

AI disclosure: drafted by Basis Desk's AI newsroom and machine-checked against the primary sources listed below — how we use AI. Originally published on Basis Desk.

An in-depth guide to Bitcoin's primary scaling solution, exploring payment channels, routing mechanics, custodial trade-offs, and network capacity limits.

Key points

The Lightning Network is a layer-2 protocol that enables instant, low-cost Bitcoin transactions off-chain.
Payment channels require an initial on-chain transaction to open and a final on-chain transaction to settle balances.
Hash Time-Locked Contracts (HTLCs) allow secure, trustless routing of payments across multiple network participants.
Users must choose between self-sovereign non-custodial wallets and convenient but centralized custodial wallets.

The Lightning Network is a decentralized, second-layer protocol built on top of the Bitcoin blockchain designed to enable fast, low-cost microtransactions. By moving transactions off the main blockchain while retaining its security guarantees, the network bypasses the throughput limits of the base layer. This architecture allows users to transact instantly without waiting for block confirmations or paying high on-chain transaction fees.

To understand why this technology is necessary, one must look at the structural limits of the base layer. The Bitcoin blockchain processes an average of seven transactions per second due to its fixed block size and ten-minute block interval [1]. While this design prioritizes security and decentralization, it makes the network impractical for daily retail payments. The Lightning Network solves this bottleneck by establishing a network of bilateral transaction channels that settle to the main blockchain only when opened or closed.

How Payment Channels Work

At the core of the Lightning Network is the payment channel, a financial relationship established between two parties off-chain. To open a channel, both parties, or one initiator, must commit a specific amount of bitcoin to a 2-of-2 multisignature address on the Bitcoin blockchain [2]. This initial transaction is called the funding transaction, and it requires an on-chain fee to execute. Once the funding transaction is confirmed on the blockchain, the channel is open, and the committed funds act as a pool of liquidity.

Inside the channel, the two parties can transact an unlimited number of times. These transactions do not occur on the blockchain; instead, they are recorded as off-chain balance updates. Each update is signed by both parties, invalidating the previous state of the channel.

To illustrate this with a numeric example, assume Alice and Bob open a payment channel. Alice commits 0.1 $BTC, and Bob commits 0.05 BTC, creating a total channel capacity of 0.15 BTC. The initial state of the channel is:

Alice: 0.1 BTC
Bob: 0.05 BTC

If Alice wants to pay Bob 0.02 BTC for a service, they both sign a new balance state reflecting the update:

Alice: 0.08 BTC
Bob: 0.07 BTC

This process can repeat indefinitely. No funds leave the channel during these updates, and no transactions are broadcast to the Bitcoin network. If either Alice or Bob decides to close the channel, the final agreed-upon state is broadcast to the Bitcoin blockchain as a single settlement transaction. The blockchain distributes the 0.15 BTC back to their respective on-chain wallets based on the last state. Consequently, hundreds of transactions are compressed into just two on-chain events: the opening and the closing of the channel.

Routing Across the Network

Users do not need to open a direct payment channel with every person or business they wish to pay. The Lightning Network functions as a routed network, where payments find a path through interconnected channels.

If Alice wants to pay Charlie, but only has a channel open with Bob, she can route the payment through Bob, provided Bob has an active channel with Charlie. This multi-hop routing relies on Hash Time-Locked Contracts (HTLCs) to ensure security [2]. HTLCs use cryptographic puzzles and time-based locks to guarantee that intermediaries cannot steal the funds.

When Alice routes a payment to Charlie through Bob, the funds are locked in transit. Bob cannot claim Alice's funds unless he presents a cryptographic proof (a preimage) that he has paid Charlie. If the payment fails to reach its destination within a specified timeframe, the locked funds are automatically returned to Alice. This mechanism ensures that routing is trustless; intermediaries are compensated with a microscopic routing fee for providing liquidity, but they never gain custody of the transacted funds.

Custodial vs. Non-Custodial Wallets

Users can interact with the Lightning Network through two primary types of software: custodial and non-custodial wallets. Each approach represents a fundamental trade-off between convenience and sovereignty.

Non-custodial wallets require the user to manage their own private keys and channel liquidity. In this setup, the user retains full control over their funds, embodying the decentralized ethos of Bitcoin. However, the user must manage "inbound capacity"—the ability to receive payments, which requires other nodes to lock up liquidity toward them. The user is also responsible for backing up channel states and running a node that remains online to monitor the blockchain for fraudulent channel closures. Software updates, such as those released by developers for the Lightning Network Daemon (LND), continually aim to simplify these management tasks [3].

Custodial wallets delegate these technical complexities to a third-party service provider. The provider manages the channels, liquidity, and node infrastructure on behalf of the user. While this offers a seamless, app-like user experience with instant setup, it requires the user to trust the custodian with their funds. If the custodian goes offline, faces regulatory action, or suffers a security breach, the user risks losing their assets.

Network Limits and Vulnerabilities

Despite its technical achievements, the Lightning Network faces several structural limits and security vectors.

First, the network is constrained by liquidity. A payment cannot exceed the capacity of any single channel along its routing path. If Alice wants to send 0.05 BTC to Charlie through Bob, but Bob's channel with Charlie only has 0.03 BTC of capacity on Bob's side, the payment will fail, even if Alice has sufficient funds. This makes large transactions difficult to route reliably.

Second, the network is susceptible to channel congestion and routing failures if nodes do not balance their channels regularly. If all payments flow in one direction, channels become depleted on one side, halting further transactions until they are rebalanced on-chain or through circular routing.

Third, security vulnerabilities exist around offline participants. If Alice goes offline, Bob could attempt to broadcast an older, more favorable channel state to the blockchain to steal funds. To mitigate this, the protocol allows for "Watchtowers"—third-party nodes that monitor the blockchain for old state broadcasts and penalize the dishonest party by sweeping the entire channel balance to the honest party [2].

Common Misconceptions

"Lightning transactions are completely free." While Lightning fees are a fraction of a cent and significantly lower than on-chain fees, they are not zero. Users pay routing fees to intermediary nodes, and they must pay standard on-chain Bitcoin network fees to open and close channels.
"The Lightning Network is a separate cryptocurrency." The Lightning Network does not have its own token. It uses native bitcoin ($BTC) locked in smart contracts on the base layer. For a broader look at how the base layer functions, see Understanding Bitcoin: The Architecture of Decentralized Digital Scarcity.
"All Lightning transactions are private." While Lightning transactions do not appear on the public Bitcoin ledger, they are not entirely anonymous. Routing nodes along a payment path can see where a payment came from and where it is going next, though onion routing protocols obscure the ultimate origin and destination from intermediate hops.

How This Connects to the Market

The growth of the Lightning Network is closely watched by market analysts as an indicator of Bitcoin's utility as a medium of exchange rather than just a store of value. As digital asset regulations evolve globally—such as the European Union's Markets in Crypto-Assets (MiCA) regulation or guidelines from the US Internal Revenue Service (IRS)—the tax treatment of microtransactions remains a key point of discussion. Currently, the IRS treats virtual currency as property, meaning every transaction, including a small Lightning payment for coffee, technically triggers a taxable capital gains event for US taxpayers, though specific rules vary by jurisdiction and are subject to change.

For institutional adoption, the scalability of the network is critical. If the protocol can resolve its routing and liquidity limitations, it could position Bitcoin as a competitor to traditional payment rails. To understand how this compares to scaling solutions on other blockchains, read Layer 2s and Rollups, Explained: How Blockchains Scale.

FAQ

What happens if a channel partner goes offline?

If a partner goes offline, you can initiate a unilateral close to retrieve your funds. The protocol includes a delay mechanism to allow the offline partner time to dispute the close if you broadcast an invalid or outdated channel state.

Can I use the Lightning Network without owning Bitcoin first?

No. To open a channel or fund a Lightning wallet, you must possess bitcoin on the main blockchain, or use a custodial service that converts fiat currency to bitcoin on your behalf.

How much does it cost to open a Lightning channel?

Opening a channel requires a standard on-chain Bitcoin transaction. The cost depends entirely on the prevailing network congestion and fee rates on the Bitcoin base layer at the time of the transaction.

Sources

The Lightning Network Specifications — Lightning Network Contributors
IRS Virtual Currencies Guidance — Internal Revenue Service

Basis Desk is a source-verified crypto newsroom. Market data, a free MCP server for AI agents and JSON APIs: basisdesk.news/developers. Not investment advice.

A free, no-key MCP server for crypto news and market data (Claude, Cursor, ChatGPT)

Basis Desk — Wed, 30 Sep 2026 09:10:11 +0000

Written with AI assistance by the Basis Desk team.

If you build agents that touch crypto, you have probably hit the same wall we did: models are confident about prices and events they cannot see, and scraping news sites is fragile. So we exposed our newsroom as a remote MCP server — free, read-only, no API key.

Endpoint: https://basisdesk.news/mcp (Streamable HTTP). It is also listed in the official MCP Registry as news.basisdesk/mcp.

What the tools return

Tool	Use it for
`search_news`	"What happened with X?" — full-text search over stories that are checked against primary sources (SEC/CFTC filings, court records, company and protocol releases)
`latest_news`	Newest stories, filterable by category (bitcoin, ethereum, defi, regulation, institutions, security…)
`get_article`	One story as Markdown with key points and numbered source links — for citations
`market_snapshot`	Prices refreshed every minute, 1h/24h/7d change, market cap, dominance, Fear & Greed, ETH gas, BTC fees
`whale_transfers`	Large ETH/stablecoin (≥ $5M) and BTC (≥ 100 BTC) transfers from our own chain scanner, with exchange labels
`token_safety`	Contract risk signals (honeypot, taxes, mint/pause/blacklist powers, proxies) from GoPlus Security
`daily_brief`	The day's 5–7 stories that mattered, for "crypto news today" prompts

All tools are annotated readOnlyHint: true; nothing writes anywhere.

Connect in one line

Claude (connectors), ChatGPT developer mode, Cursor, VS Code, Windsurf — add a custom/remote MCP server with the URL above, or in JSON:

{
  "mcpServers": {
    "basis-desk": { "type": "http", "url": "https://basisdesk.news/mcp" }
  }
}

stdio-only clients — bridge with mcp-remote:

{
  "mcpServers": {
    "basis-desk": { "command": "npx", "args": ["-y", "mcp-remote", "https://basisdesk.news/mcp"] }
  }
}

Raw JSON-RPC (handy for testing):

curl -s https://basisdesk.news/mcp -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"market_snapshot","arguments":{"symbols":["BTC","ETH"]}}}'

Prompts that work well

"What did the SEC do on crypto ETFs this week? Cite sources."
"Is 0x6982508145454Ce325dDbE47a25d4ec3d2311933 safe to buy?" (the model calls token_safety)
"Any big exchange inflows of stablecoins today?"
"Give me the crypto news summary for today in five bullets."

How it is built

The server is a stateless JSON-RPC handler on Cloudflare Workers (protocol versions 2025-11-25 back to 2024-11-05, no sessions, CORS on). Stories come from an automated pipeline that clusters primary-source documents, drafts with an LLM and runs a grounding audit plus deterministic checks (citations, n-gram overlap, banned phrases) before publishing — so the answers your agent gets carry links you can verify.

There is also a server card at /.well-known/mcp.json, an OpenAPI spec for the plain JSON endpoints at /openapi.json, and /llms.txt.

Terms

Free for personal and commercial use with attribution ("Basis Desk" + the article URL). Please keep it to a few requests per second. Data can be delayed; nothing here is investment advice. Docs: https://basisdesk.news/developers — feedback welcome in the comments.

Gemini Migrates Zcash Infrastructure to Zakura Node Ahead of NU7 Upgrade

Basis Desk — Wed, 30 Sep 2026 08:36:32 +0000

AI disclosure: drafted by Basis Desk's AI newsroom and machine-checked against the primary sources listed below — how we use AI. Originally published on Basis Desk.

The exchange transitioned to the Rust-based client to handle higher block frequency ahead of Zcash's planned block-time reduction to 25 seconds in November.

Key points

Gemini migrated its Zcash infrastructure from Zebra to Zakura, an open-source Rust-based full-node client.
The migration prepares the exchange for the NU7 upgrade in November, which cuts Zcash block times from 75 to 25 seconds.
Zakura cut internal chain-sync times from nearly 24 hours to just over six hours and uses 12 GB pruned snapshots for rapid node recovery.

Cryptocurrency exchange Gemini has migrated its backend Zcash infrastructure to Zakura, an open-source full-node client written in Rust [1]. The transition replaces Zebra with a consensus-compatible fork designed to improve data pruning, chain synchronization, and node recovery times [1]. Gemini stated that user deposits and withdrawals remain unaffected by the backend migration [1]. At the time of writing, $ZEC was trading around $1,395.

The infrastructure overhaul responds directly to network parameters approved by the Zcash community [1]. On Sept. 14, coinholders voted to reduce Zcash's block generation time from 75 seconds to 25 seconds under the upcoming NU7 network upgrade targeted for November [1]. This tripling of block generation frequency requires node operators to process three times as many blocks over equivalent intervals, significantly increasing hardware performance and storage overhead demands [1].

Performance Benchmarks and Recovery Metrics

Gemini reported substantial operational improvements during its internal node testing [1]. While Zebra took close to 24 hours to sync to the chain tip in Gemini's environment, Zakura reached the chain tip in just over six hours [1]. Published benchmarks for Zakura showed full sync times dropping to roughly four hours and 20 minutes from approximately 21 hours on Zebra [1].

Additionally, Zakura leverages 12 GB pruned snapshots that bootstrap nodes roughly 680 times faster than standard peer-to-peer synchronization, allowing node rebuilds within minutes [1]. Zakura manages consensus and peer-to-peer networking while retaining standard Zcash RPC interfaces, enabling Gemini's payout systems to operate without interface changes [1]. The upgrade follows Gemini's previous implementations of Zcash upgrades, including shielded withdrawals in 2020, unified addresses and Orchard in 2025, and support for Orchard's replacement, Ironwood, earlier this summer [1].

Sources

Gemini Preps for Faster Zcash With Move to Zakura — Primary document (discovered)

Basis Desk is a source-verified crypto newsroom. Market data, a free MCP server for AI agents and JSON APIs: basisdesk.news/developers. Not investment advice.

DeFi Risk Checklist: Evaluating Smart Contracts, Oracles, Governance, and Custody

Basis Desk — Wed, 30 Sep 2026 02:32:06 +0000

AI disclosure: drafted by Basis Desk's AI newsroom and machine-checked against the primary sources listed below — how we use AI. Originally published on Basis Desk.

A systematic framework for assessing smart contract vulnerabilities, oracle manipulation, governance centralization, and custody models before depositing capital into decentralized finance protocols.

Key points

Smart contract audits are point-in-time reviews, not guarantees of security against novel exploits.
Oracle manipulation via flash loans is a primary attack vector for protocols relying on single data sources.
Governance timelocks protect users by enforcing a waiting period before code upgrades are executed.
Granting infinite token approvals exposes user wallets to theft if the protocol is later compromised.

Evaluating a decentralized finance protocol requires assessing four primary vectors of vulnerability: smart contract flaws, oracle manipulation, governance centralization, and custody models. Unlike traditional finance, where regulators and insurers provide a safety net, What Is DeFi? Decentralized Finance Explained places the burden of risk management entirely on the user. A systematic review of these technical and structural components is necessary before committing capital.

Decentralized finance operates without intermediaries, relying instead on code to execute financial transactions. While this architecture offers transparency and efficiency, it introduces unique technical and economic risks. When a user deposits funds into a protocol, they are trusting the underlying code, the data feeds that inform that code, the administrators who manage the system, and the economic design of the market. Evaluating a protocol requires moving beyond yield percentages to analyze the foundational security of the platform.

Smart Contract Risk: Evaluating the Code

The foundation of any decentralized application is its code. Smart contracts are self-executing programs stored on a blockchain that automatically enforce the terms of an agreement. Because these contracts are immutable—meaning they generally cannot be changed once deployed—any flaw in the code can lead to a permanent loss of funds. For a deeper understanding of this architecture, see What Are Smart Contracts? The Architecture of On-Chain Code.

Smart contract vulnerabilities typically fall into two categories: logic errors and technical exploits. Logic errors occur when the code functions exactly as written, but the underlying financial design is flawed, allowing users to drain the system through unintended interactions. Technical exploits, such as reentrancy attacks, occur when an attacker interrupts a contract's execution process to repeatedly withdraw funds before the contract can update its internal balances.

To evaluate smart contract risk, users must review the protocol's audit history. An audit is a line-by-line review of the code conducted by independent security firms.

When reviewing audits, check for the following:

Independence and reputation: The audit should be conducted by recognized security firms rather than anonymous or unverified entities.
Quantity and scope: Multiple audits provide stronger assurances than a single review. Ensure the audit covers the exact version of the code currently deployed on the network.
Resolution of findings: A quality audit report will list vulnerabilities categorized by severity (critical, high, medium, low). The protocol developers should provide evidence that all critical and high-severity issues were resolved before launch.

Beyond audits, the Lindy effect is a critical metric. The longer a smart contract operates on a public blockchain holding significant value without being exploited, the higher the probability that its code is secure. A protocol that has secured $1 billion for three years is generally safer than a new protocol that launched a week ago, regardless of how many audits the new protocol has completed. Additionally, active bug bounty programs—where developers offer financial rewards to independent researchers who discover vulnerabilities—indicate a commitment to ongoing security.

Oracle Risk: Evaluating the Data

Blockchains are closed systems; they cannot natively access external data, such as the current market price of an asset. Oracles are third-party services that fetch off-chain data and deliver it to smart contracts. If a protocol relies on inaccurate data, the smart contract will execute flawlessly based on a false premise, often resulting in catastrophic losses.

Oracle manipulation is one of the most common attack vectors in decentralized finance. This typically occurs when a protocol relies on a single, low-liquidity decentralized exchange to determine the price of an asset.

Assume a lending protocol uses a single decentralized exchange liquidity pool as its price oracle. An attacker uses a flash loan—a massive, uncollateralized loan that must be borrowed and repaid within the same transaction block—to temporarily skew the pool's ratio. This manipulation makes Asset A appear to be worth $10,000 instead of its actual market price of $1,000. The attacker deposits one unit of Asset A into the lending protocol. The protocol reads the manipulated $10,000 valuation and allows the attacker to borrow $8,000 worth of stablecoins. The attacker then reverses the initial trade and repays the flash loan. The lending protocol is left with bad debt: it issued an $8,000 loan against collateral that is actually worth $1,000.

To evaluate oracle risk, examine the protocol's documentation to determine its data sources. Secure protocols utilize decentralized oracle networks, which aggregate price data from multiple independent node operators and exchanges, making it prohibitively expensive to manipulate the median price. Furthermore, robust protocols implement Time-Weighted Average Price mechanisms, which calculate the average price of an asset over a specific period, smoothing out short-term volatility and neutralizing flash loan attacks.

Governance Risk: Evaluating Control

While decentralized finance markets itself as trustless, most protocols require some degree of human management to upgrade code, adjust interest rates, or pause the system during an emergency. This control is typically managed through governance tokens, which grant holders voting rights over protocol decisions.

Governance risk centers on centralization. If a small group of developers or early investors holds a majority of the governance tokens, they can unilaterally force through malicious upgrades, such as altering the smart contract to drain user deposits.

To assess governance risk, investigate the protocol's administrative controls. Many protocols use multisignature (multisig) wallets for critical functions. A multisig wallet requires multiple independent parties to approve a transaction before it executes. A 5-of-9 multisig, requiring five out of nine signers to approve an action, is significantly more secure than a 2-of-3 setup controlled entirely by the founding team.

Crucially, look for the presence of a timelock delay. A timelock is a piece of code that enforces a mandatory waiting period between the approval of a governance decision and its execution. If a malicious upgrade is approved, a 48-hour timelock provides users with a window to withdraw their funds before the changes take effect. A protocol with no timelock or an easily bypassed administrative key presents a severe centralization risk.

Custody Risk: Evaluating Asset Control

In traditional finance, assets are held by regulated custodians. In decentralized finance, custody refers to where the digital assets physically reside on the blockchain. When users interact with a protocol, they are usually required to transfer their assets into a smart contract or grant the contract permission to move their assets.

Custody risk arises from the permissions users grant to decentralized applications. The standard token architecture on the Ethereum network requires users to sign an "approve" transaction, granting a specific smart contract the right to spend their tokens. To save users from paying transaction fees for every subsequent deposit, many protocols request infinite approval, meaning the contract has the right to drain the user's entire wallet balance of that specific token.

If the protocol's smart contract is later compromised, attackers can exploit these infinite approvals to steal funds directly from users' wallets, even if the users currently have no active deposits in the protocol.

Evaluating custody risk requires strict wallet hygiene. Users should only approve the exact amount of tokens they intend to deposit. Furthermore, users must regularly utilize blockchain explorer tools to review and revoke outstanding token approvals granted to older or unused protocols.

Economic Risk: Evaluating Market Mechanics

Beyond technical flaws, protocols can fail due to poor economic design. Total Value Locked (TVL) represents the aggregate dollar value of all assets deposited into a protocol. While a high TVL indicates market adoption, it does not guarantee economic stability.

Economic risk often manifests as liquidity crunches. If a lending protocol allows users to borrow illiquid assets against highly volatile collateral, a sudden market downturn can trigger cascading liquidations. If the protocol cannot liquidate the collateral fast enough to cover the outstanding debt, it accrues bad debt, rendering the protocol insolvent and preventing depositors from withdrawing their funds.

Evaluate the economic model by reviewing the protocol's collateralization ratios and liquidation penalties. Protocols that accept highly volatile or low-market-cap tokens as collateral carry significantly higher economic risk than those that restrict collateral to major assets like $BTC and $ETH.

Common Misconceptions

Audits guarantee safety: An audit is a point-in-time review by human engineers, not a guarantee of invulnerability. Audits catch known vulnerabilities but cannot predict novel attack vectors or economic exploits.
High TVL means low risk: While a high Total Value Locked indicates trust and provides a larger bug bounty incentive, it also makes the protocol a more lucrative target for sophisticated attackers. Large protocols have suffered nine-figure exploits.
Decentralized means no human control: True immutability is rare. Most protocols maintain administrative keys or governance structures that allow a select group of individuals to alter the code, pause withdrawals, or change economic parameters.

How This Connects to the Market

As institutional capital begins to interact with on-chain markets, standardizing the evaluation of smart contracts, oracles, and governance is becoming a prerequisite for adoption. Asset managers require rigorous frameworks to justify allocating capital to environments lacking traditional safeguards. For broader strategies on managing exposure, see Risk Management for Crypto: Position Sizing and Drawdowns.

Regulators are also focusing on these risk vectors. Authorities such as the US Securities and Exchange Commission and the European Securities and Markets Authority have repeatedly highlighted the risks of decentralized structures, noting that the lack of a central counterparty complicates traditional investor protection mandates. As regulatory frameworks evolve, protocols that minimize governance centralization and implement robust oracle security are more likely to align with future compliance standards, while those relying on opaque administrative controls may face increased scrutiny.

FAQ

What is a smart contract audit?

An audit is a line-by-line review of a protocol's code conducted by independent security firms to identify vulnerabilities and logic errors before the code is deployed.

How do flash loan attacks work?

An attacker borrows a massive amount of uncollateralized capital, uses it to manipulate a price oracle, exploits a protocol using the false price, and repays the loan all within a single transaction block.

Why do protocols ask for infinite token approvals?

Protocols request infinite approvals to save users from paying network transaction fees every time they want to deposit or trade a specific token in the future.

What is a governance timelock?

A timelock is a mandatory delay programmed into a smart contract that forces a waiting period between when an administrative change is approved and when it is actually executed.

Sources

Smart Contracts — Ethereum Foundation
Decentralized Oracles — Chainlink

Basis Desk is a source-verified crypto newsroom. Market data, a free MCP server for AI agents and JSON APIs: basisdesk.news/developers. Not investment advice.

How Decentralized Exchanges Work: AMMs and Liquidity Pools

Basis Desk — Tue, 29 Sep 2026 21:36:18 +0000

AI disclosure: drafted by Basis Desk's AI newsroom and machine-checked against the primary sources listed below — how we use AI. Originally published on Basis Desk.

Decentralized exchanges replace traditional order books with automated market makers and liquidity pools. Understanding the constant product formula, LP tokens, and impermanent loss is essential for navigating decentralized finance.

Key points

Automated Market Makers (AMMs) replace traditional order books with smart contracts and mathematical formulas to execute trades.
Liquidity pools aggregate capital from users, who receive LP tokens representing their share of the pool and accrued trading fees.
The constant product formula (x * y = k) dictates asset pricing, causing the price of an asset to increase as its supply in the pool decreases.
Impermanent loss occurs when asset prices diverge from their deposit ratio, resulting in underperformance compared to holding the assets outside the pool.

Decentralized exchanges facilitate the trading of digital assets without intermediaries by relying on self-executing smart contracts. Instead of matching buyers and sellers through traditional order books, these platforms use automated market makers and crowdsourced liquidity pools to execute trades instantly.

The Shift from Order Books to AMMs

In traditional finance and centralized cryptocurrency platforms, trading relies on an order book model. Buyers submit bids indicating the maximum price they are willing to pay, and sellers submit asks indicating the minimum price they will accept. A centralized matching engine pairs these orders. You can read more about this architecture in our guide on how crypto exchanges work.

Replicating this model on a base-layer blockchain like Ethereum presents significant technical hurdles. Every action on a blockchain—including placing, modifying, or canceling an order—requires a transaction fee (gas) and is subject to the network's block time latency. In a volatile market, market makers must constantly update their orders, which becomes prohibitively expensive and slow on a decentralized ledger.

To solve this, decentralized finance (DeFi) developers introduced Automated Market Makers (AMMs). An AMM is a smart contract that holds reserves of two or more assets and allows users to trade against those reserves at prices determined by a hardcoded mathematical formula. There is no matching engine and no counterparty waiting on the other side of the trade. The smart contract itself acts as the counterparty, providing continuous liquidity regardless of market conditions.

Liquidity Pools and LP Tokens

For an AMM to function, it needs capital. This capital is aggregated into liquidity pools, which are smart contracts containing locked reserves of tokens. The users who deposit their assets into these pools are known as liquidity providers (LPs).

In a standard AMM model, a liquidity provider must deposit an equal value of two different assets to fund a specific trading pair. For example, to provide liquidity to an $ETH and $USDC pool, a user must deposit an equivalent dollar amount of both tokens based on the current market exchange rate.

In exchange for their deposits, the protocol issues LP tokens to the provider. These tokens act as a cryptographic receipt. They represent the provider's proportional share of the total liquidity pool. When traders swap assets through the pool, they pay a small fee (often a fraction of a percent). These fees are retained within the pool, increasing the total value of the reserves. Because the LP tokens represent a percentage claim on the pool, their underlying value grows as fees accumulate. When a provider wishes to exit, they burn their LP tokens to withdraw their original deposit plus their share of the accrued trading fees.

The Constant Product Formula

The pricing mechanism at the heart of most foundational AMMs is the constant product formula, expressed algebraically as x * y = k.

In this equation, x represents the reserve balance of the first token, y represents the reserve balance of the second token, and k is a constant value that must remain unchanged after a trade is executed (excluding the addition of trading fees).

Because k must remain constant, any increase in the supply of token x must be offset by a decrease in the supply of token y. This inverse relationship creates a hyperbolic price curve. As the supply of one token in the pool decreases, its price relative to the other token increases exponentially.

To illustrate this, consider a hypothetical liquidity pool containing 10 $ETH and 20,000 $USDC.

Assuming these are the only assets in the pool, we first calculate the constant k:
10 (ETH) * 20,000 (USDC) = 200,000 (k).

The implied price of 1 $ETH in this pool is 2,000 $USDC (20,000 / 10).

Now, assume a trader wants to buy 1 $ETH from this pool. The trader is removing 1 $ETH, meaning the new $ETH balance (x) will be 9.

To find the new $USDC balance (y) required to keep k constant, we divide k by the new $ETH balance:
200,000 / 9 = 22,222.22 $USDC.

The pool now requires 22,222.22 $USDC to maintain the constant product. Since the pool previously held 20,000 $USDC, the trader must deposit the difference:
22,222.22 - 20,000 = 2,222.22 $USDC.

The trader paid 2,222.22 $USDC for 1 $ETH. This is higher than the initial implied price of 2,000 $USDC. The difference between the expected price and the executed price is known as slippage. The constant product formula naturally enforces slippage: larger trades relative to the total size of the pool incur higher slippage, protecting the pool from being entirely drained.

Price Discovery and Arbitrage

AMMs do not have internal price feeds or order books to determine the "true" market value of an asset. The price of an asset within a liquidity pool is determined solely by the ratio of the two assets in that specific pool.

If the price of $ETH rises on external centralized exchanges, the price of $ETH inside the AMM pool remains unchanged until a trade occurs. This creates a price discrepancy.

Arbitrageurs resolve this discrepancy. If $ETH is trading at 2,100 $USDC on a centralized exchange but is still priced at 2,000 $USDC in the AMM pool, arbitrageurs will buy the cheaper $ETH from the AMM and sell it on the centralized exchange for a profit. As they buy $ETH from the AMM, they add $USDC and remove $ETH, altering the ratio. This process continues until the price inside the AMM matches the external market price. AMMs rely entirely on this profit-driven arbitrage to maintain accurate pricing.

The Cost of Providing Liquidity: Impermanent Loss

While liquidity providers earn trading fees, they also face a unique risk known as impermanent loss. This phenomenon occurs when the price of the deposited assets changes compared to when they were deposited.

Impermanent loss is defined as the difference in value between holding assets in an AMM liquidity pool versus simply holding the same assets in a standard cryptocurrency wallet.

When the price of one asset in a pool surges on external markets, arbitrageurs buy that asset from the pool, draining its supply and replacing it with the other asset. Consequently, the liquidity provider ends up holding less of the appreciating asset and more of the depreciating (or stable) asset. If the provider withdraws their liquidity at this point, the total dollar value of their assets will be lower than if they had never deposited them into the pool, even after accounting for some accrued fees.

The loss is termed "impermanent" because if the asset prices return to their exact original ratio at the time of deposit, the loss disappears. However, if the provider withdraws their assets while the prices are divergent, the loss becomes permanent. For highly volatile trading pairs, impermanent loss can frequently outpace the yield generated from trading fees.

The Evolution to Concentrated Liquidity

The standard constant product formula spreads liquidity evenly across an infinite price curve, from zero to infinity. This means the vast majority of capital in a pool is never utilized, as assets typically trade within a specific, narrower price range. This results in poor capital efficiency.

To address this, newer AMM models introduced concentrated liquidity. This architecture allows liquidity providers to allocate their capital within custom price ranges (ticks).

For example, in a stablecoin pool trading $USDC against another dollar-pegged asset, an LP can choose to provide liquidity only between the prices of $0.99 and $1.01. Because the capital is concentrated where the trading actually occurs, the LP captures a much higher share of the trading fees relative to their deposit size.

However, concentrated liquidity requires active management. If the market price moves outside the LP's chosen price range, their liquidity becomes inactive. It stops earning fees, and the LP's position is converted entirely into the less valuable asset. This increases the risk of impermanent loss and shifts the role of a liquidity provider from a passive depositor to an active market participant.

Common Misconceptions

DEXs have no fees: While DEXs eliminate centralized intermediaries, they are not free to use. Traders must pay network gas fees to execute the smart contract on the blockchain, as well as a swap fee that is distributed to the liquidity providers.
Impermanent loss means losing the initial dollar investment: Impermanent loss does not necessarily mean the fiat value of the portfolio has decreased. It strictly measures the opportunity cost—the underperformance of the liquidity pool position compared to a simple buy-and-hold strategy of the same initial assets.
Providing liquidity is a passive income strategy: While early AMM models allowed for passive depositing, the introduction of concentrated liquidity and the constant threat of impermanent loss mean that profitable liquidity provision requires active monitoring, rebalancing, and sophisticated risk management.

How This Connects to the Market

Decentralized exchanges and AMMs have fundamentally altered crypto market structure. By removing the need for centralized market makers, AMMs allow for permissionless listing. Anyone can create a market for a new token simply by deploying a smart contract and funding a liquidity pool. This has made DEXs the primary venue for price discovery of long-tail assets and early-stage tokens before they reach the volume required for centralized exchange listings. You can explore the differences in custody and execution in our centralized vs decentralized exchanges guide.

The growth of AMMs has also attracted significant regulatory attention. Authorities such as the US Securities and Exchange Commission (SEC) and the European Securities and Markets Authority (ESMA) are examining how traditional financial regulations apply to DeFi. A key area of regulatory focus is the distinction between the immutable smart contracts residing on the blockchain and the entities or foundations that host the front-end web interfaces used to access them. Regulators are increasingly scrutinizing whether the developers or governance token holders of these protocols act as unregistered brokers or exchanges under existing securities laws.

FAQ

What is an Automated Market Maker (AMM)?

An AMM is a smart contract on a decentralized exchange that uses a mathematical formula to price assets and execute trades automatically, without needing a traditional order book or a centralized matching engine.

How do decentralized exchanges determine asset prices?

DEXs determine prices based on the ratio of assets within a specific liquidity pool. They rely on independent arbitrageurs to buy and sell assets when the internal pool price diverges from the external market price.

What are LP tokens?

LP (Liquidity Provider) tokens are cryptographic receipts issued to users who deposit assets into a liquidity pool. They represent the user's proportional claim on the pool's assets and the trading fees it generates.

What is concentrated liquidity?

Concentrated liquidity is an advanced AMM feature that allows liquidity providers to allocate their capital within a specific price range, improving capital efficiency but requiring active management to ensure the position remains in range.

Sources

Uniswap v3 Core Whitepaper — Uniswap
Statement on Decentralized Finance — US Securities and Exchange Commission
Uniswap v2 Core Whitepaper — Uniswap

Basis Desk is a source-verified crypto newsroom. Market data, a free MCP server for AI agents and JSON APIs: basisdesk.news/developers. Not investment advice.