Skip to content
This repository was archived by the owner on May 12, 2025. It is now read-only.

spec for speudorandom generation#51

Open
amiller wants to merge 1 commit intomainfrom
amiller-pr
Open

spec for speudorandom generation#51
amiller wants to merge 1 commit intomainfrom
amiller-pr

Conversation

@amiller
Copy link

@amiller amiller commented Oct 31, 2023

@Ruteri
Copy link
Collaborator

Ruteri commented Oct 31, 2023

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.
What's the use case for calling this precompile during chain transition?

@amiller
Copy link
Author

amiller commented Oct 31, 2023

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

@amiller amiller changed the title spec for speudorandom genreation spec for speudorandom generation Oct 31, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants