You could for instance take the first decimal via pregmatch and use it as a 0-9 RNG. My test script that I ran hundred of times (1 billion iterations each) verifies that it's evenly distributed 0-9 and no number is in favor.
Okay, how about taking the exact blocksize as the second secret then? That should be unguessable before the block gets found/generated?
Not beforehand, the second a new block is found the information is there and I can use it for 1 conf txs.
If so what is it about their method(s) that make them unsuitable for your use-case (and thus requires you to re-invent their apparently not so elegant after-all wheel)?
I just want it to be a full transparent RNG layer on top of the block chain.