dshulyak

bors try

bors merge

The concern here is what happens inside Float64 conversion. Not because of the casting to uint64. But right this is probably an issue because of `f = math.Ldexp(float64(mantissa), exp-Msize1)`. Before...

rational number (big.Rat) internal state is two integers (numerator/denominator). when Float64 is called they are divided and floating part is kept. instead we can divide them ourselfs and round down.

Thanks i forgot to open a bug for that, it is not a problem if you just store value as int64 and cast it back to uint64 when loaded. But...

this was a bug about nonce, please open another issue with specific description

I still believe that it will be a huge mess if opened transactions will be passed across modules. What i would do instead is to check why we need to...

bors merge

this seems to be the culprit: ``` hare_rounds_test.go:146: at layer 0 node 2 has non-empty set in result (0) ```

since we are adding nonce to selfspawn, we can probably support this feature as well without significant effort? @lrettig do you want to include it?