The JIL Wallet security architecture is built on multiple reinforcing layers: 2-of-3 key-share signing, where no single device could sign on its own, is a design target (on the default key today, JIL holds every key share and reconstructs the key on the server to sign, so there is no user shard), cosigner responses carry a post-quantum ML-DSA (Dilithium) co-signature alongside the classical signature, and the send path is built to ask a compliance check for an allow decision before submission and to refuse the send without one. Biometric Proof-of-Humanity (BPoH) identity binding and Kyber key encapsulation for wallet keys are design targets, not live.
Wallet security is the foundation of digital asset protection. A single vulnerability in any layer can result in total fund loss. Institutional-grade wallets must protect against current threats (phishing, malware, social engineering), future threats (quantum computing), and operational risks (device loss, key compromise).
JIL Sovereign Technologies Incorporated manages and operates getjil.com and wallet.getjil.com. The default key is reconstructed on the server. There is no user shard. A hardware wallet or a Safe whose owners you control is where you hold the keys. This page is a glossary note. It is not a claim that the wallet runs this network, bridge, rollup, or chain. Payment integrity at jilsovereign.com is the same company as the Layer-1 host and a different product. The same company manages and operates this wallet. The software is owned by JIL Sovereign Holdings, LLC (WY). The Layer-1 at jilsovereign.net is not an Ethereum chain.
The default key is reconstructed on the server, so there is no user shard. Sends are approved with your passkey, and cosigner responses carry a post-quantum ML-DSA (Dilithium) co-signature next to the classical signature. A hardware wallet or a Safe whose owners you control is the live path where you hold the keys.
Partly. Cosigner responses carry a hybrid post-quantum ML-DSA-65 (Dilithium) co-signature next to the classical signature. Kyber key encapsulation for wallet keys is a design target, not live, and the default key is still a classical key reconstructed on the server.