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

imp: consistent encoding of sp1 inputs #252

Merged
merged 4 commits into from
Feb 3, 2025

Conversation

srdtrk
Copy link
Member

@srdtrk srdtrk commented Feb 2, 2025

Description

closes: #132


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.

  • Linked to GitHub issue with discussion and accepted design, OR link to spec that describes this work.
  • Wrote unit and integration tests.
  • Added relevant natspec and godoc comments.
  • Provide a conventional commit message to follow the repository standards.
  • Re-reviewed Files changed in the GitHub PR explorer.
  • Review SonarCloud Report in the comment section below once CI passes.

Copy link

codecov bot commented Feb 2, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.47%. Comparing base (ec5227e) to head (d947c08).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #252   +/-   ##
=======================================
  Coverage   99.47%   99.47%           
=======================================
  Files          12       12           
  Lines         572      572           
=======================================
  Hits          569      569           
  Misses          3        3           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

bincode = { workspace = true }
serde_cbor = { workspace = true, features = ["std"] }
prost = { workspace = true }
Copy link
Member Author

Choose a reason for hiding this comment

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

I decided that we either use protobuf encoding (convenient for ibc types) or ethereum abi encoding (convenient for contracts). There is no "clean" way to use just one of these in my opinion. And this keeps the code clean as well

Comment on lines +23 to +25
// Re-export the supported zk algorithms.
pub use ibc_eureka_solidity_types::msgs::IICS07TendermintMsgs::SupportedZkAlgorithm;

Copy link
Member Author

Choose a reason for hiding this comment

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

I moved this to a separate line. (No new logic here)

@srdtrk srdtrk marked this pull request as ready for review February 3, 2025 15:12
Copy link
Contributor

@gjermundgaraba gjermundgaraba left a comment

Choose a reason for hiding this comment

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

💥 LGTM!
Clean and nice!

@gjermundgaraba gjermundgaraba merged commit 1b9a151 into main Feb 3, 2025
61 checks passed
@gjermundgaraba gjermundgaraba deleted the serdar/132-consistent-encoding branch February 3, 2025 15:17
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.

Use a consistent encoding for the inputs of the sp1 programs
2 participants