Subject: [bitcoindev] Transaction Validation Optimization

From: John <[email-masked]>
Date: Tue, 18 Feb 2025 07:22:44 -0800 (PST)

Hi everyone,

While analyzing the codebase, I observed what seems to be duplicate 
validation steps for transactions that already exist in the mempool when 
they appear in new blocks. Specifically, I'm curious if the secondary 
validation performed during block acceptance could be safely optimized for 
SegWit-verified transactions using their wtxid hashes.（I'm still working on 
the source code, and I'm not sure if the source code was validated twice）

I'm particularly seeking clarification on two aspects: First, does the 
current implementation indeed perform full re-validation of mempool 
transactions during block processing? Second, if such optimization is 
theoretically possible, what subtle risks might emerge regarding 
transaction propagation timing or node synchronization that a newcomer like 
myself might overlook?

I'd be grateful for any insights about historical design decisions in this 
area, critical code sections I should study more deeply, or potential 
pitfalls in this line of thinking. 

Thanks in advance for sharing your expertise,
John

-- 
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email-masked].
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/3c2b1e7a-ffcd-41da-a533-2d9224fc016fn%40googlegroups.com.