Skip to content

Observe any chain structure

Mateusz Tyszczak requested to merge tm-squash-listeners-per-event-type-queen into main

This MR introduces architecture decisions made in the project:

  • separation of data structures exposed to bot implementations from chain APIs. That allows flexibility if chain API will change - such abstraction layer allows to perform needed conversions
  • internal (future) ability to add separate source for data collectors. Right now they work with JSONRPC chain APIs. It should be quite easy to change them to REST APIs. Also it should be possible to implement SQL based sink (most of data aquired by workerbee is operation/account based), so tracking such data by haf pp should be not big problem
  • designed internal quasi ORM which allows to build complex filter conditions and dynamically typed data providers, then exposing typed data structures to bot handlers
  • stable "scenario driven" public interface (for most common use) to quickly and simply write a bot without days of reading docs
Edited by Bartek Wrona

Merge request reports