Improve tx monitoring usability #7
Description
With release r23.06 we introduced a preliminary (alpha) solution for real time tx monitoring and notifications (#4). At the moment it has several issues that need to be solved before being usable in production.
Here we list a non exhaustive list of things to improve.
- Only slack notifications are implemented at the moment.
- Tx data is directly read from the node to be as timely as possible with notifications. This leads to problems in the case of btc-like currencies where historical data is needed to resolve the outgoing addresses (the spent coins) to generate outgoing events. The current version uses the gs-database (cassandra) to do that efficiently. This can lead to many non resolvable input addresses and therefore missed outflow events for those addresses if the gs-database is not synced with a high frequency.
- Notifications are sent out per block and are not batched or bundled somehow. This can lead to a lot of messages if the watch addresses receive a lot of traffic.
- messages set currently contain raw/ unformatted transaction data.