> For the complete documentation index, see [llms.txt](https://evorium.gitbook.io/evorium-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://evorium.gitbook.io/evorium-docs/wallet-safety.md). # Wallet Safety ## Wallet Safety Wallet safety is one of the most important parts of using the Evorium blockchain. A wallet is the gateway between a user and the network. It allows users to hold EVO, send transactions, connect to decentralized applications, sign messages, approve token usage, and interact with smart contracts. Because of that, wallet security matters. In Web3, users control their own assets. This gives users more freedom, but it also creates more responsibility. If a private key or seed phrase is exposed, assets can be lost permanently. ### Your Wallet Is Your Access A blockchain wallet is not just an application. It controls access to your on-chain assets. On Evorium, a wallet can be used to: * Store and send EVO * Pay gas fees * Connect to dApps * Sign transactions * Interact with smart contracts * Approve token usage * Manage digital assets * Participate in ecosystem activity Anyone who controls the wallet’s private key or seed phrase can control the assets inside it. This is why wallet safety should always be treated seriously. ### Protect Your Seed Phrase A seed phrase is the backup key to a wallet. If someone gets access to your seed phrase, they can import your wallet and move your assets. No official team, application, validator, or support account should ever ask for it. Never share your seed phrase with anyone. Do not enter it into websites, forms, chats, bots, emails, or unknown applications. Do not store it in screenshots, cloud storage, public notes, or messaging apps. A safe seed phrase should be stored offline and protected from unauthorized access. If your seed phrase is exposed, the wallet should be considered compromised. ### Understand What You Sign Every wallet signature matters. When a wallet asks you to sign something, it means an application is requesting permission to perform an action. That action may be harmless, but it may also involve moving assets, approving token spending, or interacting with a smart contract. Before signing, users should check: * Which website or dApp is requesting the signature * What wallet is connected * What network is active * What action is being requested * Whether the request matches what the user intended * Whether the transaction uses EVO for gas * Whether a smart contract is involved Do not sign transactions you do not understand. A safe wallet habit is simple: read before confirming. ### Token Approval Risk Token approvals are one of the most common risks in Web3. When a user approves a smart contract to spend tokens, that contract may be allowed to move tokens from the wallet based on the approval amount. If the approved contract is unsafe, malicious, or compromised, user funds can be at risk. Users should be careful with approvals, especially unlimited approvals. Before approving a token, check: * Which token is being approved * Which contract receives permission * How much is being approved * Why approval is required * Whether the application is trusted * Whether the approval can be reduced or revoked later Approvals should not be treated as simple clicks. They are permissions. ### Verify the Network When using Evorium, users should make sure their wallet is connected to the correct network. Wrong network settings can cause confusion, failed transactions, or interaction with the wrong contracts. A legitimate Evorium dApp should guide users to the correct network and clearly show when a network switch is required. Before interacting with a dApp, users should verify: * The active network * The native gas coin: EVO * The dApp URL * The contract address if provided * The transaction details shown in the wallet Network verification helps reduce mistakes and protects users from fake or misleading applications. ### Beware of Fake Websites and Links Phishing is one of the biggest threats in Web3. A fake website can look similar to an official application and trick users into connecting their wallet, signing a malicious transaction, or entering a seed phrase. Users should avoid clicking random links from messages, comments, ads, unknown accounts, or unofficial communities. Before connecting a wallet, always check the website carefully. Warning signs include: * Misspelled domain names * Urgent messages asking users to act fast * Requests for seed phrases * Unexpected airdrop claims * Fake support accounts * Suspicious wallet popups * Unknown contract approvals * Unrealistic reward promises If something feels rushed or unclear, stop before signing. ### Use Separate Wallets Using one wallet for everything increases risk. A safer approach is to separate wallet activity based on purpose. Users may keep long-term assets in one wallet and use another wallet for daily dApp interaction. This helps reduce exposure if one wallet interacts with an unsafe contract or application. Common wallet separation can include: * Main wallet for long-term holding * Activity wallet for dApps * Testing wallet for new applications * Validator or operational wallet if applicable Not every user needs a complex setup, but separating high-value assets from frequent activity can improve safety. ### Check Transaction Details Before confirming a transaction, users should review the wallet prompt. A transaction should match the action the user expects. If the wallet shows an unexpected contract, unknown permission, high token approval, or confusing action, the transaction should not be signed. Users should check: * Transaction type * Estimated gas fee * Receiving address * Contract address * Token amount * Approval amount * Network name * dApp requesting the action A few seconds of checking can prevent permanent mistakes. ### After the Transaction After signing and submitting a transaction, users should wait for confirmation. A transaction may be pending before it is included in a block. Once confirmed, users can verify the transaction through a blockchain explorer or the dApp interface. A good wallet flow should help users understand: * Whether the transaction is pending * Whether it succeeded or failed * How much gas was used * Where the transaction can be verified * What changed after confirmation If a transaction fails, users should avoid repeating it blindly without understanding the reason. ### Wallet Safety for Developers Developers building on Evorium should design wallet flows that protect users. A dApp should clearly explain what users are signing and why. It should avoid confusing prompts, unnecessary approvals, hidden contract interactions, and unclear transaction descriptions. A safe dApp should: * Show the connected wallet * Verify the active chain ID * Display the action before wallet confirmation * Avoid unlimited approvals when unnecessary * Handle rejected transactions gracefully * Show transaction status clearly * Provide explorer links * Warn users before sensitive actions * Never ask for seed phrases or private keys Good wallet safety is not only a user responsibility. It is also a developer responsibility. ### The Evorium Approach to Wallet Safety Evorium is built with the belief that Web3 should become easier and safer to use. Wallet safety is a major part of that experience. Users should understand what they are signing.\ Developers should build clearer transaction flows.\ Applications should avoid unnecessary risk.\ The ecosystem should help people verify before they trust. A secure blockchain experience does not end at the protocol level. It continues inside every wallet interaction. For Evorium, wallet safety is part of making Web3 more practical, more transparent, and more trustworthy for real users. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://evorium.gitbook.io/evorium-docs/wallet-safety.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.