heed VS nanodb-specification

At Meilisearch we are currently trying to add a better error handling in heed v0.20, our LMDB key-value store wrapper. Unfortunately, when there are a lot of generics it can become harder to play with…

There are issues and pull requests but I advise you to look at the milli folder in the Meilisearch repository, it’s where all the logic is done. We extensively use RoaringBitmaps, heed the LMDB wrapper and grenad when indexing.

I’ll continue to introduce new features and new safety guards until v0.20.0. Can you tell me more about your project? Or is it private?

LMDB support multiple readers and one writer at the same time. It is ensured by the library. Note that LMDB is a key-value store. You can use the heed library which is the most maintained Rust wrapper.

Note that heed is ensuring that you are not trying to use transactions, databases and environments in the right way. I have added much more work in that regard in the important update that I am working on too!

I am currently working on exposing the new LMDB encryption feature from heed the safe LMDB wrapper with the help of the Cryptography community.

Have you considered heed or even sanakirja?

rkv hasn't been updated for a while. I recommend using heed - https://docs.rs/heed

For wrappers around LMBD, I'd recommend RKV or Heed https://github.com/mozilla/rkv https://github.com/Kerollmops/heed

Hello all. I'm having some issues using https://github.com/mozilla/rkv wrapper for LMDB database operations. I want to read a table called 'accounts' from a cryptocurrency's ledger database file (specifically the nano ledger). There is an example doing this in python here in the sample folder if it might help, but I can't translate much over myself that has proved useful.

And besides, Bitcoin nodes aren’t incentivized either. I see you’re an ETH fan though, so we can use that as an example instead. Eth is at 860 GB of storage and their nodes aren’t directly incentivized either. So why is it only an issue for NANO? I don’t know how much space ETH transactions take but I was actually mistaken about NANO’s. Since NANO requires two blocks for a full confirmation (send and receive), it would be 432 bytes(216 each block) between two already existing accounts. I believe new accounts take space as well but let’s just use the 58.8 GB current ledger size divided by the current amount of blocks per nano looker and you have roughly 478 bytes per transaction. So roughly 8.72TB a year if we see it do 50 million transactions a day. And mind you this is a simple SoV/MoE coin, not a smart contract platform. I would be shocked if it did 50 million transactions a day anytime soon, even if it saw widespread success. But again, I foresee ETH’s ledger size increasing much more rapidly so why is it that the lack of direct incentive for running a node is only an issue for NANO?