pull down to refresh

22 sats \ 2 replies \ @Filiprogrammer OP 27 Apr \ parent \ on: OCEAN successfully delays spam transactions mempool
No, because the overall fee to get into the next block was driven up by other transactions immediately after. Ironically, it was almost included—now it’s still stuck waiting in the mempool.
write
preview
this territory is moderated
0 sats \ 1 reply \ @denlillaapan 27 Apr
So not censoring/filtering by just good ole fashioned fee pressure...?
reply
0 sats \ 0 replies \ @Filiprogrammer OP 27 Apr
Yeah, but the transactions would have been included in the OCEAN block, if they weren't dropped due to the block template policy that the miner used.
It's technically not OCEAN who filtered these transactions since we are talking about a DATUM block. This means that the miner uses their own block template. In the case of this block, that miner was "Elektron Energy".
reply