Nanollet VS nanodb

Practically speaking, most wallet applications are dependent on a node to know the state of the ledger. The natrium wallet is connected to the natrium node. The nault wallet randomly chooses a node from a pool of nodes but can be configured to connect to any node. It is possible to design a wallet that doesn't rely on a node and instead connects directly to the network and maintains its own perspective on the state of the ledger locally. I hope to make a proof of concept of that at some point in the near future. This is how the nanollet wallet worked.

A wallet called nanollet has been pointed out to me that was built using a pruned approach but was later abandoned because of the explosion in frontiers and need to keep up with the rapidly changing protocol. This approach appears to make that sort of distributed wallet viable again.

Also — sharing this too incase it's helpful: https://github.com/mistakia/nanodb

There is a project that lets you convert the nano ledger into sql : https://github.com/mistakia/nanodb (also into neo4j)

I'm working on this and creating tools and datasets to make it more accessible for others to do research on this (and ledger analysis in general). I'm setting up new dataset pipeline that should be ready in the next 10 days.

I will at some point provide an API as well. In the meantime, I have the ledger data loaded up in MySQL and would be happy to run some queries and export the results for you.

You can download the ledger and start digging.

I was thinking about using IPFS (via something like Nano IPFS-Log) to maintain and track these accounts. That way IPFS Pubsub can be used to easily propagate new frontiers to all peers.

Improving Nano ledger data accessibility — https://github.com/mistakia/nanodb