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

# Wallet and transaction safety

Participants on Quantix hold their own keys. The protocol cannot reverse a transaction or recover funds sent or signed away in error, so a few habits materially reduce risk.

Confirm the contract before interacting with it. The official QFI token addresses on TRON and BNB Chain, and the protocol's pool contracts, are published under Deployment Network; checking an address against that list defeats most impersonation attempts. Read each transaction before signing — an unexpected token approval, an unlimited allowance, or an interaction with an unfamiliar contract is a reason to stop, because a signature is how value actually leaves a wallet. Quantix will never request a seed phrase or private key, and no legitimate party ever needs one.

Institutional participants apply the same principles at scale: signing responsibilities are segregated, keys are held in hardware or institutional custody, and address and transaction details are confirmed through an independent channel before signing. Quantix maintains a single published list of its official addresses, domains, and support channels so participants have one authoritative source to check against.