feat(test-suite): use latest solidity library and host-contracts#277
Merged
feat(test-suite): use latest solidity library and host-contracts#277
Conversation
jatZama
changed the title
PacificYield
approved these changes
Jun 13, 2025
jatZama
force-pushed
the
removeEbytesTestSuite
branch
from
afeb72d to
e3e8a26
Compare
paulo-zama
pushed a commit
that referenced
this pull request
Mar 26, 2026
* feat: add chainid column * feat: create db migrations * chore: refactor `fromString` to `from` for better object interface * fix: fake the right event name * fix: this is not a constructor * feat: define chain * feat: add chain id to dapp as a number * feat: enable chain selection * fix: broken tests * fix: broken tests * fix: chain id type * chore: fix submodule version
paulo-zama
pushed a commit
that referenced
this pull request
Mar 26, 2026
* feat: add chainid column * feat: create db migrations * chore: refactor `fromString` to `from` for better object interface * fix: fake the right event name * fix: this is not a constructor * feat: define chain * feat: add chain id to dapp as a number * feat: enable chain selection * fix: broken tests * fix: broken tests * fix: chain id type * feat: compose use cases compose the sign up use case with single step use cases. Each module should expose the use cases and not the repositories * feat: define password reset token * fix: missing exports * feat: define a password reset token repository * feat: send password reset requested event * fix: reset password created payload * feat: add request password reset to resolver * feat: reset password and login * feat: frontend stuff + fix back errors * feat: integrate with orchestrator flow * feat: basic rust implementation * feat: define email domain events * Add chain ID to dApp (#277) * feat: add chainid column * feat: create db migrations * chore: refactor `fromString` to `from` for better object interface * fix: fake the right event name * fix: this is not a constructor * feat: define chain * feat: add chain id to dapp as a number * feat: enable chain selection * fix: broken tests * fix: broken tests * fix: chain id type * chore: fix submodule version * feat(relayer): error handling and fhevm update * feat: expose http port in standalone mode * feat: add unrecoverable error catching in http listener * chore: update relayer based on new fhevm-relayer * chore: update fhevm-relayer and fhevm-test-suite * chore: add logs of ct-handles to debug zws-dev bug (#285) * chore: add logs of ct-handles to debug zws-dev bug * chore: fix rust ci by pinning grcov version * chore: udpate fhevm-relayer to v0.1.0-rc8 (#287) * reset password (#288) * feat: add chainid column * feat: create db migrations * chore: refactor `fromString` to `from` for better object interface * fix: fake the right event name * fix: this is not a constructor * feat: define chain * feat: add chain id to dapp as a number * feat: enable chain selection * fix: broken tests * fix: broken tests * fix: chain id type * feat: compose use cases compose the sign up use case with single step use cases. Each module should expose the use cases and not the repositories * feat: define password reset token * fix: missing exports * feat: define a password reset token repository * feat: send password reset requested event * fix: reset password created payload * feat: add request password reset to resolver * feat: reset password and login * feat: frontend stuff + fix back errors * feat: integrate with orchestrator flow * fix: revert fhevm-relayer commit * Potential fix for code scanning alert no. 13: Workflow does not contain permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com> * feat: remove vulnerabilities (#290) * feat: remove vulnerabilities * fix: image version * fix typo * chore: bump fhevm-relayer-version to rc8 * fix: missing dependency in tests --------- Co-authored-by: manoranjith <manoranjith.ponnuraj@zama.ai> * Improve code (#278) * feat: add chainid column * feat: create db migrations * chore: refactor `fromString` to `from` for better object interface * fix: fake the right event name * fix: this is not a constructor * feat: define chain * feat: add chain id to dapp as a number * feat: enable chain selection * fix: broken tests * fix: broken tests * fix: chain id type * feat: compose use cases compose the sign up use case with single step use cases. Each module should expose the use cases and not the repositories * feat: change password (#292) * feat: setup email sqs * feat: add zapier gateway * fix: remove rust code * feat: email yaml configuration * feat: send email with ses * feat: send reset password email * feat: let define arrays as env variables * feat: expand yaml template with env variables * fix: change yaml template pattern * feat: migrate configuration for orchestrator and web3 * fix: web3 start * fix: after merge errors * fix: ignore no test error * fix: email build --------- Co-authored-by: Luis Montero <17201527+fd0r@users.noreply.github.com> Co-authored-by: Alex Quint <86411313+aquint-zama@users.noreply.github.com> Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com> Co-authored-by: manoranjith <manoranjith.ponnuraj@zama.ai>
paulo-zama
pushed a commit
that referenced
this pull request
Mar 26, 2026
* Av/chain config (#296) * feat: change config to yaml * feat: move chains to config * fix: security code scan * fix: lock out of sync * fix: build * fix: remove the base.yaml file * fix: prisma generate error * fix: tests * user decrypt (#298) * feat: enable user decrypt * feat: enable multiple chain id formats * fix: broken tests * fix: increase length for random generic invalid string * fix: string can be undefined (#303) * remove correlation id for relayer (#304) * feat: remove correlation ID for relayer events * feat: add missing private decrypt workflow * fix: broken test * fix: retrieve the right invitation secret (#306) * send reset password email (#300) * feat: add chainid column * feat: create db migrations * chore: refactor `fromString` to `from` for better object interface * fix: fake the right event name * fix: this is not a constructor * feat: define chain * feat: add chain id to dapp as a number * feat: enable chain selection * fix: broken tests * fix: broken tests * fix: chain id type * feat: compose use cases compose the sign up use case with single step use cases. Each module should expose the use cases and not the repositories * feat: define password reset token * fix: missing exports * feat: define a password reset token repository * feat: send password reset requested event * fix: reset password created payload * feat: add request password reset to resolver * feat: reset password and login * feat: frontend stuff + fix back errors * feat: integrate with orchestrator flow * feat: basic rust implementation * feat: define email domain events * Add chain ID to dApp (#277) * feat: add chainid column * feat: create db migrations * chore: refactor `fromString` to `from` for better object interface * fix: fake the right event name * fix: this is not a constructor * feat: define chain * feat: add chain id to dapp as a number * feat: enable chain selection * fix: broken tests * fix: broken tests * fix: chain id type * chore: fix submodule version * feat(relayer): error handling and fhevm update * feat: expose http port in standalone mode * feat: add unrecoverable error catching in http listener * chore: update relayer based on new fhevm-relayer * chore: update fhevm-relayer and fhevm-test-suite * chore: add logs of ct-handles to debug zws-dev bug (#285) * chore: add logs of ct-handles to debug zws-dev bug * chore: fix rust ci by pinning grcov version * chore: udpate fhevm-relayer to v0.1.0-rc8 (#287) * reset password (#288) * feat: add chainid column * feat: create db migrations * chore: refactor `fromString` to `from` for better object interface * fix: fake the right event name * fix: this is not a constructor * feat: define chain * feat: add chain id to dapp as a number * feat: enable chain selection * fix: broken tests * fix: broken tests * fix: chain id type * feat: compose use cases compose the sign up use case with single step use cases. Each module should expose the use cases and not the repositories * feat: define password reset token * fix: missing exports * feat: define a password reset token repository * feat: send password reset requested event * fix: reset password created payload * feat: add request password reset to resolver * feat: reset password and login * feat: frontend stuff + fix back errors * feat: integrate with orchestrator flow * fix: revert fhevm-relayer commit * Potential fix for code scanning alert no. 13: Workflow does not contain permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com> * feat: remove vulnerabilities (#290) * feat: remove vulnerabilities * fix: image version * fix typo * chore: bump fhevm-relayer-version to rc8 * fix: missing dependency in tests --------- Co-authored-by: manoranjith <manoranjith.ponnuraj@zama.ai> * Improve code (#278) * feat: add chainid column * feat: create db migrations * chore: refactor `fromString` to `from` for better object interface * fix: fake the right event name * fix: this is not a constructor * feat: define chain * feat: add chain id to dapp as a number * feat: enable chain selection * fix: broken tests * fix: broken tests * fix: chain id type * feat: compose use cases compose the sign up use case with single step use cases. Each module should expose the use cases and not the repositories * feat: change password (#292) * feat: setup email sqs * feat: add zapier gateway * fix: remove rust code * feat: email yaml configuration * feat: send email with ses * feat: send reset password email * feat: let define arrays as env variables * feat: expand yaml template with env variables * fix: change yaml template pattern * feat: migrate configuration for orchestrator and web3 * fix: web3 start * fix: after merge errors * fix: ignore no test error * fix: email build --------- Co-authored-by: Luis Montero <17201527+fd0r@users.noreply.github.com> Co-authored-by: Alex Quint <86411313+aquint-zama@users.noreply.github.com> Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com> Co-authored-by: manoranjith <manoranjith.ponnuraj@zama.ai> * Improve config (#308) * feat: ignore keys if are not array indexes * feat: improve config * fix: revert fhevm-relayer * fix: improve tests * chore: update aws clients for supporting irsa creds (#311) * chore: update aws clients for supporting irsa creds Signed-off-by: Ghislain Cheng <ghislain.cheng@zama.ai> * chore(ci): improve ci build Signed-off-by: Ghislain Cheng <ghislain.cheng@zama.ai> --------- Signed-off-by: Ghislain Cheng <ghislain.cheng@zama.ai> * fix: aws client config (#312) Signed-off-by: Ghislain Cheng <ghislain.cheng@zama.ai> * feat: public decrypt (#310) * feat: public decrypt * fix broken tests * fix: test * fix: remove cpx and rimraf * chore: migrate to latest version of fhevm and fhevm-relayer (#307) * chore: migrate to latest version of fhevm and fhevm-relayer * fix: move ses configuration to dedicated key (#320) * fix: move ses configuration to dedicated key * fix: missing endpoint * feat: integrate fhevm-relayer (#319) https://github.com/zama-ai/fhevm-relayer/pull/339 implements the proper SQS interactions to integrate the fhevm-relayer with the Console. `make fhevm-up && make console-build && FHEVM_RELAYER=1 make console-up && make test` can be used to test that everything works fine. Tests are passing when interacting with the Console through SQS. The serialization format of messages is inconsistent between operations. It should be refactored at a later time. `payload` should contain the raw http payload. `requestId` should be at the same level as `payload` and not inside it. User decrypt payload should be consistent with the others. Public decrypt SQS endpoint is not yet tested. * fix: sqs infinite loop in production (#322) * chore: add tests * fix: aknowledge processed messages to prevent infinite loop * fix: explicitly ack the message * Add Trivy summary to Github Job Summary (#221) * chore: adds table summary and print it to github-summary * chore: removes exit-code 1 and get total of vulns, miscfg and secrets * chore: adds colored text in job summary * chore: comments 'exit 1' to avoid enforcing zero-vulns * chore: enables 'exit 1' to enforce zero-vulns in repo * chore: fix typo * chore: disables enforcement zer-vulns * chore: remove discosing of nginx version for front end server (#284) * feat: remove dapp status and deployment (#325) * chore: fixes docker workflow, prefix imagename with console (#204) * * chore: fix clippy * chore: update fhevm-relayer * chore: fix clippy * feat: sign up workflow (#324) * fix: broken tests after useConfigCredentials was introduced * fix: validate contractsChainId * feat: use config service to retrieve feature flags * fix: fail early when frontendUrl is missing * feat: enable signup with email or invitation * feat: move from reset password token to user token * feat: enable signup with email confirmation * fix: send token instead of hash * feat: send confirmation email * feat: forward user created to email * feat: self-served signup frontend (#321) * chore: move signup to invitation * feat: signup form * feat: front signup * feat: validate user email * fix: make revert confirmEmail into a mutation @avitali-zama @fd0r * fix: remove contact support text @stongo * feat: front feature flag (#323) * chore: move signup to invitation * feat: signup form * feat: front signup * feat: validate user email * feat: feature flag to toggle signup link * feat: adjust env vars * Add Trivy summary to Github Job Summary (#221) * chore: adds table summary and print it to github-summary * chore: removes exit-code 1 and get total of vulns, miscfg and secrets * chore: adds colored text in job summary * chore: comments 'exit 1' to avoid enforcing zero-vulns * chore: enables 'exit 1' to enforce zero-vulns in repo * chore: fix typo * chore: disables enforcement zer-vulns * chore: remove discosing of nginx version for front end server (#284) * feat: remove dapp status and deployment (#325) * chore: fixes docker workflow, prefix imagename with console (#204) * fix: broken merge * * chore: fix clippy * chore: update fhevm-relayer * chore: fix clippy * feat: pass fhevm tests + shorten long strings * fix: point to v0.7.0 --------- Co-authored-by: Roger Carhuatocto <chilcano@intix.info> Co-authored-by: Pierre Besson <pierre.besson@zama.ai> Co-authored-by: Alessandro Vitali <alessandro.vitali@zama.ai> Co-authored-by: Luis Montero <17201527+fd0r@users.noreply.github.com> --------- Co-authored-by: Alessandro Vitali <alessandro.vitali@zama.ai> Co-authored-by: Roger Carhuatocto <chilcano@intix.info> Co-authored-by: Pierre Besson <pierre.besson@zama.ai> Co-authored-by: Luis Montero <17201527+fd0r@users.noreply.github.com> * chore: improve passowrd tests (#327) * fix: add missing default value for invitations (#328) * chore: fix docker compose * chore: remove fhevm-relayer submodule (pre-migration) * chore: migrate fhevm-relayer submodules to console submodules * chore: update Cargo.lock to reflect fhevm-relayer migration * chore: move github workflow files * chore: naive github action migration * chore: prefix image name with repo name * ci: prepare relayer ci for release * chore: update relayer docker workflow * ci: update workflow to support mono-repo releases (#516) - The wrong workflow was updated. This time it's the correct one. - For the corresponding change in the ci-templates repo, see zama-ai/ci-templates@4d72229 * feat: add support for extra_data field & decryption_proof - The extra_data field was introduced as a place holder for adding additional information. This field by itself contains the version information. For now, this field is set to 0x00 by all components. - Adapt decryption requests, responses and callback to decryption oracle to handle this correctly. - In decryption responses, instead of signatures, we now include decryption_proof. This fields for now includes signatures and extra_data. - Also, updating the decryption and input proof gateway contract bindings introduced some name changes to fields in the functions used by relayer. Relayer code is updated for this as well. * fix: use tracing! instead of println! * fix: validate & parse extraData from json * fix: use gw chain id from cfg in mock * feat: update calldata scheme for decr callback - The Signature expected was callback function for public decryption is being updated in v0.8.0-2 release of fhevm stack. - Update the calldata construction logic accordingly. * fix: clippy and fmt warnings * chore: bump version to v0.3.0 This relayer release will correspond to fhevm release v0.8.0-2 * fix: rebuild provider/connexion on `BackendGone` errors (#514) * chore: migrate provider from Arc to Arc<RwLock> * chore: refactoring in progress with RwLock provider + reset + wrapper * chore: all calls to provider going through * chore: please clippy * chore: remove console relayer * chore: relayer/fhevm-relayer -> relayer * chore: update github workflow for fhevm-relayer -> relayer * chore: rm unused deps and limit to needed features * feat: use gw bindings from fhevm monorepo * feat: discriminate revert errors * test: migrate tests to 0.8 mock contracts * ci: fix ci * fix: update Makefile API tests with extraData * ci: clean CI setup and set proper requirements for PR status checks [API-681] (#538) * ci: rename trivy workflow * docs: add contributing.md docs [API-661] (#536) * feat: add liveness/healthz/version endpoints [API-630] (#554) * chore: rm gateway-l2 submodule * docs: update tech-spec (lot of work to update it still) (#497) * docs: update tech-spec (lot of work to update it still) * chore: ignore obsidian config file * chore: add changes from discussion * docs: some cleanup * fix(oracle): add same gateway decryption contract bit limitation in oracle [API-695] (#564) The decryption contract on the gateway chain has a constrain on the number of bits per public decryption request. The easiest way to avoid a mismatch between the host and the gateway is to check for this limitation directly in the oracle decryption contract. That being said we should think of another solution in the future. Indeed a contract might need to do an oracle call with a number of bits higher than the current limit. The relayer should be able to split and gather all responses but in the current design in would cause an issue when verifying the signature of the decryption results. * chore: remove old stuff * feat: handle user registered * chore: remove old migrations * fix: remove api key from config * test: add oracle ci + tests * fix: add automatically generated OpenAPI swagger [API-692] * fix: remove prisma from the dockerfile * chore: solve typo * fix: add a default fallback value * chore: remove not used code * Update apps/back/src/modules/webhooks/app/webhooks/webhooks.service.ts Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * chore: code organization * Potential fix for code scanning alert no. 128: Workflow does not contain permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com> * Potential fix for code scanning alert no. 129: Workflow does not contain permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com> * Potential fix for code scanning alert no. 37: Workflow does not contain permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com> * fix: remove old stuff * fix: allows tests to pass with no tests * fix: broken cicd tests * chore: remove old frontend stuff * fix: outdated lock file * fix: broken build * chore: use string for node version * Update apps/back/src/modules/webhooks/app/webhooks.service.ts Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --------- Signed-off-by: Ghislain Cheng <ghislain.cheng@zama.ai> Co-authored-by: Luis Montero <17201527+fd0r@users.noreply.github.com> Co-authored-by: Alex Quint <86411313+aquint-zama@users.noreply.github.com> Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com> Co-authored-by: manoranjith <manoranjith.ponnuraj@zama.ai> Co-authored-by: Ghislain CHENG <ghislain.cheng@zama.ai> Co-authored-by: Roger Carhuatocto <chilcano@intix.info> Co-authored-by: Pierre Besson <pierre.besson@zama.ai> Co-authored-by: Gaspard Beernaert <gaspard@gmail.com> Co-authored-by: Luis Montero <luismontero@hotmail.fr> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR updates the test-suite to use latest version of the
FHE.sollibrary (0.7.0-5) with removal of ebytesXX types. It also uses latest version of host contracts, with updated FHEVMEExecutor (removal of ebytesXX) as well as corresponding updated HCULimit contract, and updated ACL contract, which adds an env variablePAUSER_ADRESSinside the.env.hostfile. Note this last remark is important for ZWS setup.For the upgrade of testnet, we still need to follow same conventions as agreed with gateway team, as current contracts still use
reinitializer(2)with a singlie insitilizer, instead of 2 initializer functions which shoudl be protected viareinitializer(3)instead, this will be done in a futrue PR, according to this issue https://github.com/zama-ai/fhevm-internal/issues/68.