NoUJoe
NoUJoe
node-fetch: v2.6.6 **Only in v2, v3 is fine.** If there is an error **after** we receive the initial http response, but before the body of the response has been received....
Library does not use any http compression. I.e `Content-Encoding` header. Using compression would save bandwidth for both you and binance servers.
Some API calls do not use options that you set. For example, `binance.prices ()` vs `binance.prevDay ()`: `binance.prevDay ()` **does** follow the options that you set because of the following...
I've been running a test project to get familiar. I was briefly disonnected from my wifi when moving my laptop, which lead to this. When my app attempted to reconnect,...
https://bscscan.com/address/0xd32db42675c921531d4faa925e82be2c85845f6e#readContract at time of writing: "sqrtPrice": "76243620223535651510009976419", "tick": "-769", According to TickMath.getTickAtSqrtRatio(). tick should be -768. I know -769 has 69 in it but it's still incorrect (I think)
Been testing Pool. Long story short, I discovered something odd when timing the performance of some functions. I've made a gist for replication: https://gist.github.com/NoUJoe/d57b3d478767dd409bab7e8f6aff44e0.js The code sets up a pool,...
I've found what I believe to be a "corrupt" pool on BSC. The SqrtPrice is 0 on the contract and from subgraph. Tick is `null` on subgraph. Here's the explorer...
I've posted this on the discord, but haven't received any acknowledement as of yet. Upon investigation, I've discovered the cause the problems described. Here's the original post that I posted...
This is really minor, I will admit. However incorrect, is incorrect. And it bugged me enough so here it is. https://docs.uniswap.org/sdk/v3/guides/quoting Doc states: > We use a batch Promise call....
See: https://github.com/Uniswap/v3-sdk/issues/182 for full breakdown of the issue. What it boils down to is token0Price and token1Price are incorrectly calculated. I've had a look through, and located the main problem....