-
Notifications
You must be signed in to change notification settings - Fork 148
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
Fix 500 error encountered with sendTransfer API #5250
Comments
Just dropping this here as i think this could be related to the issue i posted earlier |
Thanks for the report – we'll investigate ASAP today. |
markmhendrickson
changed the title
leather wallet is throwing 500 from ordinals explorer
Fix 500 error encountered with sendTransfer API
Apr 18, 2024
markmhendrickson
added
bug
Functionality broken
bug-p2
Critical functionality broken for few users, with no clear workarounds
area:send
area:api
labels
Apr 18, 2024
alter-eggo
added a commit
that referenced
this issue
Apr 18, 2024
alter-eggo
added a commit
that referenced
this issue
Apr 18, 2024
alter-eggo
added a commit
that referenced
this issue
Apr 18, 2024
Merged
kyranjamie
pushed a commit
that referenced
this issue
Apr 18, 2024
## [6.35.0](v6.34.0...v6.35.0) (2024-04-18) ### Features * filter out runes utxos, closes [#5207](#5207) ([1e02992](1e02992)) ### Bug Fixes * add default runes symbol ([b3109ed](b3109ed)) * check utxo fallback error, closes [#5250](#5250) ([321a00a](321a00a)) * duplicated connect btn, closes [#5255](#5255) ([2655c0f](2655c0f)) * **ledger:** no signer breaking homepage ([7624c0a](7624c0a)) * rpc send transfer data, closes [#5243](#5243) ([1858348](1858348)) * runes ui, closes [#5246](#5246) ([b4dcf87](b4dcf87)) ### Internal * post-release merge back ([75c4f5d](75c4f5d))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are seeing a persistent issue trying to send bitcoin tx from LeatherProvider as a request to ordinals explorer seems to throw a 500 resulting in the rpc call to crash
we have a project going live in < 12 hours. would great if someone could shed some light on this issue or point out if we're doing something wrong here.
The text was updated successfully, but these errors were encountered: