# Next steps on Seaport migration

By [OpenSea for Developers](https://paragraph.com/@sea-2) · 2022-06-14

---

Earlier today, we [announced](https://opensea.io/blog/announcements/launching-seaport-saving-the-community-millions-in-fees/) that we’ve started to migrate to [Seaport](https://opensea.io/blog/announcements/introducing-seaport-protocol/), a new web3 marketplace protocol designed for safely and efficiently buying and selling NFTs.  Following up on our [detailed migration guide for developers](https://nft.mirror.xyz/Bi_UbdXOi4AU3LtHT3WoLAN0a9YIWE2gYQmkyZ5whVM) that we had shared a few weeks ago, we’re highlighting the implications for developers at this milestone.

To recap, here’s what developers can expect from today (June 14) forward:

**June 14**

✅ **API:** Begin using the new Seaport [offers](https://docs.opensea.io/v2.0/reference/retrieve-offers) and [listings](https://docs.opensea.io/v2.0/reference/retrieve-listings) endpoints on Mainnet

✅ **API:** Begin parsing new Seaport offers and listings from [/assets](https://docs.opensea.io/reference/getting-assets) and [/bundles](https://docs.opensea.io/reference/retrieving-bundles) endpoints on Testnets

✅ **SDK:** Begin using new Seaport-ready functions in [SDK v4.0.0](https://www.npmjs.com/package/opensea-js) on Mainnet

**June 21**

✅ **API+ SDK:** Offers and listings can no longer be posted to [Wyvern v2.3 contract](https://etherscan.io/address/0x7f268357a8c2552623316e2562d90e642bb538e5) using OpenSea

**July 13**

✅ **API + SDK:** Offers and listings can no longer be fetched from [Wyvern v2.3 contract](https://etherscan.io/address/0x7f268357a8c2552623316e2562d90e642bb538e5) using OpenSea

For more details on each of these updates, please refer back to our [detailed Seaport migration guide](https://nft.mirror.xyz/Bi_UbdXOi4AU3LtHT3WoLAN0a9YIWE2gYQmkyZ5whVM).  If you have any questions, please [reach out on Discord](https://discord.com/channels/397566282729390110/434175585745633280) as we’re here to help.

---

*Originally published on [OpenSea for Developers](https://paragraph.com/@sea-2/next-steps-on-seaport-migration)*