Non-Interactive RDMPF Encapsulation

• The paper introduces a novel non-interactive key encapsulation mechanism employing RDMPF to achieve sender anonymity, content confidentiality, and forward secrecy.
• The protocol uses ephemeral intermediaries and rigorous formal proofs to ensure IND-CPA security, hint privacy, and uninterrupted key derivation.
• The deployment on the Internet Computer demonstrates practical system enhancements, including cross-subnet canister integration and certified destruction protocols.

A non-interactive RDMPF-based encapsulation is a cryptographic scheme that utilizes the rank-deficient matrix power function (RDMPF) for key encapsulation and transport key establishment in privacy-preserving architectures. Its design targets sender anonymity, content confidentiality, unlinkability, and forward secrecy, and it is implemented with ephemeral intermediaries and secure destruction protocols. Most notably, the protocol is adopted in production on the Internet Computer (ICP) as the ICPP system and features exhaustive formal security arguments and operational enhancements (Salazar, 29 Dec 2025).

1. Formal Definitions and Setup of RDMPF-KEM

The scheme operates over modular arithmetic and matrix constructs:

• Parameters: A prime $p$ (approx. 192 bits), dimension $d$ ($8 \leq d \leq 24$), $\mathbb{Z}_p = \mathbb{Z}/p\mathbb{Z}$, $\mathbb{Z}_{p-1} = \mathbb{Z}/(p-1)\mathbb{Z}$.
• Matrix Selection: Public rank-deficient base matrices $BaseX, BaseY \in \mathbb{Z}_{p-1}^{d\times d}$ with rank $d-1$ and a full-rank mixing matrix $W \in \mathbb{Z}_p^{d\times d}$.
• Public Setup: The tuple $\pi_{pub} = (p, d, BaseX, BaseY, W)$ is published.

Key Generation

Each user $U$ (sender or recipient):

• Samples $d$0.
• Computes public matrices:
  • $d$1,
  • $d$2.
• The public key is $d$3; secret key is $d$4.

Rank-deficient sampling uses random matrices to ensure target rank properties, critical for subsequent scalar-action commutativity.

Encapsulation (Non-Interactive KEM)

Given a recipient public key $d$5 and public context $d$6:

1. Ephemeral sender key generation as above.
2. Nonce $d$7 sampled.
3. Compute RDMPF tokens:
   • $d$8
   • $d$9
4. Compose shared secret matrix: $8 \leq d \leq 24$0, where the $8 \leq d \leq 24$1th element is $8 \leq d \leq 24$2.
5. Hash $8 \leq d \leq 24$3 via SHA3; derive KEM seed $8 \leq d \leq 24$4.
6. Generate transport keys $8 \leq d \leq 24$5 using HKDF with info and salt.
7. Authentication tag: $8 \leq d \leq 24$6.
8. Capsule formed as $8 \leq d \leq 24$7.
9. Public hint $8 \leq d \leq 24$8. 10. Optionally, apply AEAD encryption with $8 \leq d \leq 24$9.

Decapsulation

Recipient uses $\mathbb{Z}_p = \mathbb{Z}/p\mathbb{Z}$0 and capsule $\mathbb{Z}_p = \mathbb{Z}/p\mathbb{Z}$1:

• Recompute $\mathbb{Z}_p = \mathbb{Z}/p\mathbb{Z}$2 as above.
• Compute $\mathbb{Z}_p = \mathbb{Z}/p\mathbb{Z}$3, hash and derive $\mathbb{Z}_p = \mathbb{Z}/p\mathbb{Z}$4.
• Verify authentication tag; output $\mathbb{Z}_p = \mathbb{Z}/p\mathbb{Z}$5 if valid, else $\mathbb{Z}_p = \mathbb{Z}/p\mathbb{Z}$6.

2. Mathematical Properties of the RDMPF Construction

RDMPF Definition

For $\mathbb{Z}_p = \mathbb{Z}/p\mathbb{Z}$7:

$\mathbb{Z}_p = \mathbb{Z}/p\mathbb{Z}$8

Composition Law: For $\mathbb{Z}_p = \mathbb{Z}/p\mathbb{Z}$9,

$\mathbb{Z}_{p-1} = \mathbb{Z}/(p-1)\mathbb{Z}$0

Rank Deficiency

Rank deficiency in $\mathbb{Z}_{p-1} = \mathbb{Z}/(p-1)\mathbb{Z}$1 (rank $\mathbb{Z}_{p-1} = \mathbb{Z}/(p-1)\mathbb{Z}$2) enforces scalar-action commutativity (Lemma 4.1). Full rank in $\mathbb{Z}_{p-1} = \mathbb{Z}/(p-1)\mathbb{Z}$3 ensures unpredictability and security of $\mathbb{Z}_{p-1} = \mathbb{Z}/(p-1)\mathbb{Z}$4.

This suggests the scalar-action commutativity enabled by rank deficiency is required to guarantee decaps/encaps correctness and the non-interactive property.

Correctness

Encapsulation and decapsulation steps yield identical $\mathbb{Z}_{p-1} = \mathbb{Z}/(p-1)\mathbb{Z}$5, and hence derived $\mathbb{Z}_{p-1} = \mathbb{Z}/(p-1)\mathbb{Z}$6 (Theorems 4.2–4.3), ensuring functional consistency.

Non-Interactivity

All computations depend solely on public keys and ephemeral random choices; no rounds of interaction are required.

3. Security Arguments and Guarantees

Confidentiality and IND-CPA

The encapsulation achieves IND-CPA security for transport key derivation (Theorem 4.10):

• $\mathbb{Z}_{p-1} = \mathbb{Z}/(p-1)\mathbb{Z}$7 possesses high conditional min-entropy for any PPT adversary given public information.
• HKDF produces $\mathbb{Z}_{p-1} = \mathbb{Z}/(p-1)\mathbb{Z}$8 indistinguishable from uniform.
• AEAD under $\mathbb{Z}_{p-1} = \mathbb{Z}/(p-1)\mathbb{Z}$9 ensures IND-CPA security for the payload.

The combination $BaseX, BaseY \in \mathbb{Z}_{p-1}^{d\times d}$0 prevents leakage of $BaseX, BaseY \in \mathbb{Z}_{p-1}^{d\times d}$1 and message contents.

Hint Privacy

$BaseX, BaseY \in \mathbb{Z}_{p-1}^{d\times d}$2 is a 256-bit digest. Security arguments (Theorem 4.13) assert that in absence of a SHA3 inversion, adversaries cannot correlate HINT with $BaseX, BaseY \in \mathbb{Z}_{p-1}^{d\times d}$3 except with negligible probability ($BaseX, BaseY \in \mathbb{Z}_{p-1}^{d\times d}$4).

Forward Secrecy

Ephemeral secrets $BaseX, BaseY \in \mathbb{Z}_{p-1}^{d\times d}$5 persist only in memory of short-lived canisters ("I₁"/"I₂"). Witness $BaseX, BaseY \in \mathbb{Z}_{p-1}^{d\times d}$6 attests to destruction ("DestructProof"). After teardown, past secrets are irrecoverable—even if RDMPF is later compromised.

4. Protocol Architecture and System Integration

Ephemeral Intermediaries and Storage

• I₁ (deposit): Receives $BaseX, BaseY \in \mathbb{Z}_{p-1}^{d\times d}$7, writes sealed payload to storage canisters $BaseX, BaseY \in \mathbb{Z}_{p-1}^{d\times d}$8, announces $BaseX, BaseY \in \mathbb{Z}_{p-1}^{d\times d}$9 publicly.
• I₂ (retrieval): Pulls capsule from $d-1$0 quorum, authorizes user via $d-1$1, delivers decrypted payload.

Public Notice and Discovery

HINT serves as the sole public identifier on the noticeboard. It does not reveal identity information for participants. Retrieval is a "pull" operation where recipients scan for HINT.

Destruction Proofs and Attestation

Each ephemeral canister issues a destruction intent, is torn down by Factory, and the ephemeral witness $d-1$2 records proofs of destruction. Finalization binds HINT to the published proofset.

ICP-Specific Enhancements

• Dual ($d-1$3) canister storage for minimal cost; the protocol generalizes to $d-1$4-of-$d-1$5 quorums.
• Cross-subnet deployment and distinctness enforced via $d-1$6.
• Canister-Signed Receipt Nonces (CSRN) enable mutual confirmation without identity leakage.
• Zeroization of transient memory before canister destruction.

5. Security and Correctness Proofs

The protocol's security is formalized via theorems and definitions provided in the reference paper (Salazar, 29 Dec 2025):

Security Property	Mechanism/Argument	Statement
Encaps/Decaps correctness	Composition law, NIKA correctness	Both sides derive identical transport keys
IND-CPA for KEM/AEAD	cRDMPF entropy, HKDF extraction	Keys indistinguishable from uniform
Hint privacy	Non-invertibility of SHA3	HINT uncorrelated to public keys
Forward secrecy	Ephemeral secrets, attested destruction	Past keys inaccessible post-teardown
Authorization soundness	HMAC verification	Authentication tag verifies context
Timeout reclaim	DestructProof protocol	Intent and proof auditable on noticeboard

Context and Significance

These proofs establish that sender anonymity, content confidentiality, and unlinkability are maintained under standard cryptographic and threat assumptions. The protocol is tailored for the operational environment of ICP, but the design principles generalize to any infrastructure permitting ephemeral, certified-destruction components.

6. Operational Deployment and Enhancements

The non-interactive RDMPF-based encapsulation described here is implemented in production as ICPP on the Internet Computer. Extensive testing and targeted enhancements address operational features unique to ICP, including cross-subnet canister placement, low-cost quorum, and robust memory zeroization protocols. The noticeboard architecture affords public auditability, while certified destruction mechanisms provide verifiable liveness and finality.

This suggests that the RDMPF-based encapsulation can be adapted to other contexts with similar ephemeral computation and attestation capabilities, although performance and deployment details are contingent on system-level primitives.