Generating random numbers in solidity based on block hash
My intended contract scenario:
The player makes bets. The contract remembers its block number. Then player again makes a request to the contract with the next transaction and receives the result of his bet based on the hash of his bet block
Is there a vulnerability in this scenario? (not considering miner attacks and a limit of 256 blocks)?
solidity
asked Nov 23 '18 at 3:49
Алекс Кирсанов
323
add a comment |
My intended contract scenario:
The player makes bets. The contract remembers its block number. Then player again makes a request to the contract with the next transaction and receives the result of his bet based on the hash of his bet block
Is there a vulnerability in this scenario? (not considering miner attacks and a limit of 256 blocks)?
solidity
asked Nov 23 '18 at 3:49
Алекс Кирсанов
323
add a comment |
My intended contract scenario:
The player makes bets. The contract remembers its block number. Then player again makes a request to the contract with the next transaction and receives the result of his bet based on the hash of his bet block
Is there a vulnerability in this scenario? (not considering miner attacks and a limit of 256 blocks)?
solidity
asked Nov 23 '18 at 3:49
Алекс Кирсанов
323
My intended contract scenario:
The player makes bets. The contract remembers its block number. Then player again makes a request to the contract with the next transaction and receives the result of his bet based on the hash of his bet block
Is there a vulnerability in this scenario? (not considering miner attacks and a limit of 256 blocks)?
solidity
solidity
asked Nov 23 '18 at 3:49
Алекс Кирсанов
323
asked Nov 23 '18 at 3:49
Алекс Кирсанов
323
asked Nov 23 '18 at 3:49
Алекс Кирсанов
323
asked Nov 23 '18 at 3:49
Алекс Кирсанов
323
asked Nov 23 '18 at 3:49
Алекс Кирсанов
323
323
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
If you ignore miner attacks, then there shouldn't be a problem. The people submitting transactions will not be able to knowingly influence the block or block hash that gets generated with their transaction.
However, this is absolutely something that can be influenced by a miner, so simply ignoring it does not make it less of an attack vector.
answered Nov 23 '18 at 4:59
Shawn Tabrizi
4,8332522
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "642"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fethereum.stackexchange.com%2fquestions%2f62888%2fgenerating-random-numbers-in-solidity-based-on-block-hash%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you ignore miner attacks, then there shouldn't be a problem. The people submitting transactions will not be able to knowingly influence the block or block hash that gets generated with their transaction.
However, this is absolutely something that can be influenced by a miner, so simply ignoring it does not make it less of an attack vector.
answered Nov 23 '18 at 4:59
Shawn Tabrizi
4,8332522
add a comment |
If you ignore miner attacks, then there shouldn't be a problem. The people submitting transactions will not be able to knowingly influence the block or block hash that gets generated with their transaction.
However, this is absolutely something that can be influenced by a miner, so simply ignoring it does not make it less of an attack vector.
answered Nov 23 '18 at 4:59
Shawn Tabrizi
4,8332522
add a comment |
If you ignore miner attacks, then there shouldn't be a problem. The people submitting transactions will not be able to knowingly influence the block or block hash that gets generated with their transaction.
However, this is absolutely something that can be influenced by a miner, so simply ignoring it does not make it less of an attack vector.
answered Nov 23 '18 at 4:59
Shawn Tabrizi
4,8332522
If you ignore miner attacks, then there shouldn't be a problem. The people submitting transactions will not be able to knowingly influence the block or block hash that gets generated with their transaction.
However, this is absolutely something that can be influenced by a miner, so simply ignoring it does not make it less of an attack vector.
answered Nov 23 '18 at 4:59
Shawn Tabrizi
4,8332522
answered Nov 23 '18 at 4:59
Shawn Tabrizi
4,8332522
answered Nov 23 '18 at 4:59
Shawn Tabrizi
4,8332522
answered Nov 23 '18 at 4:59
Shawn Tabrizi
4,8332522
4,8332522
add a comment |
add a comment |
Thanks for contributing an answer to Ethereum Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fethereum.stackexchange.com%2fquestions%2f62888%2fgenerating-random-numbers-in-solidity-based-on-block-hash%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
