Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with keccak
Search options not deleted
user 126112
keccak is a cryptographic family which is used in ethereum and nowerdays provides the standards for sha-3
0
votes
2
answers
33
views
Hashes don't seem to match even though created with the same params
I have a function in Solidity that is supposed to check if the recovery hash committed by the Email recovery service matches the hash generated through the token and nonce sent by the user (He receive …
0
votes
Hashes don't seem to match even though created with the same params
It worked when I created the emailVerificationHash in the contract's commitRecoveryHash(...) instead of sending the hash from the test suite directly.
Here's how the commitRecoveryHash() is modified:
…
0
votes
Accepted
Hashes don't seem to match even though created with the same params
The hash was being created using a uint64 nonce in the test file whereas in the contract it was generated using uint256 nonce. Since the data type of nonce was different, the hashes were different.