Research for better scaling solutions around transactions & outputs

[laumair]

Description

In the current design of the wallet library, all transactions and outputs are loaded at once. This is not scalable. Imagine exchanges using the library or firefly with hundreds and thousands of outputs / transactions.

An initial idea from @Thoralf-M is to use timestamps and then always loading transactions based on an upper & lower bound.

Motivation

For a performant and scalable wallet library, this is needed.

Requirements

• Research for solutions for how to tackle this problem;
• Look at other similar packages and how they have solved this problem;
• Discuss with Bee & Hornet team. I am certain they would have good ideas around this problem.

Open questions (optional)

N/A

Are you planning to do it yourself in a pull request?

No