Satoshi

Anna needs to pay 25000 sat, but her wallet displays 0.00025 BTC. These are not different currencies or a better exchange rate: they are two ways of writing the same amount. The relationship is 1 BTC = 100000000 sat, so 0.001 BTC = 100000 sat as well. For everyday smaller amounts, sats can be easier to read than a string of zeros after a decimal point. Bitcoin's exchange rate against a national currency can change; the conversion between BTC and sat does not change with it. [1] [2]

When Anna selects sats in the settings, her bitcoin goes nowhere and no new coins appear. Only the number and unit on the screen change. The abbreviation sat denotes the unit; sats is commonly used in the plural. The name honors Satoshi Nakamoto, Bitcoin's creator, rather than a separate asset that must be purchased separately. A smaller unit makes small amounts easier to describe. It guarantees neither stable purchasing power nor a profit. [2]

Suppose Anna's wallet uses a previously received amount of 50000 sat. It sends 25000 sat to the recipient, returns 24000 sat to Anna and leaves 1000 sat as a fee for the miner that includes the transaction in a block. The numbers balance: 50000 = 25000 + 24000 + 1000. Anna has therefore spent 26000 sat on the payment, not the entire amount used. This is an illustration, not a typical or recommended fee. Before approving, read the recipient's amount and the fee separately. [8]

Alongside the fee, the wallet may show a Fee Rate in sat/vB. This is the number of satoshis per virtual byte, a unit used to measure transaction size for fees. A size of 100 vB at 10 sat/vB gives a fee of 1000 sat. The rate is not a percentage of the money sent. Two payments of the same value can have different sizes, for example when one combines more previously received amounts. Check the result in the wallet's final review screen. [7] [8]

A number without its unit is not enough. Entering 25000 in a sats field means something very different from entering it in a BTC field. After scanning a payment QR code, check the address, network, amount and fee before signing. A signature is digital authorization to spend: the wallet creates it using a private key, a secret value that enables control over the bitcoin. Under BIP 321, the payment-link specification, a payment link's amount parameter uses decimal BTC and a period: amount=0.00025 means 25000 sat. That remains true when the wallet displays sats or uses a local decimal separator. There is no need to edit the link manually; what matters is the correct result on the confirmation screen. [3]

The network does not contain little files representing individual satoshis. It records transaction outputs with amounts and conditions for spending them. An output that has not yet been spent is called a UTXO. A wallet may have several such received amounts and add their values into one balance. When paying, it spends some outputs in full and creates new ones for the recipient and any change. Satoshi is the unit used to count these values, not a separate object sitting in the wallet. [2]

An amount’s precision and a practical payment size are different things. An output can contain 1 sat. Nodes, the computers that verify and pass on transactions, may nevertheless refuse to relay a transaction that creates an output that is too small. Dust concerns a node's transaction relay rules and estimated future spending costs. The threshold also depends on the output type and policy settings. It is not a universal rule that every valid payment must meet the same minimum amount. Even a tiny output already in a block may cost more to spend than it is worth. [7]

Lightning Network uses payment channels, where participants update how the funds committed to a channel are divided. This lets payments take place without recording each one separately in a Bitcoin block. Its internal calculations also use millisatoshi, abbreviated msat: 1 sat = 1000 msat. This is useful for finer fee accounting, for example. It does not create an output containing a fraction of a satoshi on Bitcoin's base layer. When channels close, Lightning's rules convert values into whole satoshis and omit some outputs that are too small. More precise internal accounting and final settlement are different things. [6] [5]

Dividing one BTC into a hundred million parts does not increase the amount of bitcoin, just as converting metres to centimetres does not make a table longer. New bitcoin is created according to the block subsidy rules: the new issuance associated with a block. At a Halving, that subsidy is halved in whole satoshis; fractions are discarded, and far enough into the future the result becomes zero. The technical constant MAX_MONEY serves as an amount-range check. By itself, it does not mean that exactly 21 million BTC will actually be issued and available to spend. Lost keys and some unusable or unclaimed rewards also reduce availability. [1] [8]

Bitcoin Core uses CAmount, a 64-bit integer type, for amounts, and a constant called COIN with a value of 100000000. The amount 0.00025 BTC is therefore handled internally as the integer 25000. This helps avoid inaccuracies in ordinary binary floating-point arithmetic. For a user, the lesson is simple: check the unit and exact amount. If you build a calculator or process payments in software, use whole satoshis or exact decimal arithmetic rather than rounding an approximate result afterwards. [1]