This adds a python API service that dumps the blockchain to postgreSQL and uses that blockchain to do simple SQL queries to identify the transactions associated with an address. It emulates the same format of the address summary API endpoint to return the proper data.
Linked issue
3409
4211
4213
4215
4217
Type of change
[ ] π Bug fix (non-breaking change which fixes an issue)
[ ] π New feature (non-breaking change which adds functionality)
[ ] β οΈ Breaking change (fix or feature that would cause existing functionality to change)
[ ] π Refactoring that does not change existing functionality but does improve things like code readability, structure etc
[ ] π¨ New or improved tests for existing code
[ ] β git-flow chore (backport, hotfix, etc)
Developer checklist
[ ] I have read the style guide document, and my code follows the code style of this project.
[ ] If my code deals with exceptions, it follows the guidelines.
[ ] I have updated any documentation accordingly, if needed. Documentation changes can be reflected in opening a PR on cardanodocs.com, amending the inline Haddock comments, any relevant README file or one of the document listed in the docs directory.
[ ] CHANGELOG entry has been added and is linked to the correct PR on GitHub.
Testing checklist
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
QA Steps
Screenshots (if available)
How to merge
Send the message bors r+ to merge this PR. For more information, see
docs/how-to/bors.md.
Description
This adds a python API service that dumps the blockchain to postgreSQL and uses that blockchain to do simple SQL queries to identify the transactions associated with an address. It emulates the same format of the address summary API endpoint to return the proper data.
Linked issue
3409
4211
4213
4215
4217
Type of change
Developer checklist
Testing checklist
QA Steps
Screenshots (if available)
How to merge
Send the message
bors r+
to merge this PR. For more information, seedocs/how-to/bors.md
.