Currently, the benchmarks and SMHasher scores shown in README.md and xxhash.h are out of date. They should be updated, as XXH32 fails SMHasher and they don't include the newer hashes.

Hi, im trying to use Hashids with Typescript and Node.

import Hashids from 'hashids';

I'm not getting any Typescript errors in the editor, but Im getting this error when the code is compiled.

Using ts-node version 8.5.4, typescript version 3.7.5

`Error: No valid exports main found for 'node_modules\hashids'
at resolveExportsTarget (internal/modules/cjs/loader.js:625:9)

$ python3 loki.py
Traceback (most recent call last):
  File "loki.py", line 43, in <module>
    from lib.lokilogger import *
  File "/Users/w/Downloads/Loki/lib/lokilogger.py", line 15, in <module>
    from helpers import removeNonAsciiDrop
ModuleNotFoundError: No module named 'helpers'

Python 3.7.7 homebrew
Cloned directly from master.
helpers.py is present in

This one is all you @NoHatCoder :) Not sure what you have planned for that, but it seems like we should check in a copy of your blog post at some point when it is ready, just so people can understand what is going on here with hash levels. Maybe we make a "doc" directory? I can then link to it with the main readme.md (assuming GitHub actually has a way to do that... I will check).

- Casey

Winxp, need to redo Server and Client Documentation

Wiki should be updated to inform users the C# client is technically Depreciated at this time and current wiki should be converted to using the python client as its main focus ( Or make the link to the Client repo much more apparent ((probably the best option)))

Videos should be rather generic on setup Pointing users to use commands found

Here we're re-exporting methods of ethjs-util:

https://github.com/ethereumjs/ethereumjs-util/blob/3b1085059194b02354177d334f89cd82a5187883/src/index.ts#L2-L5

But because they're manually added to the exports object, typescript is not adding type definitions for them and Typescript users get an error when using one of those methods, e.g. stripHexPrefix.

I motion to split "block layer" and "codec layer" and do so consistently across all our specs and docs.

Fundamental reason: the work the codec code does is almost entirely about how to encode/linearize/serialize/whatever-you-call-it Data Model trees into flat bytes (and of course vice versa, unfurling flat bytes to DM). It's very little to do with blocks. There's two separate things going on

Not always in real life need to work so accurately. For example, if it is necessary to determine the motion in the picture such precision is excessive and the image will mean the same and the algorithm will say that change more than 10% that would be wrong.

ExtAverageHash
real live recommend add filter

if p > avg && math.Abs(p-avg) > 12.5 {

problem

![output_2_3](https://user-images.gi