The Cost of Movement: Fee Calculation and Estimation Logic

In the "Forge of the Ledger," every movement of money requires a "Bribe" (the Fee) to the miners. But how much should you pay? If you pay too little, your transaction might wait for weeks. If you pay too much, you are wasting your hard-earned satoshis. The Bitcoin Core wallet includes a sophisticated Fee Estimation system that watches the network's "Market Rate" and recommends the perfect fee for your desired confirmation time. It is the "Price Discovery of the Sovereign."

Fee calculation is a "Multi-Dimensional Problem." You have to consider the "Size" of your transaction (in vBytes), the "Urgency" of your payment (in blocks), and the "Future Cost" of your change output. In the source code, this is handled by a bridge between the wallet logic and the node's fee_estimator.

Analyzing the Price Engine: CalculateMaximumSignedTxSize

Before the wallet can estimate the fee, it must know the "Exact Size" of the transaction. But a transaction's size can change depending on how it is "Signed." To be safe, the wallet calculates the "Maximum Possible Size."

/**
 * This function calculates the "Max Weight" of a transaction before it is signed.
 */
TxSize CalculateMaximumSignedTxSize(const CTransaction &tx, const CWallet *wallet, ...)
{
 // 1. We start with the "Fixed Weight" (Version, LockTime, and counts).
 int64_t weight = (4 + 4 + counts_size) * 4; // Scale factor for non-witness data.

 // 2. We loop through every "Input" and estimate its "Signature Size."
 for (uint32_t i = 0; i < txouts.size(); i++) {
 // We use the "Descriptor" to see how big the signature MUST be.
 const auto txin_weight = GetSignedTxinWeight(wallet, ...);
 weight += *txin_weight;
 }

 // 3. Return the "Total Weight" and the "Virtual Size" (vBytes).
 return TxSize{GetVirtualTransactionSize(weight), weight};
}

Explaining the Fee: The Postage Meter

• WITNESS_SCALE_FACTOR: Remember the "SegWit Discount"? This constant (4) is what makes SegWit data "Cheaper." When we calculate the "Weight," we multiply the non-witness data by 4 and add the witness data by 1. This "Mathematical Geometry" is what defines the "vBytes" you see in your wallet. It is the "Law of the Discount."

• GetSignedTxinWeight: A signature is not a fixed size. Depending on the math, it can be 71 bytes or 72 bytes. The wallet always "Assumes the Worst" (72 bytes). This "Conservative Buffer" ensures that you always include "Slightly More Fee" than needed, so your transaction never gets "Stuck" because it was one byte too big. It is the "Safety Margin of the Sovereign."

• GetVirtualTransactionSize: This is the "Final Price Tag." It takes the raw "Weight" and converts it into the "vBytes" that the miners use to calculate their profit. When you set a "Fee Rate" of 10 sat/vB, the computer multiplies that by this virtual size to get the total fee. It is the "Metric of the Market."

The "Sovereign's Fee Control"

As an architect, you should always enable Replace-By-Fee (RBF). It allows you to "Bump" the fee of a pending transaction by sending a new version with a higher bribe. This "Active Negotiation" is the ultimate tool for managing the "Cost of Movement." You are the "Master of the Market," ensuring your "Heartbeats" always reach the ledger, no matter how congested the forge becomes.