In undergrad studies we were told a true story about a fire that broke out in a conference hotel; the engineer woke up in their room, grabbed many buckets of water, threw them all over the room until the fire was extinguished, and went back to sleep. The physicist woke up, calculated the exact angle, angular momentum, and amount of water to throw at the fire, the last drop elegantly extinguished it, and the physicist went back to sleep proud of themself. The mathematician too woke up, proved to themselves that a solution exists, and went back to sleep. This tale manifested in kas history, with golang devs taking an engineer's approach, rusty @MichaelSuttonIL taking a physicist's approach, and while I am not a mathematician per se I do tend to be satisfied with proving a solution and going to sleep. In truth, a distributed systems engineer must embrace the mental model of the physicist, in the sense of comprehending theoretical constraints vs degrees of freedom as a method of drawing the contours of the solution space---merely implementing a working solution is typically not enough, likely unsound. To give a quick example, consider how the full node code should identify or detect when the node is fully synced or require syncing (aka IBD in btc/kas jargon), specifically when a mining node is up to date with the DAG and should start or resume mining. It's very easy to implement some flow that works -- until it doesn't: premature detection may lead to an unsynced miner flooding its peers with out-of-date unmergable blocks, whereas overdue detection leads to synced miners not initiating mining when needed, eg after a network hiccup or a node restart, despite being fully synced. The "physicist" must comprehend these opposing constraints, weigh the respective implications of the edge-threats, pick a sound sweetspot and proceed to the algorithmic design and implementation. This process is much more challenging, rewarding, and robust compared to the prevailing engineers' approach of just building systems that "work" c'est tout. It was a privilege to watch from the courtside your thoroughness and technological leadership @MichaelSuttonIL. Kudos to you and to the rest of the RK/10bps devs who undertook this heavylifting. More than the product itself, you have ingrained the culture of Kaspa in your image, that of a boutique R&D engine driven by first principles and fundamentals throughout. Looking forward eagerly, impatiently for the implementation of this KIP and for mainnet HF activation. Make satoshi great again <3