-
Notifications
You must be signed in to change notification settings - Fork 2
Issues: hyperledger/indy-read-replica
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
Suggestion: A query without a targeted network identifier that the Replica sorts out
#37
opened Nov 20, 2024 by
swcurran
Support a single config for both the api and daemon
Complexity: high
Likely to be difficult to implement with several unknowns.
Priority: mid
Feature request is a important to our roadmap but can be delayed
#30
opened Oct 30, 2024 by
rxbryan
Pub-Sub API for Indy Read Replica
Complexity: high
Likely to be difficult to implement with several unknowns.
Priority: mid
Feature request is a important to our roadmap but can be delayed
#29
opened Oct 23, 2024 by
rxbryan
Support releasing deployable artifacts
Complexity: mid
Likely to be challenging but manageable.
Priority: high
High priority concern or feature request. Very Important to our roadmap and must be addressed
#28
opened Oct 22, 2024 by
rxbryan
Allowing the upstream nodes to be configured at runtime
Complexity: high
Likely to be difficult to implement with several unknowns.
Priority: mid
Feature request is a important to our roadmap but can be delayed
#27
opened Oct 22, 2024 by
rxbryan
source transactions from an Indy Read replica
Complexity: high
Likely to be difficult to implement with several unknowns.
Priority: high
High priority concern or feature request. Very Important to our roadmap and must be addressed
#26
opened Sep 24, 2024 by
rxbryan
ProTip!
Follow long discussions with comments:>50.