Change Details

A group can be "address", or "SLP token ID" or other protocols. This struct allows us to conveniently and generically index the tx history of all such groups. The legacy Chronik indexer only allowed indexing by script/address, however, many people have been asking to add support to index by other predicates. Since the tx history for some addresses is already +1M, we store the history paginated. This also allows APIs to more easily and efficiently serve paginated tx history. Txs can be grouped by implementing `Group` on some struct, which then receives `GroupQuery`s, and returns `Member`s, which are then grouped and sorted into the DB.

A group can be "address", or "SLP token ID" or other protocols. This struct allows us to conveniently and generically index the tx history of all such groups. The legacy Chronik indexer only allowed indexing by script/address, however, many people have been asking to add support to index by other predicates. Since the tx history for some addresses is already +1M, we store the history paginated. This also allows APIs to more easily and efficiently serve paginated tx history. Txs can be grouped by implementing `Group` on some struct, which then receives `GroupQuery`s, and returns `Member`s, which are then grouped and sorted into the DB. Depends on D13498.

A group can be "address", or "SLP token ID" or other protocols. This struct allows us to conveniently and generically index the tx history of all such groups. The legacy Chronik indexer only allowed indexing by script/address, however, many people have been asking to add support to index by other predicates. Since the tx history for some addresses is already +1M, we store the history paginated. This also allows APIs to more easily and efficiently serve paginated tx history. Txs can be grouped by implementing `Group` on some struct, which then receives `GroupQuery`s, and returns `Member`s, which are then grouped and sorted into the DB. Depends on D13498.