04:21:48 U sure youre sure? 04:21:54 Not 100% 04:21:57 Bad wording 04:22:07 Maybe I should test it 04:22:38 From the what remember reading was that it actually can get slower 04:22:51 Oh. Could you link it? 04:22:58 I made a naive conclusion 04:23:22 I'd have linked it if i has any idea where i read it 😆, sorry 04:23:34 Was like.. maybe 1 year ago 09:05:56 just 3 ideas: bounding a specific set of treads to each cpu core, using more minimalistic os, disable any energy saving features if there is any 14:51:50 Hey, I had a software wallet and then sent the balance I had to the cli-wallet but now it's not appearing on the cli - have I messed up something? (Download was from getmonero.org) 14:59:11 Make sure your daemon is synced, that your wallet has refreshed from it after synced, that the wallet's refresh-from-height is lower or equal to the earliest block you used that wallet. 15:24:59 Thanks, I forgot to sync daemon 16:06:19 Hello community 16:08:29 wrong room 16:08:44 you want to be in #monero-community:monero.social 17:34:38 where does the Monero GUI get the addresses of remote nodes from? Is it from node.moneroworld.com DNS records? 17:35:30 No 17:35:50 From the network (--public-node) 17:36:56 Gui in simple mode runs with `--no-sync --bootstrap-daemon=auto`. This connects to peers and looks for peers that have added --public-node to their nodes 17:37:28 It then uses the `--no-sync` monerod to proxy rpc requests to those `--public-node` peers 17:39:14 gui in simple bootstrap mode runs without `--no-sync` (so it syncs the blockchain), but it still uses `--bootstrap-daemon=auto` to find random `--public-node` nodes to connect and proxy rpc connections to 17:41:12 Alright, thanks for the clarification o​frnxmr!