-
Notifications
You must be signed in to change notification settings - Fork 186
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
User rejected the transaction firing incorrectly #8128
Open
Labels
Comments
purelycrickets
added
bug
Something isn't working
needs engineering
Requires engineering input before bounty
labels
Nov 14, 2024
For reference:
|
1 task
github-project-automation
bot
moved this from Up next / groomed
to Done
in ShapeShift Dashboard
Nov 15, 2024
User reached out again with a new Jam. Still blocked but with a new error message this time: {"error":{"date":1731951725910,"message_type":"FAILURE","message_enum":3,"message":{"code":9,"message":"Encountered invalid prevhash 2"},"from_wallet":true}} |
github-project-automation
bot
moved this from Done
to Up next / groomed
in ShapeShift Dashboard
Nov 18, 2024
|
gomesalexandre
moved this from Up next / groomed
to In progress
in ShapeShift Dashboard
Nov 19, 2024
This was referenced Nov 19, 2024
feat: bump @shapeshiftoss/bitcoinjs-lib to upstream bitcoinjs-lib@7.0.0-rc.0
shapeshift/hdwallet#694
Draft
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Overview
Jam from an affected user that is getting the 'User rejected the transaction' error as something not related to the address validation endpoint.
References and additional details
Native wallet user, DOGE chain:
https://jam.dev/c/5d4c64b5-5085-486e-b94e-a5329c9e5730
Error that fires: Error: failed to add input: Error: RangeError: value out of range
Acceptance Criteria
User is able to interact with their DOGE without the 'user rejected the transaction' error blocking them from interacting with their funds.
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response
The text was updated successfully, but these errors were encountered: