Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Ergo connector: Large (>Number.MAX_SAFE_INTEGER) quantities in txs render them unsignable.
See original GitHub issueHey guys. I want to use sign_tx method for send 2 tokens in one TX. After I enter the spending password, nothing happens. Promise just has ‘pending’ state.
If I reject this TX, I can catch ‘reject’ state.
- State after opened yoroi-dapp-connector window.
- State after close yoroi-dapp-connector window.
- State after opened yoroi-dapp-connector window.
- State after entered and confirmed spending password.
Issue Analytics
- State:
- Created 2 years ago
- Comments:15 (11 by maintainers)
Top Results From Across the Web
Number.MAX_SAFE_INTEGER - JavaScript - MDN Web Docs
The Number.MAX_SAFE_INTEGER constant represents the maximum safe integer in JavaScript (2 53 – 1). For larger integers, consider using BigInt .
Read more >What is JavaScript's highest integer value that a number can ...
The largest exact integral value of this type is Number. ... MAX_SAFE_INTEGER; ... say, log these numbers to the console, they will get...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It looks like the types for sigma-rust’s JSON parsing is now
number | stringas well. I’ll try just removing the check/conversion then and we’ll see what happens.Internally we use it for calculations, but for the JSON passing to/from the dApp we have it as
number | string. However, the sigma-rust json parsing expects (or was expecting at the time of writing) onlynumberwhich is why we had that conversion + error.