We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
downloadBlobberBlock always sets the owner to be the client. This is wrong when a 3rd party pays and the owner is someone else.
The end result seems to be that 0chain read_redeem can fail as it gets confused verifying the signature, assuming the owner has signed it.
read_redeem
The text was updated successfully, but these errors were encountered:
Actually, on investigation, while this is clearly confusing, the cause of the problem was caused by 4f105be#diff-dbc2b4d74b0c2ba20c9c503f9afab19b99134642777fe5c087964942dc7b074a where two feids were added to authTicket and its hash and not mirrored in 0chain. this is fixed in 0chain/0chain#521.
Sorry, something went wrong.
I've included this in coming PR in refactored download.
lpoli
Successfully merging a pull request may close this issue.
downloadBlobberBlock always sets the owner to be the client. This is wrong when a 3rd party pays and the owner is someone else.
The end result seems to be that 0chain
read_redeem
can fail as it gets confused verifying the signature, assuming the owner has signed it.The text was updated successfully, but these errors were encountered: