<l​akeviewapartments:matrix.org> Hey I have a question about Monero block verification, specifically about merkle roots

<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

<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

spackle: ping

lakeviewapartments The functions to look at are get_tx_tree_hash and get_block_hashing_blob which calls it

<s​omeoneelse495495:matrix.org> Be aware monero.social have federation issues with matrix.org. Relaying response from sech1:

<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

<s​yntheticbird:monero.social> big syncing issue with matrix.org these days

<s​yntheticbird:monero.social> this time its matrix.org messages not coming in monero.social feed

<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

selsta: Cherry-picking #9342 did solve my debug build problems

Left a comment in the PR

I just finished my review of #8619, the wallet background sync PR for the master branch

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?

I just open two browser tabs and switch between them to check that changed are exactly the same

*changes

jberman: if we merge 8619 to master, is there any compatibility issue that I have to be aware of?

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.

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).

I do not follow. A node I did not have as --add-exclusive-node was able to connect to me.

ah, I think I see what you mean. I guess 'exclusive' is not quite as exclusive as I expected.

spackle thats bad news I haven't checked my node but I expect the same result as yours

this command line switch is only for outgoing connections

if you don't want incoming connections from random nodes, don't open port 18080

or firewall it to only enable your list of exclusive nodes

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.

sech1 got it, thanks. I'll look to using ufw for what I had in mind.

<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?

<m​iad.atri:matrix.org> Even when I try to enter xmr.se site, it gives me an error

<m​iad.atri:matrix.org> Does anyone know what happened?

Or just tell it not to accept incoming connections (--in-peers 0).