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.
Only use the domains listed below when connecting a wallet or signing messages with EnteleWALLET. Domains marked reserved are official but not yet serving the wallet application.
entelewallet.comapp.entelewallet.comentelewallet.appentelewallet.orgwallet.entelekron.ioentelekron.ioentelekron.apptvk.groupEnteleWALLET ownership verification should use a clearly identifiable authentication message. Typed-data signatures, permit signatures, and Permit2 authorizations can authorize asset spending even when they do not immediately create an on-chain transaction.
EnteleWALLET 1.1 uses SIWE (EIP-4361) for ownership verification when the feature is enabled in the app.
The expected message must identify EnteleWALLET, the requesting domain, wallet address, purpose, nonce, issued time, and expiration time where applicable.
A basic ownership-verification message must not request token approval, Permit, Permit2, asset transfer, marketplace order, delegation, or unlimited authorization.
Inspect your wallet's signature details before signing.
Reject unexpected typed-data, permit, approval, or transaction requests.
A signature may carry authorization even if no gas fee is charged at signing time.
EnteleWALLET will never ask for a seed phrase or private key.
EnteleWALLET, EnteleKRON, TVK Group, TVK Labs, SOVRA, support staff, admins, partners, or community moderators will never ask for:
EnteleWALLET 1.1 connects through the wallet providers configured in the application. Always verify you are using the official wallet application or extension.
EnteleWALLET uses RainbowKit / wagmi, WalletConnect-compatible transport and EIP-6963 multi-provider discovery. Compatible installed injected wallets can appear even when they are not individually named below.
Important: exchange entries are verified official-navigation destinations. They are not connected exchange accounts, imported custodial balances, endorsements, partnerships or affiliate relationships.
Use the Transparency Center to verify official contracts, treasury wallets, presale wallets, and ecosystem addresses.
Visit Transparency CenterA source-bound view of what is available now, what is implemented but disabled, what is under independent review, and what remains future work.
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.
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 ·
If you discover a vulnerability, phishing site, or impersonation attempt, report it to our security team.
Report a Security Concernsecurity@tvk.group
EnteleWALLET 1.1 does not custody funds or store seed phrases or external-wallet private keys.
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.