# Supported Assets

Dfns offers a wide array of chain-specific crypto asset support.  Before reviewing our support matrix, it's important to understand how Dfns exposes APIs for facilitating blockchain interactions:

1. High-level APIs: [Transfer Asset](https://docs.dfns.co/d/api-docs/wallets/transfer-asset-from-wallet) simplifies complex asset transfer operations. It abstracts away the details of blockchain interactions, allowing for easier integration. Dfns asset integrations are implemented in the context of this high-level API and are detailed below.
2. Mid-level APIs: [Sign and Broadcast](https://docs.dfns.co/d/api-docs/wallets/broadcast-transaction-from-wallet) Enables interaction with any arbitrary smart contract but requires developers to integrate with native chain SDKs to format transactions as inputs. It requires more development but provides greater control over the transaction.
3. Low-level APIs: [Generate Signature](https://docs.dfns.co/d/api-docs/wallets/generate-signature-from-wallet) offer granular control by exposing our MPC signing directly to the developer.  This also requires more engineering effort, but makes it possible to execute any interaction with any chain that supports our underlying cryptographic schemes: ECDSA, EdDSA, and Schnorr.

When using the high-level Transfers APIs, Dfns supports various assets across multiple chains, such as native cryptocurrencies, ERC-20 tokens, NFTs, and non-EVM assets. In the Dfns API, the `kind` variable specifies the type of asset being transferred. It determines how the transaction is processed based on the asset's blockchain standard. For example, `kind` can be set to `Native` for base cryptocurrencies (e.g., Bitcoin, Ethereum), `ERC20` for fungible tokens on Ethereum, or `ERC721` for NFTs. Other possible values include standards from non-EVM chains like `SPL` or `ASA`. Correctly setting the kind ensures that the API handles the transaction according to the asset's unique characteristics. 

Each asset type requires specific parameters, such as contract addresses for ERC-20 and ERC-721 tokens, or asset IDs for non-EVM assets. Transactions involve specifying the asset type, destination address, and amount, with additional fields varying by asset type.  

Please find a summary of the assets currently supported by the Dfns Transfer API under [Supported Blockchains](https://docs.dfns.co/d/api-docs/wallets#supported-networks).


---

# 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://docs-legacy.dfns.co/d/getting-started/supported-assets.md?ask=<question>
```

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.