03:34:33 <m-relay> <l​akeviewapartments:matrix.org> Hey I have a question about Monero block verification, specifically about merkle roots
03:34:33 <m-relay> <l​akeviewapartments:matrix.org> According to CryptoNote Standard 003 "CryptoNote Blockchain" the four parts of a block are the combined size o fthe header, merkle root hash, tx number, the block header itself, the merkle root hash, and the number of txs in the block
03:35:18 <m-relay> <l​akeviewapartments:matrix.org> I've been looking around functions like handle_block_to_main_chain to find where the merkle root is calculated/verified and what functions are used to do so but I haven't been able to find it
06:27:58 <xFFFC0000> spackle: ping
07:52:05 <sech1> lakeviewapartments The functions to look at are get_tx_tree_hash and get_block_hashing_blob which calls it
08:06:15 <m-relay> <s​omeoneelse495495:matrix.org> Be aware monero.social have federation issues with matrix.org. Relaying response from sech1: 
08:06:17 <m-relay> <s​omeoneelse495495:matrix.org> <s​ech1> lakeviewapartments The functions to look at are get_tx_tree_hash and get_block_hashing_blob which calls it
09:43:17 <m-relay> <s​yntheticbird:monero.social> big syncing issue with matrix.org these days
09:43:26 <m-relay> <s​yntheticbird:monero.social> this time its matrix.org messages not coming in monero.social feed
10:20:14 <m-relay> <l​akeviewapartments:matrix.org> Hey sech1 thanks for the pointers not sure how I even overlooked that, the crypto folder was very useful in looking in how its implemented in that regard
11:29:10 <rbrunner> selsta: Cherry-picking #9342 did solve my debug build problems
11:41:01 <rbrunner> Left a comment in the PR
13:08:28 <rbrunner> I just finished my review of #8619, the wallet background sync PR for the master branch
13:10:09 <rbrunner> There is the companion PR #8617 for the release branch. Now I am bit at a loss, as that probably also needs a review, how to do that in a sensible way?
13:15:39 <sech1> I just open two browser tabs and switch between them to check that changed are exactly the same
13:15:50 <sech1> *changes
13:18:04 <selsta> jberman: if we merge 8619 to master, is there any compatibility issue that I have to be aware of?
18:07:19 <spackle> It appears that --add-exclusive-node does not function as I expected. While running my private testnet (with a p2p port forwarded), it seems that a node that was not in my list of exclusive nodes was able to connect to me and force a reorg. Just wanted to share.
18:08:54 <moneromooo> It is expected. It tells the node to only connect to that node (though maybe seed nodes can be connected to as well, not quite 100% sure).
18:12:33 <spackle> I do not follow. A node I did not have as --add-exclusive-node was able to connect to me.
18:15:30 <spackle> ah, I think I see what you mean. I guess 'exclusive' is not quite as exclusive as I expected.
18:41:06 <SyntheticBird> spackle thats bad news I haven't checked my node but I expect the same result as yours
18:44:09 <sech1> this command line switch is only for outgoing connections
18:44:19 <sech1> if you don't want incoming connections from random nodes, don't open port 18080
18:44:42 <sech1> or firewall it to only enable your list of exclusive nodes
18:44:57 <spackle> indeed. I brought down the connection on port 29000, figuring that after the reorg'd we both need to reset before the test can continue.
18:45:25 <spackle> sech1 got it, thanks. I'll look to using ufw for what I had in mind.
18:56:51 <m-relay> <m​iad.atri:matrix.org> Good time friends. I opened the element today and the error of not connecting to the server was shown .Is the xmr.se server down?
18:56:53 <m-relay> <m​iad.atri:matrix.org> Even when I try to enter https://xmr.se site, it gives me an error
18:56:55 <m-relay> <m​iad.atri:matrix.org> Does anyone know what happened?
19:12:53 <moneromooo> Or just tell it not to accept incoming connections (--in-peers 0).