Team CryptoInsightfull 
My Debug.log shows
2023-10-27 05:48:02 ERROR: CTxMemPool::accept() : nonstandard transaction (scriptpubkey)
2023-10-27 05:48:02 received: tx (421 bytes)
2023-10-27 05:48:02 ERROR: CTxMemPool::accept() : nonstandard transaction (scriptpubkey)
2023-10-27 05:48:02 received: block (697515 bytes)
2023-10-27 05:48:02 received block 000000000000000000033a0e17f780d84bd05dd479f8b5b1a052c2a23b433417
2023-10-27 05:48:02 ProcessBlock: ORPHAN BLOCK, prev=00000000000000000003f0be72edf0554c803ea8f1bf69ca3f9606992deac8d9
2023-10-27 05:48:02 sending: getblocks (997 bytes)
2023-10-27 05:48:02 CreateNewBlock(): total size 1224
2023-10-27 05:48:02 Running BitcoinMiner with 2 transactions in block (413 bytes)
I’m running Bitcoin Satoshi 0.8.6-Beta with GEN=1 set and its downloading the blockchain and processing it – I’ve found several Proof Of Works that my node validated while running GEN=0 – And they show up as Orphans when I use gettransaction transaction in the console panel. With GEN=1 set, my wallet is generating the mined rewards. I also found alot of other nodes Orphaned Blocks and Transactions. I don’t see any knowledge bases with this information.
I also have my coinbase.conf file set with
dbcache=22000 MegaBytes
maxmempool=2024 MegaBytes
mempoolexpiry=240000 Hours
persistmempool=1 Yes, Keep mempool in memory for restarting.
maxorphantx=1042300
blockreconstructionextratxn=1042300
It may be doing the trick to also process Orphan Transactions and Add them to the Mempool, which my debug.log’s have been showing an immense number of transactions being added and confirmed.
