Torus compression

[JuI3s]

Description

closes: #XXXX

---

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

• Targeted PR against correct branch (master)
• Linked to GitHub issue with discussion and accepted design OR have an explanation in the PR that describes this work.
• Wrote unit tests
• Updated relevant documentation in the code
• Added a relevant changelog entry to the Pending section in CHANGELOG.md
• Re-reviewed Files changed in the GitHub PR explorer

[markosg04]

Great job! Mostly left some questions and nits.

Prior to merging, can we first confirm that Jolt CI passes when swapping the arkworks patch for the compression branch (no need to integrate or anything just want to ensure doesn't break Jolt -- which I don't think it should good to double check).

[markosg04]

how come we renamed this?

[JuI3s]

Again I copied and pasted from the reference implementation in curves (which unfortunately I had to do the copying due to the way arkworks was setup...). I don't know why it's G1Config previously, but I checked the naming "Config" is consistent with the rest of arkworks codebase.

[markosg04]

are we re-implementing this? just a bit confused

[JuI3s]

These are copy-paste from arkworks (unfortunately due to the replication in test-curve and curve I need to copy) which they implement. I didn't touch this part of the code.

[JuI3s]

Great job! Mostly left some questions and nits.

Prior to merging, can we first confirm that Jolt CI passes when swapping the arkworks patch for the compression branch (no need to integrate or anything just want to ensure doesn't break Jolt -- which I don't think it should good to double check).

How do you check "swapping the arkworks patch" work?

[markosg04]

Great job! Mostly left some questions and nits.
Prior to merging, can we first confirm that Jolt CI passes when swapping the arkworks patch for the compression branch (no need to integrate or anything just want to ensure doesn't break Jolt -- which I don't think it should good to double check).

How do you check "swapping the arkworks patch" work?

I think easiest way would just be swap the git link and branch in the Cargo.toml in Jolt with your link and branch

[JuI3s]

Great job! Mostly left some questions and nits.
Prior to merging, can we first confirm that Jolt CI passes when swapping the arkworks patch for the compression branch (no need to integrate or anything just want to ensure doesn't break Jolt -- which I don't think it should good to double check).

How do you check "swapping the arkworks patch" work?

I think easiest way would just be swap the git link and branch in the Cargo.toml in Jolt with your link and branch

I can't seem to do that easily as Dory depends on dev/twist-shout branch, so I would have a dep conflicts. I think it's ready to merge as the test suite for bn254 as is in this crate is pretty extensive.