Secure Electronic Communication via Threshold Secret Sharing Across Independent Communication Channels
The foundational patent covering Xail Mail: split-channel secure messaging, visual security tiers, progressive enrollment, enterprise compliance, deferred delivery, on-device AI, key-free P2P, and universal transport envelopes.
Claim 1 — Core Split-Channel Secure Communication SystemSYSTEM
Split plaintext into n shares via threshold secret sharing (k-of-n, fewer than k reveals nothing), transmit each via separate independent channel, reconstruct at recipient from k verified shares.
Alice sends a sensitive email through Xail. The message is split into 3 shares — one goes via Gmail, one via Outlook, one via Yahoo. No single email provider can read the message.
Claim 15 — Secure Communication with Message ID + IntegritySYSTEM
Split + attach unique message ID + integrity check to each share + transmit via independent channels from different service providers.
Each share carries a UUID and HMAC tag. The recipient's app matches shares by UUID and verifies each HMAC before reconstruction — tampered shares are rejected automatically.
Claim 20 — Core Split-Channel (Computer-Readable Medium)CRM
Instructions to split, transmit via independent channels, collect k shares, verify integrity, reconstruct.
The patent covers the software itself — the code running on any device that splits messages, sends shares through independent channels, and reconstructs at the other end.
Claim 28 — Visual Security-Level IndicatorMETHOD
Maintain channel count, determine k-of-n config, map to visual indicator state via deterministic function, render real-time updating graphical element. Communicates minimum compromises needed without user understanding threshold math.
A user's inbox shows green borders on messages from contacts with 3+ channels and blue borders for 2-channel contacts. The colors instantly communicate security level — no crypto knowledge needed.
Claim 33 — Progressive Security EnrollmentMETHOD
Start with 1 channel (single-channel, no threshold). Add 2nd → auto-activate k=2,n=2 + visual upgrade. Add 3rd → k=2,n=3 + visual upgrade to fault-tolerant.
A new user connects only Gmail — they get basic email. They add Outlook — blue border appears, messages are now split-channel secure. They add Yahoo — green border, now fault-tolerant too.
Claim 43 — Enterprise Compliance (Compliance Copy)METHODCONTINUATION 1
Split + transmit via threshold sharing. Simultaneously encrypt compliance copy with org public key. Store on compliance server (decryptable only by compliance officer). Channel operators cannot access.
A hospital uses Xail for doctor-patient communication. Messages are threshold-shared for privacy, but an encrypted compliance copy goes to the hospital's compliance server for HIPAA audit — only the compliance officer can decrypt it.
Claim 47 — Deferred Delivery to Non-Registered RecipientMETHODCONTINUATION 1
Detect recipient not registered. Send first share + "Join Xail" wrapper. Hold remaining share(s) in pending state on sender device. Auto-deliver when recipient registers.
Bob sends a secure message to Carol, who is not on Xail yet. Carol gets a teaser email saying "You have a private message from Bob." When Carol joins Xail, the second share auto-delivers and the message appears.
Claim 77 — Structural Anti-Spam Without Content FilteringMETHODCONTINUATION 1
Require any reconstructable message to be delivered as k shares to k of n registered addresses (disclosed only to authorized senders). Unauthorized sender without all n addresses = cannot deliver. No content analysis, no ML classification.
Spammers cannot send Xail messages because they would need ALL of a user's registered email addresses AND deliver coordinated shares to each. It is structurally impossible — no AI spam filter needed.
Standalone claim — no dependents
Claim 78 — Universal Transport Envelope EncodingMETHODCONTINUATION 1
Binary header with 4-byte magic number (IDA5) + version byte + share index. Base45 encoding for email/QR/text protocols. Same format for message shares, file shares, key shares, code shares.
Whether it is an email share, a QR code backup, or a code deployment package, every share starts with the IDA5 magic number and uses the same envelope format. One format to rule them all.
Standalone claim — no dependents
Claim 54 — On-Device AI ProcessingMETHODCONTINUATION 2
Reconstruct exclusively on device. AI inference (summarize, extract entities/actions, suggest replies) entirely on device. Persist results in encrypted local index. Nothing transmitted to any server.
Kaia AI reads a user's reconstructed messages to generate summaries and action items — but everything happens on-device. No message content ever leaves the laptop, not even to Anthropic or OpenAI.
Claim 58 — Contact Auto-EnrichmentMETHODCONTINUATION 2
A method of automatically enriching contact address records in a split-channel secure messaging system. As shares traverse independent channels, the system passively discovers additional email addresses associated with known contacts and updates their CRM records without user intervention.
Bob sends a secure message to Alice via Xail. When Alice's device reconstructs shares arriving from Gmail, Outlook, and Yahoo, the system learns that Alice controls all three addresses — enriching Bob's contact record automatically. Next time, Bob's client can route shares across all three channels for maximum resilience.
Standalone claim — no dependents
Claim 63 — Key-Free P2P CommunicationMETHODCONTINUATION 2
Split into n shares, establish P2P channels WITHOUT any key exchange/generation/storage/rotation. Security derives entirely from threshold sharing properties. Each share = indistinguishable from random noise.
Two Xail users on the same office WiFi communicate via direct P2P. There is no Diffie-Hellman, no TLS handshake for content security — the XorIDA split IS the security. Shares look like random noise on the wire.
Standalone claim — no dependents
Claim 68 — Delivery Acknowledgment Proving ReconstructionMETHODCONTINUATION 2
Recipient sends acknowledgment only after successful reconstruction (not just share delivery). Tamper-evident receipt with message ID + timestamp + cryptographic signature. Exportable as documentary evidence.
A lawyer sends a legally binding notice via Xail. The delivery receipt proves the recipient's device reconstructed the full message — not just that an email was delivered to a server. Admissible in court.
Standalone claim — no dependents
Claim 72 — Secure AI Tool Call Result DeliveryMETHODCONTINUATION 2
Tool call result from external tool server split into n shares via threshold IDA. Each share in transport envelope (sender DID, recipient DID, nonce, timestamp, scope, signature). Transmit to independent endpoints. Reconstruct at recipient agent. No single operator sees reconstructable result.
An AI agent queries a medical database. The results (containing PHI) are XorIDA-split across 3 relay endpoints. The AI processes the results locally — no single relay ever sees the complete patient data.
Claim 75 — Secure Structured Data Payload Delivery SystemSYSTEMCONTINUATION 2
Protocol-agnostic transport adapter layer + universal transport envelope format + n independent channels + threshold reconstruction. Works with any structured invocation protocol. Adding new protocol = new adapter only.
The same split-channel system secures REST API calls, gRPC streams, and MCP tool results — the transport envelope is protocol-agnostic. Adding a new protocol just means writing a new adapter.
Standalone claim — no dependents