5
$\begingroup$

Suppose we have a random number generator badrand() generating 1 with probability $0.9$ and 0 with probability $0.1$.

How can we combine $n$ bits from badrand() to get one bit of betterrand()? What will be its probability of giving a 0 or 1?

I assume that this is possible since the entropy of the combined output increases with each call to badrand(). Please guide me if I am wrong.

$\endgroup$
1

3 Answers 3

1
$\begingroup$

This is pretty common and easy to fix. Although that's a really poor RNG :-)

In the case of very small computational capabilities (e.g. Arduino Uno), we'd extract via the von Neumann technique as per the other answer [see note though]. For larger devices (e.g. ARM, Snapdragon and bigger) we leverage the Leftover Hash Lemma (LHL). That allows extraction in $O(1)$ time.

Given that there is no such thing as pure randomness (it's always $\epsilon$ away from unbiased), we know from LHL that $\epsilon = 2^{-(sn-k)/2}$. We then:-

  1. Choose an acceptable bias, say $\epsilon = 2^{-64}$ as per NIST recommendation.

  2. Select a hash function to act as the principle randomness extractor, say SHA-256 so that we can utilise CPU SHA extensions for uber speed.

  3. Solving the LHL formula leads us to determine that the input length of bits to the hash function should be 2527 bits, given that your badrand() min.entropy ($H_{\infty}$) is 0.152 bits/bit.

  4. Therefore final entropy bias will be $(1-\frac{1}{2^{64}})$ bits/bit.

  5. Converting that to a probability bias, $P(x_i = 0, x_i = 1) \approx 0.5 \pm 2^{-66}$.


Note: von Neumann absolutely requires that the input stream be uncorrelated. If it has auto-correlation (typically $R > 10^{-3}$), the extraction technique is inappropriate. LHL has no such restriction. It only requires a measurement of $H_{\infty}$ so is more flexible, although it has a higher computational element only appropriate for larger processors.

$\endgroup$
11
  • $\begingroup$ Paul, thank you for an enlightening answer. Could you please guide me to the LHL formula that you are using in step 3? You have linked to a detailed paper on the LHL, but unfortunately due to my limited cognitive skills, most of it is inaccessible to me. $\endgroup$ Apr 3, 2021 at 3:48
  • $\begingroup$ Ok I get it now, but I have two questions: 1. Why did you choose $v=0.192x$? 2. You mention in step 3 that the minimum entropy of badrand() is 0.152. How do I arrive at this? My confusion arises because according to my understanding, the Shannon entropy should be $- 0.9 \log_2 0.9 - 0.1 \log_2 0.1 = 0.469$. Am I getting it wrong? $\endgroup$ Apr 3, 2021 at 4:13
  • 1
    $\begingroup$ @RiteshSingh Good questions now that (in the UK after lock down) we're moving to post sobriety. LHL is predicated on the min.entropy ($H_{\infty}$) of the input sequence for reasons I can't explain. It just is. So we don't use Shannon entropy, but calculate min.entropy as $H_{\infty} = -\log_2(P(max(x_i)) $. So $H_{\infty} = -\log_2(0.9) $. More tomorrow. $\endgroup$
    – Paul Uszak
    Apr 3, 2021 at 6:01
  • $\begingroup$ Thank you Paul! 🙏🏼🙏🏼😊 So, just to confirm, $0.152$ should be used in place of $0.192$ giving 2527 bits. Is this correct? $\endgroup$ Apr 3, 2021 at 6:27
  • 1
    $\begingroup$ @RiteshSingh Yes. You're absolutely correct. My bad. Please refer to the sobriety comment above :-( I'll fix it. $\endgroup$
    – Paul Uszak
    Apr 3, 2021 at 12:48
2
$\begingroup$

If the outputs of badrand are independent and identically distributed you can use a randomness extractor function with $m=1$ and $k=-n\lg 0.9$.

If you're prepared to have a non-deterministic waiting time for an output, the von Neumann extractor is good way to get probability exactly 0.5 out of i.i.d. bit outputs. Sample pairs of bits until you get a pair with precisely one zero; if your pair is 01 return 0 and if it is 10 return 1. The i.i.d property means that the probability of these two events is equal (in your example both have probability 0.09 and resampling has probability 0.82, leading you to expect around 100/9 badrand outputs to produce one betterrand output).

$\endgroup$
2
  • $\begingroup$ Thank you for a very interesting answer. Please forgive my naivety, but where should I use the $m$ and $k$? Besides, the $log$ in $k$ would be base 2, I presume? $\endgroup$ Apr 2, 2021 at 17:15
  • 1
    $\begingroup$ You'll find various designs for families of randomness extractors (e.g. Trevisan's extractor) in the literature and they will quote theorems about how hard they are to distinguish from a uniform distribution based on the parameters $m$ (size of output) and $k$ (the minimum entropy of the input). The $\log$ is usually taken to be base-2 in papers, though entropy can be measured to any base by multiplication by constant so it is worth checking. $\endgroup$
    – Daniel S
    Apr 2, 2021 at 17:32
1
$\begingroup$

You could leverage hash functions which are built off of the sponge construction, to serve as both a randomness extractor & entropy pool, simultaneously. The sha3-512 standardized hash function would be suitable, as it offers various strengths, including always producing bits that appear random & statistically-independent of the input data's bit distribution. This shifts the focus from how to produce near-uniform output from a non-uniform source (a rigorously solved problem), to how to make the output as difficult to reproduce as you'd like.

Think of the sha3-512 function as an object that maintains a 1600-bit entropy pool. The object can be updated with as many bits as desired, & a unique 512-bit pseudo-random output can be obtained after each update of the object. The entropy pool for the object starts off with zero bits of entropy, & each time the object is updated with new bits of some entropy distribution, the entropy pool's entropy increases proportionally. But how many bits need to be fed into the object to achieve a sufficient amount of entropy? There's a way to work that out.

If $badrand()$ produces bits

1 with probability 0.9 and 0 with probability 0.1

then we can use the formula

$\sum_{i=0}^{1} $ $Pr(c_{i})$ $⋅$ $log_2($$\frac{1}{Pr(c_{i})}$$)$

where $c_{0} = 0$, $c_{1} = 1$, and $Pr(x)$ gives the probability of $x$ occurring, to calculate

$Pr(c_{0})$ $⋅$ $log_2($$\frac{1}{Pr(c_{0})}$$)$ $+$ $Pr(c_{1})$ $⋅$ $log_2($$\frac{1}{Pr(c_{1})}$$)$ $=$ $0.46899559358928133$

as the amount of entropy (in bits) each call to $badrand()$ can be expected to produce on average.

But, as the above answers describe, the minimum entropy

$H_{min} = -log(0.9) = 0.15200309344504997$

is the value that should be used for various reasons (page 10).

If $N$ is the amount of entropy (in bits) you wish to fill the pool with, and we use $B = 2^{H_{min}}$ as a logarithmic base, then the number of calls to $badrand()$ you'd need to initialize the object is

$N_B = log_B(2^N)$

Once the object is initialized, you then have a forward secret pseudo-random number generator that produces bits in 512-bit chunks that are indistinguishable from random, contains entropy $≈ N$, & increases in entropy each time it's updated with additional entropic material. After you've consumed the first 512-bit output, feed at least another $bitrate = 576$ number of bits from $badrand()$ to the object before reading each subsequent output. This causes the internal state to be permuted using its $f$-function.

$\endgroup$
2
  • 1
    $\begingroup$ What is your motivation for "bitrate=576"? Specifically the 576 quantity? $\endgroup$
    – Paul Uszak
    Apr 3, 2021 at 17:11
  • 2
    $\begingroup$ That's what the keccak team calls the blocksize of the hash function, or the number of bits from the input data that are xor'd with its internal state before running its f-function permutation and is ready to process input data again. It's a term used in common by sponge-construction functions. en.wikipedia.org/wiki/Sponge_function Also, added another reference in the answer to clarify this point. $\endgroup$
    – aiootp
    Apr 3, 2021 at 17:55

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.