I’ll have to put in on my list. Generally I don’t think many people have observed bitcoin as time, nor have applied that ontology of time to QM since continuous time is the axiom underpinning literally everything. Continuous time is the Tower of Babel for QM if they are wrong. We are literally watching the construction of time and we can see both sides of the *computational* event horizon since we are the constructors of the time (only our influence is in the network) and we have the ledger of time events. My mind goes to thinking if we can ever get total network hash to 1 hash per unit Planck time and what that means. If we are objectively constructing time in bitcoin from thermo, what does it mean to be constructed from time? What is light since we are composed of light? What is the relationship of light and time?

Replies (1)

ok, then i'll suggest that maybe you have a look at writing code to demonstrate the principles you are talking about so much. i have done quite a bit of it myself, with difficulty adjustments, varying the hash functions, difficulty adjustment regimes, a former manager, used to be a physics researcher, explained PID controllers and that's very interesting and relevant. bitcoin is P only, i developed one that used integrals as well, and found it was REALLY good at accurately adjusting to sharp changes in hashpower (and this illustrated the way that if you can't predict how fast hashpower can change, you should not use a clamp). i agree with you, in the principle that the model of time can't be continuous, and thus most of quantum theory is bunk. computation is much more accurate in understanding it, and the hard fact that you can't measure planck time does mean that you must use probability and algorithmic logic to understand the behaviour of matter, and everything that is made of matter. it's just a practical reality of programming, they have made the time window down to nanoseconds and that is still an eternity compared to the time precision you need to understand stuff like even, how to build computation devices.