> For the complete documentation index, see [llms.txt](https://nufi.gitbook.io/developer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nufi.gitbook.io/developer-docs/nufi-wallet/dapp-connector.md). # DApp Connector ## DApp connectors NuFi offers several DApp connectors allowing it to interact with DApps across multiple blockchains. Below are instructions/resources clarifying how to integrate them. ### Cardano NuFi's Cardano connector implements the [CIP-30](https://github.com/cardano-foundation/CIPs/tree/master/CIP-0030) standard and the API should behave the same as Flint wallet's CIP-30 connector, except it's injected as `window.cardano.nufi`. More info at [https://www.cardano-caniuse.io](https://www.cardano-caniuse.io/). ### Ethereum / EVM NuFi's Ethereum connector implements Metamask's API documented here: . When integrating NuFi we suggest following the [eip-6963](https://eips.ethereum.org/EIPS/eip-6963) standard. #### **Legacy eip-5749** NuFi still supports [eip-5749](https://eips.ethereum.org/EIPS/eip-5749) standard and you can load NuFi from `window.evmproviders`. However, its prefered to use [eip-6963](https://eips.ethereum.org/EIPS/eip-6963) instead. #### **Legacy `window.ethereum` injection** NuFi still offers legacy support and also tries to inject itself into`window.ethereum,` but we discourage using this approach and rather move to eip-5749 proposal. Note that in that case, NuFi will not inject its API if it detects Metamask or other wallet injecting into the `window.ethereum` object, to avoid interference with these wallets. Therefore, in order to use NuFi's Ethereum connector you need to make sure that there are no other active Ethereum wallet extensions (i.e. they must be disabled/uninstalled). NuFi supports Ethereum and all EVM networks. ### Solana / SVM NuFi's Solana connector can be integrated through the Solana Wallet Standard (). More info [here](https://github.com/wallet-standard/wallet-standard). ### Bitcoin NuFi's Bitcoin connector implements the [sats-connect](https://docs.xverse.app/sats-connect/wallet-providers) standard and registers itself into the `window.btc_providers` global array, following the [WBIP-0004 standard](https://wbips.netlify.app/wbips/WBIP004). The API should behave the same as Xverse Bitcoin wallet connector, except it's injected as `window.nufiBitcoin`. ### Flow NuFi works with the official [fcl-js](https://github.com/onflow/fcl-js) SDK and is fully integrated with the [fcl-discovery](https://github.com/onflow/fcl-discovery) service. If you want to integrate NuFi directly, the parameters needed for that can be found [here](https://github.com/onflow/fcl-discovery/blob/812bff5b90343976835d17bc2d7810aac62d714d/data/services.json#L74). ### Tron NuFi injects to DApps as TronLink (if TronLink not already installed). Check [TronLink docs](https://docs.tronlink.org/dapp/getting-started/) for reference. NUFI also supports [TIP-6963](https://github.com/tronprotocol/tips/issues/737) provider autodiscovery. --- # 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://nufi.gitbook.io/developer-docs/nufi-wallet/dapp-connector.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.