Generating random numbers in solidity based on block hash
up vote
1
down vote
favorite
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 at 3:49
Алекс Кирсанов
273
add a comment |
up vote
1
down vote
favorite
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 at 3:49
Алекс Кирсанов
273
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
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 at 3:49
Алекс Кирсанов
273
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 at 3:49
Алекс Кирсанов
273
asked Nov 23 at 3:49
Алекс Кирсанов
273
asked Nov 23 at 3:49
Алекс Кирсанов
273
asked Nov 23 at 3:49
Алекс Кирсанов
273
asked Nov 23 at 3:49
Алекс Кирсанов
273
273
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
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 at 4:59
Shawn Tabrizi
4,1262522
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
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 at 4:59
Shawn Tabrizi
4,1262522
add a comment |
up vote
2
down vote
accepted
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 at 4:59
Shawn Tabrizi
4,1262522
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
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 at 4:59
Shawn Tabrizi
4,1262522
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 at 4:59
Shawn Tabrizi
4,1262522
answered Nov 23 at 4:59
Shawn Tabrizi
4,1262522
answered Nov 23 at 4:59
Shawn Tabrizi
4,1262522
answered Nov 23 at 4:59
Shawn Tabrizi
4,1262522
4,1262522
add a comment |
add a comment |
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
