> For the complete documentation index, see [llms.txt](https://omen-protocol.gitbook.io/omen-protocol-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://omen-protocol.gitbook.io/omen-protocol-docs/omen-architecture/wallet-and-transaction-safety.md).

# Wallet & Transaction Safety

Understand wallet permissions, transaction approvals, and the security practices users should follow when interacting with OMEN Utility.

OMEN Utility is designed to let users connect compatible wallets and access supported blockchain functionality while retaining control over transaction authorization.

Understanding wallet connections, transaction approvals, token allowances, and blockchain risks is essential before interacting with digital assets.

**Security note:** Specific wallet flows, swap integrations, and security controls depend on the current implementation. This page explains general safety principles and should not be interpreted as a guarantee that every transaction or asset is safe.

### Your Wallet, Your Control

Users connect their own compatible wallets to access supported wallet-dependent features.

Connecting a wallet is different from authorizing a blockchain transaction. A connection may allow the application to access publicly available wallet information, such as the connected address. It does not automatically authorize every transfer or swap.

Transactions that require wallet authorization must be reviewed and approved through the connected wallet interface.

Users should disconnect their wallet from applications they no longer use and review wallet permissions when appropriate.

### Never Share Your Seed Phrase or Private Keys

OMEN will never require users to disclose their seed phrase or private keys to access OMEN Utility.

These credentials provide control over wallet assets and must remain confidential. Do not share them with anyone claiming to represent OMEN, including through direct messages, forms, support requests, or unofficial websites.

A legitimate wallet connection should not require users to send their seed phrase or private keys to OMEN.

Be cautious of impersonation attempts, phishing websites, fake support accounts, and unsolicited messages requesting sensitive wallet information.

### Wallet Connections and Transaction Approvals

A connected wallet can enable access to supported wallet-dependent features. Individual blockchain transactions may still require separate authorization.

Before signing a transaction, carefully review the following:

1. **Token and amount:** Confirm the asset involved and the quantity being exchanged or transferred.
2. **Expected output:** Review the estimated amount of tokens to receive, where applicable.
3. **Network:** Verify that the transaction uses the intended blockchain network.
4. **Fees and slippage:** Check the displayed transaction costs and slippage settings.
5. **Transaction details:** Inspect the information presented by the wallet before signing.
6. **Destination and permissions:** Verify recipient addresses and any requested contract permissions.

Quotes, fees, and estimated outputs may change with market conditions, liquidity, and network activity. Always review the latest transaction details before approval.

Never sign a transaction you do not understand.

### Token Allowances

Some token swaps require an allowance that permits a smart contract to spend a specified amount of a token on behalf of a wallet.

An allowance is separate from connecting a wallet and may remain active after a transaction, depending on the token and contract behavior.

Before granting an allowance, review the spender address and the requested amount. Avoid granting permissions you do not understand. Where appropriate, review and revoke unnecessary allowances using a trusted blockchain tool.

Revoking an allowance may require an additional blockchain transaction and network fee.

### Swapping Tokens Through OMEN

OMEN Utility is designed to provide swap functionality for supported assets through integrated trading infrastructure.

Where swaps are available, users should review the token address, transaction route, estimated output, fees, slippage, and any required token approvals before confirming the transaction through their connected wallet.

Swap availability and execution depend on supported assets, liquidity, routing infrastructure, network conditions, token permissions, and external service availability.

A displayed quote does not guarantee execution at the same price. Transactions may fail, execute with a different output, or incur network fees.

OMEN does not require users to disclose their seed phrases or private keys to facilitate a wallet-authorized transaction.

### Protecting Your Assets

Follow these practices to reduce avoidable risks:

1. Never share your seed phrase or private keys.
2. Access OMEN Utility through its official website: <https://omenprotocol.live>.
3. Verify token addresses before trading unfamiliar assets.
4. Review wallet connection requests and transaction permissions.
5. Confirm the intended blockchain network before signing.
6. Never approve transactions you do not understand.
7. Be cautious of phishing links, impersonators, and unsolicited messages.
8. Keep your browser and wallet software up to date.
9. Use trusted tools to review token allowances when necessary.
10. Independently verify suspicious requests before taking action.

If a request asks for credentials that should remain private, do not proceed until you have independently verified the situation.

### External Services and Blockchain Risks

OMEN Utility may depend on external data providers, trading services, smart contracts, wallet software, and blockchain infrastructure. The availability and behavior of these services can affect individual features and transactions.

Blockchain transactions may be irreversible. Network congestion, insufficient liquidity, price movements, malicious tokens, contract vulnerabilities, incorrect addresses, or unexpected transaction permissions can result in failed transactions or financial loss.

Connecting a wallet securely does not guarantee that every token, smart contract, or transaction is safe. Users should independently evaluate the assets they interact with and understand the permissions they approve.

### OMEN Approach to Wallet Safety

OMEN aims to make wallet interactions clear by helping users review available transaction information and authorize actions through their own wallets.

OMEN will not require users to disclose their seed phrases or private keys as a condition of using OMEN Utility.

Users remain responsible for their wallet security, transaction approvals, and decisions involving digital assets. No crypto platform can eliminate every blockchain or trading risk.

This page provides general security information and does not constitute a guarantee of safety or financial advice.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://omen-protocol.gitbook.io/omen-protocol-docs/omen-architecture/wallet-and-transaction-safety.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.