ARM

ModernCYPH3R

u/Super_Rush7926 The short answer is **the Clock-Time Oracle Trap**. A blockchain is a closed, trustless state machine. It has absolutely no native, trustless way of knowing what day, hour, or second it is in the real world. There's no decentralized atomic clock. If Bitcoin's protocol tried to release coins based on a standard calendar schedule (e.g., "release 1% on January 1st"), it would be forced to rely on two highly insecure vectors: 1. **External Oracles**: Relying on an external API or data feed to tell the network what time it is, which instantly introduces a centralized point of failure. 2. **Validator Local Clocks**: Relying on the local clock timestamps of the miners. If you did this, miners would immediately spoof their timestamps to trick the network into thinking it's next year, artificially accelerating the coin emission to dump on the market. **Block height (Proof of Work) is the only native, trustless metric of time that exists within a blockchain.** By tying emission to block height, and using the Difficulty Adjustment algorithm to dynamically anchor those blocks to roughly 10 minutes of physical computational work, Bitcoin translates physical energy directly into chronological intervals without needing to trust any external clock. # The Floating-Point Security Risk: To calculate a smooth, continuous percentage of unreleased supply, a protocol has to execute fractional mathematical divisions. In low-level consensus languages like C++, **floating-point mathematics are a notorious security vulnerability**. Different CPU architectures (Intel vs. AMD vs. ARM) handle floating-point rounding errors in slightly different ways. If two nodes running different CPUs calculate a fractional block reward and end up with even a single-satoshi rounding discrepancy, the network splits in half (a hard fork) and consensus is destroyed. To avoid this, Satoshi Nakamoto(he, they, whatever) chose a clean, bug-free integer bitwise-shift: **Halving the block reward every 210,000 blocks**. It's a simple binary shift (`>> 1`) operating on raw integers. No rounding errors, no floats, zero risk of consensus drift. # Do other coins use a percentage/decay schedule? Yes, projects like **Monero (XMR)** use a continuous decay curve that operates on a block-by-block basis to smooth out emission rather than sudden step-function halvings. However, **every single one of them still pegs the math to block count**, never real-world calendar clock-time, for the exact reasons listed above.