Transactions table should populate recent transactions first

[turbocrime]

On the minifront transactions table, transaction info is streamed to the page.

They populate in essentially random order: they stream in lexical order of their key, which is a base64 encoding of their transaction hash.

Ideally, the most recent transactions known would populate first, and earlier transactions would load as the user scrolls down the page.

[turbocrime]

I experimented with this issue today. Unfortunately it looks like this is impossible given current idb schema constraints

1. we should add an index of transactions by height. this is doable.
2. we should query by this index. this is doable.

But, the index is also a string which sorts in lexical order, because the height in database is a jsonified bigint.

The situation is improved but still clearly incorrect.

Screen.Recording.2024-06-27.at.22.44.46.mov

[turbocrime]

if idb schema used real types instead of stringifying everything, many operations like this would be more sane and just work as expected.

[turbocrime]

if the string key bounds are interpreted lexically instead of numerically, it may not even be possible to achieve numeric ranges with idb key bounds. this could create problems long term.

[TalDerei]

closed by #1996 and more improvements in #2009