Is there a main usage goal in mind?
Some thoughts are:
1. when i see other addresses i want to explore those as well, perhaps see how it relates.
2. add time ordered replay
Separating scalable transaction storage from graph compute opens a lot. The new Google Spanner Graph launch is interesting here, and for OSS, we have been working on GFQL so you can bounce between vectorized Python dataframe mode on small graphs to 1B row GPU batches for bigger graphs.
Tangentially related but https://trueblocks.io/ is a great project if you have personal use-cases.
ClickHouse is an excellent database, provided you don't need to traverse graphs. Graph traversal requires many queries, and frequent disk interactions can significantly degrade performance.
The feature I'm working on is finding paths between 2 wallets. However, I was forced to remove it because it's not stable enough and consumes too many resources.