# The Problem As highlighted by Vitalik in [this article](https://vitalik.eth.limo/general/2025/04/14/privacy.html), privacy is simulteanously one of Crypto's most important features, as well as one of its most prominent existential threats. Over the last few years, while providers of privacy tools have gained negative media attention (i.e. Tornado Cash), the importance of safeguarding privacy in a Web3 environment has been highlighted by several high profile kidnapping and robbery cases of wealthy Crypto individuals. Moreover, the rise of bots and copytraders have increased the need for users to be able to transact privately, without anyone following their every move.\ \ As such, while private transactions can be abused by malicious actors and people looking to use cryptocurrency to hide the source of their funds, privacy should be a right and people should not be forced to share their balances, transactions or online movement. This view has been shared by many prominent figure in the Ethereum ecosystem, most importantly by earlier mentioned developer Vitalik Buterin, who is a renowned supporter of dApps such as Railgun and Tornado Cash.\ \ While the importance of privacy in Web3 is thus generally agreed upon, the offering of privacy tools remains fragmented. As described in the next chapter, IncogniFi aims to change that, by creating a one-stop-shop privacy hub for browsing, communicating, transacting and storing crypto in a private way. --- # Agent Instructions: 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: ``` GET https://incognifi-or-product-docs.gitbook.io/incognifi-or-product-docs/introducing-incognifi/the-problem.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.