Typical software wallet
- Keys generated and used inside the host app/OS stack
- Single point of failure if malware or OS compromise occurs
- PQC retrofit often bolted onto existing app trust boundaries
Overview
Most mobile and edge wallets store keys in application memory or host secure enclaves that still share a general‑purpose attack surface. QTL Wallet takes a different approach: secrets are split across shares, with the SIM (UICC/eSIM) as the trust anchor for high‑value signing and identity operations.
The architecture targets post‑quantum‑ready signing paths, permissioned network participation, and custody workflows where compromise of the host app must not imply compromise of long‑lived signing authority—across sectors that already depend on strong identity and long‑lived trust.
Status: Pilot integration—available for scoped deployment and co‑engineering engagements. Contact us to discuss a pilot.
The QTL Wallet SIM‑centric key‑splitting approach is patented with the University of British Columbia (UBC). Licensing and integration terms are available for qualified operators and integrators.
Not a software‑only wallet
QTL Wallet
- Key material split; SIM (UICC/eSIM) holds the trust anchor
- Host application orchestrates—does not alone custody root authority
- Designed for PQC‑ready signing and high‑assurance identity workflows
How key splitting works
-
Split at enrollment
Cryptographic secrets are divided into shares during provisioning—no single software process holds the full signing authority.
-
SIM as trust anchor
The UICC/eSIM participates in reconstruction and policy enforcement—rooted in carrier‑grade secure element semantics, not app sandboxing alone.
-
Sign under policy
Transactions and attestations are approved only when host and SIM shares combine under defined rules—supporting audit, rotation, and PQC algorithm agility.
Where QTL Wallet fits
QTL Wallet is designed for regulated, high‑assurance identity and signing—where keys must survive host compromise and migrate toward post‑quantum algorithms without rebuilding trust from scratch.
Government ID & digital identity
National and provincial ID programs, e‑ID credentials, and mobile document providers that need SIM‑anchored signing—not keys stored only in consumer apps.
Banks & financial institutions
Strong customer authentication, transaction signing, and institutional custody workflows where SIM‑backed keys support audit, policy, and PQC migration paths.
Healthcare & life sciences
Clinician credentials, patient‑consent attestations, and long‑lived health records where identity and signing must remain trustworthy for decades.
Permissioned ledgers & digital assets
Validator and operator keys, institutional custody, and designated‑verification networks—not public mempool semantics.
Critical infrastructure & supply chain
Operator identity, provenance attestations, and supplier credentials on edge devices in utilities, telecom, and industrial networks.
Private mobile & edge
Private 5G, enterprise mobility, and controlled field deployments where UICC/eSIM is already part of the trust model.
Works with the rest of QTL
SILMARILS TDV
160‑byte designated‑verifier authentication for permissioned ledger nodes—complements wallet‑level signing policy.
PQC Readiness
Inventory and prioritize cryptographic dependencies before wallet and ledger upgrades.
Migration programs
End‑to‑end discovery, hybrid TLS/PKI design, pilot, and production rollout.
Pilot & integration
QTL Wallet is offered as an architecture and integration engagement—not a consumer app download. We work with government ID providers, banks and financial institutions, healthcare organizations, operators, and integrators to scope SIM provisioning flows, signing policy, PQC algorithm selection, and API or ledger integration.
- Architecture review and threat modeling for your trust boundaries
- SIM‑centric provisioning and key‑lifecycle design
- Integration with permissioned nodes, APIs, or custody workflows
- Alignment with NIST PQC standards and hybrid transition plans