Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bugfix: fix bug caused by not handling mont form of stone #11

Merged
merged 3 commits into from
Sep 11, 2024

Conversation

jaehunkim
Copy link
Contributor

According to the stone code, there was a difference in implementation when using Keccak256 as PRNG versus using Poseidon3 as PRNG, specifically in whether to view the random bytes array as a value with Montgomery form (aR) applied or not. This code modifications are to reflect this.

@varunthakore It's likely that we'll need to modify the test code related to the Merkle tree.

@jaehunkim jaehunkim self-assigned this Sep 3, 2024
)),
hex("0x7f097aaa40a3109067011986ae40f1ce97a01f4f1a72d80a52821f317504992"),
hex("0x18bcafdd60fc70e5e8a9a18687135d0bf1a355d9882969a6b3619e56bf2d49d"),
hex("0x2f06b17e08bc409b945b951de8102653dc48a143b87d09b6c95587679816d02"),
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now the values are well-aligned with noninteractive_channel_test.cc

@jaehunkim jaehunkim merged commit e5f0003 into master Sep 11, 2024
2 checks passed
@jaehunkim jaehunkim deleted the dev-mont-fix branch September 11, 2024 09:55
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.

1 participant