Skip to content

Test poseidon-array compatibility #2698

Closed
richardpringle wants to merge 4 commits intodevelop-3.0from
rp/poseidon-arrays-compat
Closed

Test poseidon-array compatibility #2698
richardpringle wants to merge 4 commits intodevelop-3.0from
rp/poseidon-arrays-compat

Conversation

@richardpringle
Copy link
Contributor

This is a test, do not merge

@richardpringle richardpringle changed the base branch from main to develop-3.0 December 16, 2025 21:36
@richardpringle richardpringle force-pushed the rp/poseidon-arrays-compat branch from 08496bd to bc726db Compare December 17, 2025 17:17
@richardpringle
Copy link
Contributor Author

attempt #2

@richardpringle richardpringle force-pushed the rp/poseidon-arrays-compat branch from 4cc851a to 094bda9 Compare December 18, 2025 00:30
@richardpringle
Copy link
Contributor Author

CI passing (ish) without my changes

There's a performance regression here, again, without any changes.

This reverts commit 094bda9.
@richardpringle
Copy link
Contributor Author

The above commit does contain the poseidon-array (instead of Vec) changes

@richardpringle
Copy link
Contributor Author

turns out you can dispatch the workflow with a proof-systems commit:
https://github.com/o1-labs/o1js/actions/runs/20357830362

@richardpringle richardpringle requested review from dannywillems and removed request for dannywillems December 22, 2025 17:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants