This repository was archived by the owner on May 12, 2025. It is now read-only.
Open
Conversation
Collaborator
|
I'm not sure if we need to make the random bytes specific to a contract, since we can actually generate random bytes for all confidential computation. |
Author
|
This doesn't need to be called during a chain transition, I think it's OK to be called offline only. But the point is every off-chain computation will arrive at the same result. An example use case is to generate a public key or address associated with the contract. So you can send encrypted messages to that contract where any execution node can access it, and the contract can also own an account on Eth L1 for example |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
inspiration:
https://docs.oasis.io/dapp/sapphire/precompiles/#generating-pseudo-random-bytes