add demo for week7#196
Merged
Merged
Conversation
Collaborator
|
Hi @yyqxdlg Thanks for the proposal. Looking forward to the demo. |
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.
Assignment Proposal
Title
Fair Play in Open Cards: Implementing Commit-Reveal Voting
Names and KTH ID
Deadline
Category
Description
Public blockchains face a "transparency paradox": transparency is good for trust, but bad for game theory. In voting or auctions, if I see your transaction in the mempool, I can copy it (copy-cat voting) or outbid it immediately (front-running).
This demo solves the "Transparency Paradox" (front-running) in blockchain voting using the Commit-Reveal Scheme. I will deploy a voting contract in Remix to demonstrate:
Commit Phase: Submitting a hash of the vote + salt (hiding the choice).
Reveal Phase: Revealing the original data to verify and count the vote.
Live Cheating: Attempting to change the vote during the reveal phase to show how the contract mathematically prevents fraud.
Relevance
This pattern is fundamental for Programmable Society applications that require fairness, such as Sealed-Bid Auctions (like ENS names), Gambling, and privacy-preserving Voting. It demonstrates how to achieve temporal privacy on a completely public ledger without needing complex ZK-proofs.