Blockchain Email Authentication Bypasses SPF Forwarding Failures
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current email security systems, such as SPF, DKIM, and DMARC, are ineffective in preventing Business Email Compromise (BEC) attacks, particularly in scenarios involving mail forwarding, shared hosting, and outdated SPF records, and lack non-repudiation of email receipt verification.
Innovation Solution
A secure electronic messaging method utilizing a blockchain network to create and verify hashes of email content and sender/recipient identities, appending transaction identifiers to email headers, and using a receipt table to confirm message delivery and authenticity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional email security systems (SPF, DKIM, DMARC) are used to verify email authenticity, then domain spoofing can be blocked, but mail forwarding and shared hosting scenarios cause false positives and authentication failures
Solution Approach 1:
The patent introduces a blockchain-based intermediary system that acts as a neutral mediator between senders and recipients. Instead of relying on traditional SPF/DKIM/DMARC protocols that break down in forwarding scenarios, the blockchain serves as a universal trust layer where hash commitments are stored and verified. This intermediary resolves the contradiction by providing authentication that works across different email routing scenarios including mail forwarding and shared hosting, while maintaining reliability through cryptographic verification.
Solution Approach 2:
The patent segments the email authentication process into distinct cryptographic components: hash generation, blockchain commitment, transaction identifier embedding, and verification. By breaking down the authentication mechanism into these separable steps, the system can selectively apply verification at different stages and accommodate various email routing scenarios without compromising overall security or reliability.
2Measurement precision
If SPF records are updated frequently to reflect changing authorized IP addresses, then authentication accuracy improves, but maintenance complexity and time increase
Solution Approach 1:
The patent applies preliminary action by having senders commit their email hash, sender identity, and recipient identity to the blockchain in advance before sending the actual email. This pre-commitment creates an immutable record that serves as authentication proof, eliminating the need for frequent SPF record updates. The blockchain stores the authorized relationship beforehand, so when the email is sent, verification simply checks against this pre-established commitment rather than requiring real-time SPF record validation.
Solution Approach 2:
Instead of maintaining and updating SPF records dynamically, the system creates a cryptographic copy (hash) of the email content and sender identity, then commits this copy to the blockchain. This copy serves as the authentication reference, replacing the need for traditional SPF record maintenance. The blockchain copy is immutable and doesn't require updates even when IP addresses change, as long as the sender's identity remains the same.
3Ease of operation
If there is no receipt verification mechanism, then email delivery is simpler, but there is no undeniable proof of receipt for legal and business purposes
Solution Approach 1:
The patent implements feedback by having the recipient's mail user agent verify the blockchain transaction identifier and hash commitment, then provide a cryptographic receipt back to the sender. This feedback loop creates undeniable proof of delivery and receipt. The recipient's verification and acknowledgment are recorded on the blockchain, creating an immutable trail that provides reliable proof while maintaining operational simplicity through automated verification processes.
Solution Approach 2:
The blockchain serves as an intermediary that facilitates receipt verification without complicating the email delivery process. The transaction identifier embedded in the email header acts as a reference to the blockchain record, and the verification process automatically queries the blockchain for proof of receipt. This intermediary mechanism provides reliable legal and business proof while keeping the user experience simple and transparent.
Data Source
Figure 1
Figure 2A
Figure 2B
AI summary
An electronic messaging method comprises, in respect of a message received from a purported sender, determining if a blockchain transaction identifier is appended to the message, and comparing a hash created from the message body, the purported identity of the sender and the identity of the recipient with a hash stored on a blockchain network identified by the blockchain transaction identifier. When the created hash does not match with the stored hash, the received message is determined to be not from the purported sender. When the created hash matches the stored hash, the method may check a blockchain address registry associated with the blockchain network to determine if a blockchain address corresponding to the blockchain transaction identifier has an associated valid address in the blockchain address registry. A receipt transaction may be committed to the blockchain network in respect of the received message.