deploy cypress-cli-v0.6.1.20240403.0741.b1cbae4

[nick-bisonai]

cypress-cli-v0.6.1.20240403.0741.b1cbae4

Signature verification

Description

This PR implements submission with proof. Submission with proof can be either passed through SubmissionProxy or through Feed directly. It is possible to submit values with or without proof which can be recognized by verified property of Round struct. The verification is performed within Feed contract. By default, proof is required (proofRequired) for all submission. If one wants to allow submissions without proof, owner has to call setProofRequired(false).

Proof generation

Every node produces proof independently, and shares it with the rest of the node set.

msg = keccak256(abi.encodePacked(submission))
proof = sign(sk, msg)

Reporter collects all proofs and concatenates them into a single continuous bytes memory, which is then submitted with feeds and submissions arguments.

Proof verification

Submitted proofs are verified within Feed contract, where from each proof we extract signer and test whether it is whitelisted. If not, verification fails and currently whole transaction is rejected. This issue will be attended in Bisonai/orakl#1334.

Related follow-up tasks

• Time proof verification orakl#1333
• Proof threshold orakl#1334
• Move verification from Feed to SubmissionProxy orakl#1336

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist before requesting a review

• I have performed a self-review of my code.
• If it is a core feature, I have added thorough tests.

Summary by CodeRabbit

• New Features
  • Introduced a verification system for data submissions, allowing for enhanced data integrity and trustworthiness.
  • Added functionality to require proof of verification for data submissions, improving security measures.
• Enhancements
  • Updated data retrieval functions across several contracts to include verification status, making it easier for users to identify trusted data.
• Tests
  • Adjusted tests to accommodate new verification features and ensure robustness of the verification system.

• PR: 1331