<b​oog900:monero.social> has anyone noticed there seems to be a miner not filling blocks as much as they can, sometimes leaving them empty when there are plenty of txs.

<b​oog900:monero.social> they seem to be merge mining.

<b​oog900:monero.social> for example: 3416870, 3416869, 3416868

<b​oog900:monero.social> and there are more I can see just going back from those heights

<b​oog900:monero.social> add 3416871 to the list

<b​oog900:monero.social> `3416868` was from supportxmr.com which is the one that acctually contains txs, although they didn't fill the template as much as they could. The others have no txs

<b​oog900:monero.social> 3416872 finally has txs

<b​oog900:monero.social> monero.hashvault.pro/en/blocks

<b​oog900:monero.social> its those guys^

there was a pool that had a large % of the blocks it found had no txs because there was something wrong with their implementation which they corrected

this is to say that it is not always intentional

I assume hashvault and support are set up correctly

well they used to be set up correctly b4 merge mining

<m​onero.arbo:matrix.org> it was also happening with MoneroOcean but seems fixed now

Tari's merge mining proxy had a bug, so some pools had to mine empty blocks for a while.

<b​oog900:monero.social> well lets hope they update soon, all their blocks from the past day have had no txs

XMR empty blocks : 19.9 %

not good

in the last 360 blocks

more tx fees for p2pool though

I think it can only hurt the network if >50% of the blocks are empty. Then dynamic block size will not work (median size will be 0)

paradoxically, 20% empty blocks _increase_ the median block size. Because the other 80% blocks are more full now

<o​frnxmr:xmr.mx> I was thinking about that the other day. Why do we use median instead ofmean

to cut off outliers? Median is more reliable to show the most common value

<a​ntilt:we2.ee> in bitcoind a single empty block would increase your ban score +100, blocking the peer for 24h ...

<s​yntheticbird:monero.social> What about 1 tx block huh?

<b​oog900:monero.social> what really? surly that could cause netsplits

how would it even work

blocks are propagated by all peers in the network, including empty blocks

<a​ntilt:we2.ee> tbh - depriciated. But see:

<a​ntilt:we2.ee> par.nsf.gov/servlets/purl/10407054

<a​ntilt:we2.ee> "The Security Investigation of Ban Score and

<a​ntilt:we2.ee> Misbehavior Tracking in Bitcoin Network"

<a​ntilt:we2.ee> (table of ban rules p.3)

no empty blocks in that table

<a​ntilt:we2.ee> emty != invalid ? # mea culpa...

<a​ntilt:we2.ee> *empty

<b​oog900:monero.social> xmrchain.net/block/3417277

<b​oog900:monero.social> just means no txs other than the miner tx

empty blocks are perfectly valid

imagine there is not transactions in mempool, then empty blocks must be valid for the blockchain to keep going

<a​ntilt:we2.ee> sry, i see.

<a​ntilt:we2.ee> maybe I was triggered because I research statistical abnormality detection atm ...

<a​ntilt:we2.ee> ... and this rise in (merge mined) hash rate is a little bit too quick, for my taste.

<g​ingeropolous:monero.social> yeah. maybe its the x6.... dun dun dunnnnn