-
Notifications
You must be signed in to change notification settings - Fork 203
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
Private message fails with "No match for zerohash" #1431
Comments
Initial finding: In this case, the So I need to track back into what might cause |
In the message I can see it's for nonce=1: "pins": [
"80ad901239cc9f914907639fe4e0b19b341a3c03a1da12292f540f8f5fb2859a:0000000000000001"
], |
There is an earlier message with
|
Ok - the problem here is that we are using different signing addresses for the two messages. The second overtakes the first on-chain - because they are on different signing addresses. So the
|
Need to consider what the right answer is to this (code, architectural assurances, programming requirements, or otherwise), given the laws of physics of the blockchain when ordering, and the requirements around ordering. |
Saw this issue repeatedly in a demo application when sending a private message to self. The interesting log is this one:
Some details on the failed message:
e284e1c6-073f-404c-bfb5-2e362efd3590
5941e40a-564b-46c1-8e34-e8b5e206f6ae
28fa55dc-4e18-4762-8f05-e0caaa38b1e2
Full logs: ff.txt
The text was updated successfully, but these errors were encountered: