-
Notifications
You must be signed in to change notification settings - Fork 42
Issues: OdyseeTeam/chainquery
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
some claims not marked as spent
type: bug
Existing functionality is wrong or broken
#179
opened Nov 1, 2022 by
tzarebczan
claim id list incorrect
type: bug
Existing functionality is wrong or broken
#177
opened Aug 19, 2022 by
tzarebczan
effective amount not updated after delay
type: bug
Existing functionality is wrong or broken
#169
opened May 3, 2021 by
tzarebczan
Error: json: cannot unmarshal object into Go struct field SoftForks.softforks of type []*btcjson.SoftForkDescription
type: bug
Existing functionality is wrong or broken
#167
opened Apr 2, 2021 by
stefansundin
Surpassing Max Failures does not cycle with chains of transactions
#159
opened Oct 28, 2020 by
tiger5226
[dev.sh] trying to run from source "fcntl: too many open files" error
#150
opened Jun 2, 2020 by
gubatron
Decouple chainquery data access from the database and chainquery daemon
#148
opened Apr 22, 2020 by
anbsky
Create column for coalescing for release date and transaction date
#146
opened Apr 1, 2020 by
tiger5226
Wrong claim state in database
priority: high
Work needs to be moved into sprint ASAP
type: bug
Existing functionality is wrong or broken
#145
opened Mar 30, 2020 by
tzarebczan
1 task
store purchase information in transaction data (new table)
type: new feature
New functionality that does not exist yet
#138
opened Dec 13, 2019 by
tzarebczan
Record original claim dates in database
type: improvement
Existing (or partially existing) functionality needs to be changed
#120
opened Jul 28, 2019 by
tzarebczan
Claim takeover not updated / wrong claim showing controlling
type: bug
Existing functionality is wrong or broken
#108
opened Mar 21, 2019 by
tzarebczan
Previous Next
ProTip!
Type g p on any issue or pull request to go back to the pull request listing page.