bitcoin VS nanodb-specification

51 contributors 🚀 https://github.com/bitcoinknots/bitcoin/blob/v21.2.knots20210629/doc/release-notes.md

Bitcoin Knots. What are the changes/benefits for this project? I'm not familiar with it.

FTR we've narrowed down the issue, so it should not happen again after we can get it fixed: https://github.com/bitcoinknots/bitcoin/issues/30

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?