diff --git a/content/api-reference/data/webhooks/webhook-types/address-activity-webhook.mdx b/content/api-reference/data/webhooks/webhook-types/address-activity-webhook.mdx index f31678536..e679f761a 100644 --- a/content/api-reference/data/webhooks/webhook-types/address-activity-webhook.mdx +++ b/content/api-reference/data/webhooks/webhook-types/address-activity-webhook.mdx @@ -29,11 +29,14 @@ There are three main types of transfers that are captured when receiving a `from | Token | Event logs for ERC20, ERC721, and ERC1155 transfers. | | Internal ETH | Internal Transfers from a smart contract address. | + +**Internal transfers are now supported on every EVM network where Address Activity webhooks are available** — previously they were limited to Ethereum, Polygon, Arbitrum, Optimism, Base, BNB Chain, and Avalanche. + + **Note on Internal Transfers** -1. Internal transfers are currently only supported on Ethereum, Polygon, Arbitrum, Optimism, Base, BNB Chain, and Avalanche. Support for other networks is a WIP! -2. Internal Transfers with the call type `delegatecall` are not supported on Alchemy. Although they have a value associated with them, they don't transfer a value. For details read the [Ethereum Yellow Paper](https://ethereum.github.io/yellowpaper/paper.pdf). Internal transfer miner rewards are also unsupported on Alchemy. +Internal Transfers with the call type `delegatecall` are not supported on Alchemy. Although they have a value associated with them, they don't transfer a value. For details read the [Ethereum Yellow Paper](https://ethereum.github.io/yellowpaper/paper.pdf). Internal transfer miner rewards are also unsupported on Alchemy. # Example Response