10:44:18 any online? 10:45:29 monerod stagenet not syncing nearly 4hours 10:45:45 am i only one who getting this problem? 10:46:30 Sometimes sync is starting but host is directly blocking. Prompt: Host 18.194.***.** blocked. 10:51:47 Are you using a recent build ? Like, a couple weeks old at most or so ? It might have forked. 10:52:15 (not sure it has yet, but it's possible) 11:47:26 Good morning, I just synced all the Daemons on a new install of GUI but the Advanced setting tab is not visible. What can I do? 11:48:19 When you start the gui, you need to pick "advanced mode" instead of simple/intermediate 11:48:29 There's an option to switch somewhere, in the settings I think? 11:54:08 Found it!, The wallet had to be closed first in Settings to change the wallet mode :)  Thank you. 11:57:41 You're welcome! 12:12:26 Hi guys. I have a doubt. I have a pruned node which i made public in my linux box with the following options: --rpc-restricted-bind-ip 192.168.1.22 --rpc-restricted-bind-port 18081 --rpc-bind-ip 127.0.0.1 --rpc-bind-port 18081 --confirm-external-bind --public-node --detach. I opened the ports 18080 and 18081 in my firewall and router and I can access it from the outside. So my question is, what is 12:12:32 the use of the 18089 port? Should I also port forward this one also? 12:14:44 The restricted rpc port must be different from the unrestricted one 12:15:02 The convention is to use 18081 for unrestricted, and 18089 for restricted 12:15:19 And never expose the unrestricted to the internet 12:15:34 Only expose the unrestricted (18089) 12:15:58 (Expose == port forward on the router) 12:16:19 merope: Thanks for your reply. So, I am doing it wrong? 12:18:52 If I understand correctly I should not expose the 18081 12:22:44 Just change the port in --rpc-restricted-bind-port to 18089 and you should be fine 12:22:44 Correct. 12:22:54 (And change the router's port forwarding settings accordingly) 12:23:40 moneromooo: does monerod even start if you specify the same port number for both restricted and unrestricted? 12:24:07 ok. Thanks guys! 12:24:15 Or does it start anyway, but with only one of the two options active? 12:24:23 technically, it should be possible to bind same port seprately on two different IPs 12:25:02 Oh right, I forgot that the bind does not include localhost 12:26:17 So the parameters were technically correct, albeit non-conventional 12:28:05 sech1: is there a way to identify the mining pool from the mining blob received by xmrig? 12:29:06 Or at least, tell if two blobs belong to the same pool (assuming same height) 12:29:38 not with 100% certainty 12:30:21 the only thing you can compare is the block template timestamp (assuming same height) 12:30:34 but even two nodes in the same pool can have different timestamps 12:30:43 IIRC at least one includes (or included) advertisement in their template... 12:31:00 in tx extra? It's not visible in xmrig's blob 12:31:04 So if you don't care about impersonation, you could tell this one. 12:31:15 Oh. 12:31:16 the blob only has merkle hash instead of full block template 12:32:36 of course there's also metadata, like when you receive the blob with millisecond precision - you can then compare when other pools sent their blobs (these times differ quite a lot, sometimes up to a second) 12:33:49 oh right, there's also transaction count visible in xmrig 12:34:11 but it's the same most of the time across different pools 12:35:13 Ok, interesting 12:35:40 I'm trying to tell if the Unmineable pool is just a proxy for Minexmr 12:36:33 Because their claimed "average time between rewards" quoted figure would only make sense if they owned 40% of the nethash - which is what Minexmr does 12:36:40 then you need to connect to a specific minexmr node and compare blob receive times and number of transactions 12:36:44 xmrig shows both in the log 12:36:53 just run two xmrig windows side by side 12:37:01 Same thing for their kawpow pool, which I suspect to be a proxy for 2miners 12:37:16 (But their eth and etc pools don't seem to follow this pattern) 12:37:25 minexmr has many nodes, check them one by one 12:38:31 I guess I should expect a small but consistent delay between the minexmr template and the unmineable template (ie unmineable's ping distance from minexmr), and unmineable to never preceed minexmr 12:38:43 yes 12:39:13 Got it, thanks 12:39:21 Trail of Bits does a deep dive into mainstream blockchain adoption and discovers widespread vulnerabilities: https://www.reddit.com/r/Monero/comments/vhcd5b/trailofbits_analyzes_mainstream_blockchain/ 12:41:13 merope the delay method can be unreliable if you and unmineable use different minexmr nodes, or if unmineable chooses a random one for you every time 12:46:19 But it should be consistent within mining sessions, assuming the node doesn't change halfway on either side 12:49:06 I think transaction count is more reliable. If you get the same number in each blob from both, you can be sure it's the same node 12:52:07 Oh right, because I could have two different offsets between two different minexmr nodes