Open
Conversation
KryptSai
changed the title
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
1 participant
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 introduces an encryption layer to the bidding contract. In the current implementation, bidders submit unencrypted bids, their competitors can view these bids and adjust their own bids accordingly, creating an unfair advantage. To address this issue, this PR enables bidders to submit their bids in an encrypted format.
Bidders will encrypt their bids using the deployer's public key. Only the deployer will be able to decrypt the bids using their private key, ensuring confidentiality. After decrypting the bids, If the latest bid is higher than the previous highest bid, the state file gets updated with the latest bid amount.
Test cases:
I have tested this code by giving multiple different inputs, it is working fine.