Skip to content
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

Question on your Whitepaper #1

Open
kpeluso opened this issue Feb 1, 2020 · 1 comment
Open

Question on your Whitepaper #1

kpeluso opened this issue Feb 1, 2020 · 1 comment

Comments

@kpeluso
Copy link

kpeluso commented Feb 1, 2020

Hello,

I came across your randomity engine and I have 2 questions.

  1. You state the following in your corresponding whitepaper:

The problem here is after all the mixed hashing the creator of such smart contract will identify what the outcomes of certain blocks are and hence may use this to their advantage. Therefore, no entity will use such a facility as it is imperative and necessary to provide a degree of freedom and customisations to the random number end users.

Can you elaborate on what you mean by this? Particularly the latter sentence; why will no entity use this in a bad way / game this system in this way?

  1. Have you done any formal verification / related demonstrations of how this is scheme is resistant to various attacks like front-running, etc.?

Thanks for your time!

@FinagleLord
Copy link

Curious why the contracts are closed source, in my opinion, this makes the engine look malicious. For example, how can anyone be sure that its not random, and you don't have the only knowledge of breaking it.

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

No branches or pull requests

2 participants