removed

[May 23, 2023] Turned off Ropsten, Kovan, and Rinkeby on Ethereum

As a follow-up to our announcement of the deprecation of Rinkeby, Ropsten, and Kovan test networks last October, we've officially turned off these testnets. :wave:

[May 10, 2023] NFT API V3 Launch (Beta)

We heard your feedback and made some improvements to the NFT API and launched V3 in Beta! It includes the changes below:

added

[May 4, 2023] Starknet public launch

Starknet and its native Account Abstraction are now fully available on Alchemy! :rocket:

added

[May 1, 2023] Two factor verification at signup

We’ve added an additional verification step to our signup flow, wherein some users will be asked to verify their identity via SMS code or phone call. 📱

added

[Apr 21, 2023] Added address limit to "Add and remove webhooks addresses" endpoint

We've shipped a change to limit the number of addresses a user can send to the "Add and remove webhooks addresses" endpoint to 100 addresses per request in order to prevent large payloads from breaking things.

added

[Apr 11, 2023] New security feature: Account lockout

We've added account lockout functionality to further secure your accounts. :lock:

added

[April 4, 2023] NFT API On Sepolia

The Alchemy NFT API is now available on the Ethereum Sepolia testnet! This support includes all of the same NFT API methods that are currently available on the Ethereum Goerli testnet.

added

[March 27th, 2023] Added support for Polygon zkEVM chain

We have officially added support for Polygon zkEVM, get started by visiting Polygon zkEVM Quickstart.

removed

[Mar 17, 2023] Removed support for Crypto.org network

Starting on March 17, 2023 we no longer support existing and new accounts on Crypto.org. We have communicated this over email to impacted teams, and are adding here for posterity.

added

[Mar 2, 2023] Added 'indexed' block tag to Transfers API

We have added indexed as a block tag param for alchemy_getAssetTransfers. This block tag can be used instead of latest as the fromBlock or toBlock param. Under normal circumstances, indexed will have the same behavior as latest. However, under certain unusual situations such as a network fork or partial network outage, transfers data up to the latest block may not be available. In these cases, if latest is used as the toBlock, we will return an error; however with indexed, we will instead try to return whatever transfers data is available.