-
Notifications
You must be signed in to change notification settings - Fork 14
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
Implementation smart contract aggregate #93
Conversation
We should aim to split the PRs into smaller chunks. In example one PR related to the schema changes only, and a second introducing the aggregate and so forth. Otherwise I can be a bit hard to understand and go through every line, to make sure nothing was missed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Optional code comments. Feel free to skip whatever you don't agree with.
Purpose
To implement Smart Contract features data needs to be fetched and stored as events. These can then later be mapped to endpoints and visualised in the UI.
Design has been written at: https://concordium.atlassian.net/wiki/spaces/EN/pages/1190199324/Design
Task:
Changes
Added a Smart Contract aggregate which can map data either from node or existing data. Existing data are used by a job, which is run prior to the job which continuously fetched data from node.
Checklist
hard-to-understand areas.