Check out the Issue Explorer
Looking to fund some work? You can submit a new Funded Issue here.
The current system sends events directly via sqs, and then the std_bounties client responds directly to the messaged events.
As we want to include more realtime systems in response (ie. stats and more to come), we are running into the issue of how we accomplish it without resyncing everything to the blockchain and passing through the events via sqs. In addition, we want to store the actual events that have passed in a table for analytics reasons.
A good solution to everything is to store the events in a table and use this table to resync. This will require a refactor of the current system.
# Definition of Done
- Events are stored
- No need to resync data with having to re-initiate the sqs queue
@mbeylin and myself
# Review Requirements
A WIP pull request along the way with initial progress
Key questions posted here
Conversational and longer discussions should be directed to the bounties network slack in this channel: https://bountiesnetwork.slack.com/messages/community-dev