Poseidon2: reorder constants as per Plonky3

[tcoratger]

🗒️ Description

@GrapeBaBa I think we had an ordering problem when compared to Plonky3, please check this, this should solve your problem without any leansig modification.

🔗 Related Issues or PRs

Should close #243

✅ Checklist

• Ran tox checks to avoid unnecessary CI fails:

  uvx tox

• Considered adding appropriate tests for the changes.
• Considered updating the online docs in the ./docs/ directory.

[unnawut]

@tcoratger This requires key re-generation right? So I can do so for https://github.com/leanEthereum/leansig-test-keys for prod keys as well

[tcoratger]

@tcoratger This requires key re-generation right? So I can do so for https://github.com/leanEthereum/leansig-test-keys for prod keys as well

Yes correct, please @GrapeBaBa confirm and then we can regenerate the keys

[GrapeBaBa]

Works fine

[tcoratger]

Thanks, will merge, @unnawut then I guess we can regenerate the production keys on the other repo (only if they are generated via the Python code, no need if they are generated via Rust).

[unnawut]

Btw. I've been running the python keygen in the background since the weekend, expecting to have the keys to update https://github.com/leanEthereum/leansig-test-keys around end of today if not early tomorrow.

[unnawut]

Hey all. The new prod keys and test vectors have been generated.

• Test vectors are in the artifacts section here: https://github.com/leanEthereum/leanSpec/actions/runs/20778631727
• The prod keys used to generate the vectors are here: https://github.com/leanEthereum/leansig-test-keys/releases/tag/leanSpec-77bde6b