Jacek Sieka

> The algorithm will works. If there is no finality, the "B-Syncer" will do nothing, it will keep waiting for a valid F from CL. then we can't sync the...

A few benchmarks for hashing the beacon state - this is certainly not a exhaustive benchmark because it only tests 64-byte values, but it's still indicative on that particular sample...

> includes OpenSSL from what I remember, `openssl == blst` more or less

> Turns out you need to indeed call =destroy(getThreadDispatcher()) on the dispatcher and do so before you collect all cycles with GC_fullCollect()`. That solved it. feel free to turn this...

we're slowly working towards lock file support in nimble which would subsume the pinned file - putting hashes in the nimble file would be a no-go because it would needlessly...

When something depends on libp2p, it inherits the version constraints in in the nimble file. Consider chronos - if you were to pin chronos at some specific hash, _all_ applications...

> 129 is invalid exit code number because it falls into the signals range. For Linux SIGHUP signal sent to process could also return exit code 129. I don't remember...

hm, interesting conundrum .. if _they_ have us as a direct peer, we want to send IDONTWANT to them to avoid getting a redundant copy - I don't remember if...

simplified: ```nim import chronos # only depends on asyncloop's transitive closure proc t(): Future[void] = var retFuture = newFuture[void]("") retFuture.fail(newException(ValueError, "")) return retFuture proc m(transp: int): Future[void] = var retFuture...

Upstream bug: https://github.com/nim-lang/Nim/issues/23390