-
Notifications
You must be signed in to change notification settings - Fork 40
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
Claim takeover not updated / wrong claim showing controlling
type: bug
Existing functionality is wrong or broken
#108
opened Mar 21, 2019 by
tzarebczan
Update README (and build process?) to be friendlier towards data viz
good first issue
Good for newcomers
help wanted
Extra attention is needed
level: 1
No knowledge of the existing code required
#15
opened May 3, 2018 by
kauffj
Record Reorgs in the database
good first issue
Good for newcomers
#36
opened Jun 14, 2018 by
tiger5226
10 tasks
reorg block with claim update will remove claim
priority: low
Work should be done but can stay in the backlog for now
#43
opened Jul 16, 2018 by
tiger5226
10 tasks
Host db checkpoints every 10K blocks for chainquery
priority: low
Work should be done but can stay in the backlog for now
#50
opened Oct 2, 2018 by
tiger5226
Allow unlimited accounts against api
priority: medium
Work needs to be done within 2-3 sprints
#58
opened Oct 23, 2018 by
tiger5226
10 tasks
chainquery / sdk naming discrepancies
type: improvement
Existing (or partially existing) functionality needs to be changed
#88
opened Feb 1, 2019 by
tzarebczan
Prevent Big Queries
type: discussion
A conversation. No specific changes requested
type: improvement
Existing (or partially existing) functionality needs to be changed
#90
opened Feb 4, 2019 by
tiger5226
encoding issue with btcd.rpcclient
hacktoberfest
Welcome to Hacktoberfest
help wanted
Extra attention is needed
level: 3
Significant knowledge of the existing code is recommended
#5
opened Apr 23, 2018 by
tiger5226
10 tasks
Add cached lbrycrd getnetworkhashps call.
type: new feature
New functionality that does not exist yet
#101
opened Feb 19, 2019 by
tiger5226
Record original claim dates in database
type: improvement
Existing (or partially existing) functionality needs to be changed
#120
opened Jul 28, 2019 by
tzarebczan
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
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
Create column for coalescing for release date and transaction date
#146
opened Apr 1, 2020 by
tiger5226
Decouple chainquery data access from the database and chainquery daemon
#148
opened Apr 22, 2020 by
anbsky
some claims not marked as spent
type: bug
Existing functionality is wrong or broken
#179
opened Nov 1, 2022 by
tzarebczan
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.