02:52:50 is there any estimate timeline for fcmp? when can we expect it, next 2 years? 02:53:21 What is fcmp? 02:54:30 main advantage of fcmp is you know how ring signatures for xmr is 1 in 16? 02:54:49 fcmp will make it 1 in billion something so statistical attacks almost impossible. increasing privacy 02:58:20 Interesting 03:35:08 Within next 5 years 03:39:40 <3​21bob321:monero.social> Who is fcmp 03:40:24 Fluffy crab money pony 05:03:30 if 2 miners find blocks at the same time (both blocks are published to the network), then what's the tiebreaker rule? 05:03:31 I always thought it was the block with higher diff that wins the race 05:19:43 <3​21bob321:monero.social> They arm wrestle 05:24:15 There is no tiebreaker. If the chains only differ by one block, they will have equal cumulative difficulty 05:27:55 Tiebreakers can reduce network stability. For example, if the tiebreaker rule was to use the block with the "lower" block ID or PoW hash, then miners, even "honest" ones, who have high network delay would cause frequent reorgs with high delay when they re-mined the top block while the rest of the network has moved onto the next block 05:28:24 Removing the tiebreaker incentives miners to have low block propagation times 05:55:42 interesting 05:55:43 in that case, wouldn't using the block timestamp (the timestamp in the block header) as the tiebreaker be better option? 05:56:39 miners can game that by putting incorrect timestamps on their blocks 05:59:45 you'd end up with timestamps being lower than they're supposed to be, but above the minimum value where they're likely to be accepted by most nodes 11:26:27 "if the chains only differ by one block, they will have equal cumulative difficulty", is this true all the time? If you had two new blocks, wouldn't it be possible one has a higher difficulty than the other making for one chain with a higher cumulative difficulty? 11:35:29 It's always true due to how difficulty adjustment works. There's a lag of at least 15 blocks before any differences can emerge. 13:52:43 apparently, cumulative difficulty is not the summation of block diff but rather, the summation of network difficulty values the blocks had to overcome 13:52:43 in this definition, both chains will have the same cumulative difficulty even though the summation of individual block diff is different 14:35:51 Okay, so my understanding is the important part is that the difficulty adjustment does not take into account the current block. So in a situation where both chains have diverged by one block, its impossible for those divergent blocks to affect cummulative difficulty because cummulative difficulty's definition excludes the current block. So this holds true if there is atleast a 1 b 14:35:53 lock lag when considering difficulty adjustment 14:37:50 i.e. without 1 confirmation have you even won really? 14:47:55 No, two different blocks at the top are equal until someone mines one more block 14:54:43 think we are saying same thing? 15:02:32 "No" was an answer to "have you won" question. So yes, the same thing. 15:03:24 lol i meant it in the meme way like do you even lift bro 18:33:26 Hello. 21:08:32 How do people monitor their public nodes, I'm thinking I might as well just parse access logs to see what rpc resources are being accessed? I don't see any other solutions existing, there is the get_info endpoint but that doesn't help me track the access only the nodes health 21:13:58 <3​21bob321:monero.social> As in people syncing? 21:14:13 <3​21bob321:monero.social> Or access to the server running the node? 21:16:46 ohchase: Does this help? https://github.com/lalanza808/docker-monero-node 21:43:29 Anyone else having trouble reaching the Trocador site? According to their Reddit page, they were resolving a DDOS attack about a month ago. Is the site still down? I can't reach the site on Tor, clearnet or via their i2p or onion link. 21:44:14 Ddos is bad 21:46:55 Trocador.i2p works fine 21:47:43 https://matrix.monero.social/_matrix/media/v1/download/monero.social/BMgpixafMRzwfWpifJtaRKxr 21:50:43 Okay, this is a teaching moment for me! I don't know anything about i2p. I assumed it was like an onion address. I tried getting the Trocador i2p link from KYC.notme, but it didn't connect. Just now I tried the URL in the address bar of your screen shot, and it wouldn't connect. There must be something I don't get about i2p. Would you please school me on how to reach it? 22:16:07 are you on desktop or mobile? 22:36:14 Prefer desktop for this sort of thing 22:37:28 Matter of fact...I would first try to get connected on a Linux Mint desktop. 22:45:50 Youll have to install i2pd 22:46:33 up to you whether you prefer the version in the repo or want to keep up to date manually from git 22:46:53 If repo "sudo apt install i2pd" 22:47:24 Then after it starts up, change your browser proxy setting to 127.0.0.1:4447 22:48:42 its much easier from android. 22:48:43 install invizible, 22:48:45 in inviz, enable dnscrypt + i2p + vpn mode 22:48:47 then use any browser to visit any i2p domain 23:01:31 Wow - thanks so much for the tutorial! Much obliged 🤠 🍻 23:10:43 So i did see this, but looks to just be probing the restricted rpc endpoints. I wanted to track rpc access by endpoint / method if using base json rpc . I was playing around with ddosing my node, and had some good success. At the same time realized, I have limited to no visibility into what is being accessed with my public rpc. Is it one user constantly spamming the same block? etc 23:14:36 kinda, not to deanonymize but for monitoring. Would be nice to flag on weird requests and to monitor for any ddos 23:24:38 ohchase: Maybe `nethogs` 23:27:59 Maybe `wallet.rpc` and/or `wallet.wallet2` log categories: https://www.getmonero.org/resources/developer-guides/daemon-rpc.html#set_log_categories 23:29:14 I have seen comments in the monero code that say "we won't print everything to log so that it's harder to see some private info by default". Of course, anyone could create custom log messages by modifying the code. 23:31:00 Thanks will take a look, I am using caddy as my reverse proxy so it looks to have Prometheus metrics integration integrated. Going to pursue trying to log the access at the reverse proxy level because why not 🤷 23:31:15 Thanks will take a look, I am using caddy as my reverse proxy so it looks to have Prometheus metrics integration. Going to pursue trying to log the access at the reverse proxy level because why not 🤷 23:33:00 If your RPC is being DDoS by a malicious entity then you could solve it by closing the port or requiring username and password to access. 23:34:23 thank you, no real threat rn. Just for observability of my public node 23:35:50 <3​21bob321:monero.social> Cloudlfare????? 23:38:32 <3​21bob321:monero.social> Putting proxy infront probably will help 23:46:58 There is a grafana somewhre that shows the rpc connection types etc 23:47:21 lza_menace: do you have that public?