In order for v2 API in backend to properly work on the client-side - they need to be able to sort txs in "chain-order". And for that we need to store additional fields in DB:
epoch - int number or epoch, zero or positive
slot - in-epoch slot, number in [0, 21599]
ordinal - in-slot tx ordinal number, zero or positive
These fields are also required for some future projects.
Note - failed txs only have epoch and slot, pointing to the slot that was "current" (ongoing) at the point when the tx failed. Failed txs don't have ordinal.
In order for v2 API in backend to properly work on the client-side - they need to be able to sort txs in "chain-order". And for that we need to store additional fields in DB:
epoch
- int number or epoch, zero or positiveslot
- in-epoch slot, number in[0, 21599]
ordinal
- in-slot tx ordinal number, zero or positiveThese fields are also required for some future projects.
Note - failed txs only have epoch and slot, pointing to the slot that was "current" (ongoing) at the point when the tx failed. Failed txs don't have ordinal.