<u​nkn8wn69:matrix.org> Hey one question. Does Monerod on loglevel 0 store ANYTHING else about outgoing transactions anywhere? The documentation states the following:

<u​nkn8wn69:matrix.org> "0-4 with 0 being minimal logging and 4 being full tracing. Defaults to 0. These are general presets and do not directly map to severity levels. For example, even with minimal 0, you may see some most important INFO entries."

<u​nkn8wn69:matrix.org> How can I properly secure my node physically?

<u​nkn8wn69:matrix.org> Oh sorry just realized that I'm on Dev

<c​trej:matrix.org> to disable the log completely, you can delete contents of the file and set it to write protected (tested on windows)

<t​rasherdk:monero.social> How about `--log-file=/dev/null` 😬

<u​nkn8wn69:matrix.org> Thanks! I didnt See Option to specify the log file in documentation

<o​frnxmr:monero.social> Thats what i do :D

<o​frnxmr:monero.social> loglevel 0 stores what you see when node is running

<o​frnxmr:monero.social> Reorgs, disconnects, some errors, sync status etc

<o​frnxmr:monero.social> you can change the loglevel and watch the difference live

<o​frnxmr:monero.social> `set_log 1` for example

<r​4v3r23:monero.social> whats the wallet logic for (re)syncing from a certain restore height?

<r​4v3r23:monero.social> from my experience it never syncs from the exact block i set and has a rather large buffer

valldrac

It's to avoid pointlessly scanning all the start of the chain if you know roughly when you created your wallet.

<r​4v3r23:monero.social> moo: i know what a restore height does. thats not my question

<r​4v3r23:monero.social> im asking what happens when restoring from X restore height - is there a buffer of some kind

<r​4v3r23:monero.social> ive never seen a wallet start sycing from the exact height i set

There is a buffer, and I think it is larger when given a date rather than height.

<r​4v3r23:monero.social> whats the reason for the buffer? restore height is very specific

<r​4v3r23:monero.social> it leads to more pointless scanning, especially on tor connection

<o​frnxmr:monero.social> Buffer might be different over restricted rpc, or am i remembering things incorrectly

<o​frnxmr:monero.social> if its bypassable, i assume the --trusted-daemon flag might do that

<o​frnxmr:monero.social> ofrn shutting up now, because i dont know either of these things for a fact. Thx

<v​alldrac:matrix.org> Somehow. It doesn't begin right at the restore height. Instead, the wallet first does a fast refresh, fetching only the block hashes from the most recent checkpoint (or genesis if the restore height is less than the checkpoint), and it keeps doing that until it gets to the restore height. Then, it fetches entire blocks and starts scanning for txs as usual

<v​alldrac:matrix.org> The checkpoint is updated on every release. Latest on mainnet is 2661600 github.com/monero-project/monero/bl…rc/checkpoints/checkpoints.cpp#L242