feat/poseidon-hash

[davibauer]

PR checklist:

• [ ] Test coverage for the proposed changes
• [ ] PR description contains example output from repl interaction or a snippet from unit test output
• [ ] Documentation has been updated if new natives or FV properties have been added. To generate new documentation, issue cabal run tests. If they pass locally, docs are generated.
• [ ] Any changes that could be relevant to users have been recorded in the changelog
• [ ] In case of changes to the Pact trace output (pact -t), make sure pact-lsp is in sync.

Additionally, please justify why you should or should not do the following:

• [ ] Confirm replay/back compat
• [ ] Benchmark regressions
• [ ] (For Kadena engineers) Run integration-tests against a Chainweb built with this version of Pact

[CryptoPascal31]

I am very interested by this PR.

Let me ask some questions:

You've chosen different round numbers than recommended by the Research Paper: 53 partials rounds here , vs 57 in the paper for exp=5, Security=128 bits, arity=3 (table 2). And you've chosen different constants values (for ARC layer and Mix layers) than the reference implementation proposed by the authors.

As a consequence, your tests don't match with the reference test vectors. And this is not compatible with many others implementations (eg Circom ZK circuit compiler)

Any reason for that ?

Anyway, the parameters used should be documented somewhere. Poseidon is not a standard and there are many tweakable parameters.

[edmundnoble]

Closing in favor of #1313, which is merged.