External-wallet Send is active in EnteleWALLET 1.1. Swap and Staking remain source-disabled and require separate evidence and activation gates. Native wallet creation, import and private-key storage also remain disabled.
A source-bound view of what is available now, what is implemented but disabled, what is under independent review, and what remains future work.
Connect a compatible external wallet, verify ownership, monitor portfolio, markets and activity, use Secure Receive, approval and recipient checks, prepare and simulate a transfer, review it in human-readable form, and Send supported EVM transfers with explicit wallet-side signing. EnteleWALLET does not custody funds or store the external wallet’s private key.
Transaction Composer and pre-sign simulation are active Send prerequisites. Recipient and address risk checks, network mismatch protection, fee freshness, human-readable Clear Review and live threat-intelligence checks run before authorization. The connected wallet remains the final signing authority.
Multi-Wallet Connection Center, allowlisted 0x Swap, Lido Staking, secure account access, referrals, rewards, promotions and EnteleLINK Connect exist as implemented or staged foundations but are not active production capabilities.
External-wallet Send is active in EnteleWALLET 1.1. Swap and Staking remain source-disabled and require separate evidence and activation gates. Native wallet creation, import and private-key storage also remain disabled.
Native wallet creation and import, hardware-backed local key isolation, recovery, native signing, iOS, Windows and browser-extension wallet engines remain separately gated future work. EnteleWALLET does not claim post-quantum transaction signatures.
This public status snapshot is tied to the exact application commit below. Status rule: merged does not mean enabled or production-ready.
tvk-group/entelewallet-app 0ba1262222489a4effb95a1d2927a9632932fda5 ·
This status block is generated from the current application review at 0ba1262222489a4effb95a1d2927a9632932fda5. “Implemented but gated” means code exists but production activation remains disabled until its documented security/review gate is satisfied.