Skip to content
This repository was archived by the owner on Jun 11, 2025. It is now read-only.

feat: Implement changes for handling new types #456

Merged
merged 22 commits into from
Apr 14, 2025
Merged

feat: Implement changes for handling new types #456

merged 22 commits into from
Apr 14, 2025

Conversation

goshawk-3
Copy link
Contributor

@goshawk-3 goshawk-3 commented Apr 3, 2025

Description

This is a placeholder PR used to track changes, monitor merge conflicts, and rebase new-types when needed

@cla-bot cla-bot bot added the cla-signed label Apr 3, 2025
@goshawk-3 goshawk-3 changed the title New types feat: Implement changes for handling new types Apr 3, 2025
@PacificYield PacificYield force-pushed the new-types branch 2 times, most recently from 00057c6 to 787aff7 Compare April 4, 2025 14:25
@dartdart26 dartdart26 force-pushed the new-types branch 2 times, most recently from d884fb0 to 3fe3965 Compare April 10, 2025 10:09
@goshawk-3 goshawk-3 marked this pull request as ready for review April 14, 2025 08:43
@goshawk-3 goshawk-3 requested a review from a team as a code owner April 14, 2025 08:43
PacificYield and others added 18 commits April 14, 2025 17:48
* feat: add chainId to handles

* chore: test adjustment EncryptedERC20.FHEGas
* refactor: updates FheType and validation checks

* chore: autogenerated lib
* chore: prelease 0.7.0-5

* chore: updates description
Add a 64 bit chain ID unsigned value (in big endian) to the handle,
making the handle format the following, in order from first to last byte:

 * 21 bytes from hashing the ciphertext
 * 1 byte index
 * 8 bytes of chain ID
 * 1 byte of ciphertext type
 * 1 byte of version

Resolves: #436

Implementation taken from the following PR from @goshawk-3:
https://github.com/zama-ai/httpz-backend/pull/458/files#

Changing the chain ID type from i32 to u64 throughout the codebase will
be done in a separate commit.
@goshawk-3 goshawk-3 merged commit c3e0c31 into main Apr 14, 2025
23 checks passed
@goshawk-3 goshawk-3 deleted the new-types branch April 14, 2025 15:30
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants