This task is about to create the wallet notification server as well as the service processing the Concordium blockchain.
The purpose of the wallet notification service is to track the events that induces transfers to a given account without such account being involved in the event. This does not include the database intersection with the list of such accounts to devices.
The purpose of the server is to have a way in which we can know of the account to device mappings. This again does not include the database involvement, and neither does it include the authorisation to the server.
The requirements in terms of hosting is that the service should only have a single instance running which may be down whereas the server may not have downtime.
Changes
Adding two different services
Setting up local dev
Writing a README
Tasks:
https://linear.app/concordium/issue/MIS-70/wallet-notification-server https://linear.app/concordium/issue/MIS-68/process-events-from-chain
It is out of scope for this PR to derive the token_id from the events. Those belong to https://linear.app/concordium/issue/MIS-74/derive-token-id
Purpose
This task is about to create the wallet notification server as well as the service processing the Concordium blockchain.
The purpose of the wallet notification service is to track the events that induces transfers to a given account without such account being involved in the event. This does not include the database intersection with the list of such accounts to devices.
The purpose of the server is to have a way in which we can know of the account to device mappings. This again does not include the database involvement, and neither does it include the authorisation to the server.
The requirements in terms of hosting is that the service should only have a single instance running which may be down whereas the server may not have downtime.
Changes
Adding two different services Setting up local dev Writing a README