Bitcoin market and network context

A policy usually names one price source and one time of day for valuing the holding, for example at each month end. Using the same named source every time matters more than any single reading. Price moves also change how much of the company's assets sit in bitcoin, so the policy generator includes a review trigger: when the holding's value exceeds the cap by a set margin, the approvers meet and decide what to do. Check that against your own figures and cap, not this page. For how a holding is measured in the accounts, see accounting and tax notes.

This shows how far the price is below the highest level recorded, a measure often called the drawdown. It is one reference point when directors choose the fall to test in the sizing calculator. A policy can require the cap to be stress tested at an agreed fall before any purchase, so the company knows in advance what a large fall would mean for its runway. See choosing the inputs.

These are averages of past closing prices in US dollars, worked out on this page from completed daily and weekly closes. They describe where the price has been. They are context, not signals, and this site does not use them to suggest when to buy or sell. A written policy sets purchase and review rules in advance, so decisions do not depend on reading a chart. See what a policy should cover.

The block subsidy halves every 210,000 blocks under rules fixed in the software, so the schedule is known in advance. The time estimate assumes the 10 minute target block time; real block times vary. A halving does not change anything a company's policy controls, but directors often ask about it. See the bitcoin halving and the four-year cycle and key facts about bitcoin.

Hash rate estimates the computing power producing blocks. Difficulty resets every 2,016 blocks to keep blocks close to 10 minutes apart. These are background facts about the network. For a company, the controls that matter most sit in its own hands: who holds the keys, who approves a transfer and how recovery is tested. See practices that apply to every custody model.

Fees are paid per virtual byte (vB) of transaction data and rise and fall with demand for block space. A multisig spend carries more signatures, so it is larger than a single-key spend and costs more in fees. Plan withdrawals from an exchange or custodian into the company's multisig rather than making many small ones, send a small test amount to a new address first, and record each fee in the books. The 250 vB example is an illustration only; real sizes depend on the wallet and the number of inputs. See custody practices.