Skip to content

chore(entropy) Protocol design edit #446

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Oct 9, 2024

Conversation

aditya520
Copy link
Member

I added some links to the text as these parts of the code are asked by the devs.
Let me know if they looks good. We can add more if it seems right.

@aditya520 aditya520 requested a review from m30m October 8, 2024 20:52
Copy link

vercel bot commented Oct 8, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 9, 2024 3:55pm
documentation ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 9, 2024 3:55pm

@aditya520 aditya520 changed the title chore(entropy) Protocol design ediy chore(entropy) Protocol design edit Oct 8, 2024
Copy link
Contributor

@m30m m30m left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot!

3. After sufficient block confirmations, the provider submits a reveal transaction with $x_i$ and $x_U$ to the contract.
4. The contract verifies $\mathrm{hash}(x_U) = h_U$ and $\mathrm{hash}(x_i) = x_{i-1}$ to prove that $x_i$ is the $i$'th random number.
5. If both of the above conditions are satisfied,
the random number $r = \mathrm{hash}(x_i, x_U)$ is generated and a callback is made to the requesting contract.

This protocol has the same security properties as the 2-party randomness protocol above: as long as either
the provider or user is honest, the number $r$ is random.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can add the following to the end of this paragraph like before:

Note that providers need to be careful to ensure their off-chain service isn't compromised to reveal the random numbers -- if this occurs, then users will be able to influence the random number $r$.

@aditya520 aditya520 merged commit a740dd2 into main Oct 9, 2024
5 checks passed
@aditya520 aditya520 deleted the chore(entropy)-protocol-design-edit branch October 9, 2024 16:31
YaserJazouane added a commit that referenced this pull request Oct 11, 2024
* remove mention of pgas

* Revert "Merge branch 'main' of https://github.com/pyth-network/documentation"

This reverts commit b2cc20f, reversing
changes made to 20caa0e.

* chore(entropy) Protocol design edit (#446)

* chore(entropy) Protocol design ediy

* improvements

* improvements

* chore(pricefeed) Add unichain sepolia (#447)

* fix(pricefeed) Fix unichain address (#448)

* initial commit

---------

Co-authored-by: Aditya Arora <arora.aditya520@gmail.com>
aditya520 added a commit that referenced this pull request Oct 18, 2024
* remove mention of pgas

* Revert "Merge branch 'main' of https://github.com/pyth-network/documentation"

This reverts commit b2cc20f, reversing
changes made to 20caa0e.

* chore(entropy) Protocol design edit (#446)

* chore(entropy) Protocol design ediy

* improvements

* improvements

* chore(pricefeed) Add unichain sepolia (#447)

* fix(pricefeed) Fix unichain address (#448)

* initial commit

---------

Co-authored-by: Aditya Arora <arora.aditya520@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants