Those “invalid transaction” entries in P2Pool logs are typically caused by transactions that fail fee rate checks against the local mempool policy. The size = 0, weight = 0 values in your log suggest the transaction data was not fetched or parsed successfully — P2Pool received a tx hash from a peer but could not retrieve or validate the full transaction from your node.

A few common causes:

1. Monerod not fully synced — If your local node is slightly behind, transactions in the mempool may reference outputs your node has not yet seen
2. Bandwidth/RPC timeout — P2Pool queries monerod for tx details; under load this can fail silently and log as invalid
3. Qubic/Tari merged mining — Yes, these do produce some unusual transactions. If you see spikes in invalid tx logs after Qubic stratum announcements, that confirms the connection

The errors are non-critical. P2Pool simply skips invalid transactions when building its share chain. Your mining rewards are not affected.

If it bothers you, verify your monerod is fully synced and the RPC connection between P2Pool and monerod is healthy (check --rpc-bind-port isn’t rate-limited).