Yep - I suspect that there is a well known (by the designer, not by the DIY community) method for selecting nonce initialization data, to prevent engine overlap, and hence lost utilization efficiency. I'd really like to understand those semantics - they have serious implications for chip-chaining lengths, polling times, and so forth, which could result in significant performance optimizations on systems that are "in-the-know", versus ours, where we just poke in the dark.

To be TRULY open source, all the magic sauce needs to be known publicly - companies like SCO, who sold OS based systems and concealed all the build instructions and parametrization necessary to get the systems working from the "open source" base they provided were bankrupted, eventually, by lawsuits. They used the fruits of others' development efforts, and conspired to ensure that no-one could use their derivative works to compete with them.

It can't take but a few sentences to describe how the internal semantics work, at least to the extent that we need for designs - answering these questions would be a good 5-minute break from heads-down development.... Take a break, Fury!