Skip to content
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

Open price = close price? #29

Open
TheImaginaryOne opened this issue Jun 30, 2021 · 3 comments
Open

Open price = close price? #29

TheImaginaryOne opened this issue Jun 30, 2021 · 3 comments

Comments

@TheImaginaryOne
Copy link

When I run

{
  poolDayDatas(where: {pool: "0x99ac8ca7087fa4a2a1fb6357269965a2014abc35"}) {
    open
    close
  }
}

the close price appears to be the same as the open price for all of the data. (The given pool address is just an example.) Is there a good reason for this to happen, or is it a bug?

@hbriese
Copy link

hbriese commented Apr 10, 2022

This definitely appears to be a bug.
You can see this as the close price for the day should be the open price for day - 1

{
pool(id: "0x7bea39867e4169dbe237d55c8242a8f2fcdcc387") {
    poolDayData(first: 2, orderBy: date, orderDirection: desc) {
      date
      open
      close
    }
  }
}

In concert with looking at the hourly data it appears that the close price is actually the open price
Interestingly the hourly data seems to be correct so it can be used as a workaround

@han-qiu
Copy link

han-qiu commented Aug 13, 2022

#102
There seems to be an attemp to fix it, but never gets reviewed/merged.

@zachwill
Copy link

I'm running across this bug, as well (open and close are the same value).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants