You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When there are multiple transactions in the same block, the ordering becomes non-deterministic. This can be problematic in multi-node setup, when multiple instances of kupo may return data in different ordering and there is currently no good way of ordering them. Cardano-db-sync solves this by block_index field. Introducing block_index would resolve this.
Why is it a good idea?
To be able to retrieve txs ordered in a deterministic fashion.
Thanks for considering this ✨ !!!
The text was updated successfully, but these errors were encountered:
Describe your idea, in simple words.
When there are multiple transactions in the same block, the ordering becomes non-deterministic. This can be problematic in multi-node setup, when multiple instances of kupo may return data in different ordering and there is currently no good way of ordering them. Cardano-db-sync solves this by
block_index
field. Introducingblock_index
would resolve this.Why is it a good idea?
To be able to retrieve txs ordered in a deterministic fashion.
Thanks for considering this ✨ !!!
The text was updated successfully, but these errors were encountered: