Announcements and updates from the OpenSea Developer Platform. Stay in the loop on launches, updates, best practices, and more.
Announcements and updates from the OpenSea Developer Platform. Stay in the loop on launches, updates, best practices, and more.
Subscribe to OpenSea for Developers
Subscribe to OpenSea for Developers
OpenSea for DevelopersHorton Hears A Who!
Horton Hears A Who!Neutralizing a critical vulnerability in Wyvern Protocol — TL;DR — In Q1 of 2022, a security researcher reported a critical vulnerability in the Wyvern 2.2 smart contracts that powered OpenSea. The vulnerability was neutralized before it could be exploited, and users are no longer at risk. We awarded the vulnerability reporter a bug bounty. Historical blockchain logs provide no indication that the vulnerability was ever exploited in the wild. — The “Horton Principle” is a m...
OpenSea for DevelopersStreaming the OpenSea
Today we’re launching a beta version the OpenSea Stream API, a new websocket-based service that enables developers to receive events as they occur across our marketplace. With the massive growth in the NFT ecosystem, we know that it’s becoming increasingly challenging to rely solely on our REST APIs to stay up-to-date across a growing number of items and collections. The need to continuously poll these endpoints to refresh the data in your service can be resource-intensive and inefficient. We...
OpenSea for DevelopersMigrating to the Seaport protocol
Last week, we unpacked the early details of OpenSea’s new open-source protocol – Seaport – for the developer community. Seaport will become the foundation for OpenSea’s core products, unlocking a range of new use cases for creators, collectors, and the broader developer ecosystem. The protocol is non-custodial, non-upgradeable, and decentralized at its core — it belongs to the community first & foremost. And in that spirit, we’re inviting the community to join us in early testing via a $1M Co...
OpenSea for DevelopersHorton Hears A Who!
Horton Hears A Who!Neutralizing a critical vulnerability in Wyvern Protocol — TL;DR — In Q1 of 2022, a security researcher reported a critical vulnerability in the Wyvern 2.2 smart contracts that powered OpenSea. The vulnerability was neutralized before it could be exploited, and users are no longer at risk. We awarded the vulnerability reporter a bug bounty. Historical blockchain logs provide no indication that the vulnerability was ever exploited in the wild. — The “Horton Principle” is a m...
OpenSea for DevelopersStreaming the OpenSea
Today we’re launching a beta version the OpenSea Stream API, a new websocket-based service that enables developers to receive events as they occur across our marketplace. With the massive growth in the NFT ecosystem, we know that it’s becoming increasingly challenging to rely solely on our REST APIs to stay up-to-date across a growing number of items and collections. The need to continuously poll these endpoints to refresh the data in your service can be resource-intensive and inefficient. We...
OpenSea for DevelopersMigrating to the Seaport protocol
Last week, we unpacked the early details of OpenSea’s new open-source protocol – Seaport – for the developer community. Seaport will become the foundation for OpenSea’s core products, unlocking a range of new use cases for creators, collectors, and the broader developer ecosystem. The protocol is non-custodial, non-upgradeable, and decentralized at its core — it belongs to the community first & foremost. And in that spirit, we’re inviting the community to join us in early testing via a $1M Co...
<100 subscribers
<100 subscribers
Share Dialog
Share Dialog
Earlier today, we announced that we’ve started to migrate to Seaport, a new web3 marketplace protocol designed for safely and efficiently buying and selling NFTs. Following up on our detailed migration guide for developers 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 and listings endpoints on Mainnet
✅ API: Begin parsing new Seaport offers and listings from /assets and /bundles endpoints on Testnets
✅ SDK: Begin using new Seaport-ready functions in SDK v4.0.0 on Mainnet
June 21
✅ API+ SDK: Offers and listings can no longer be posted to Wyvern v2.3 contract using OpenSea
July 13
✅ API + SDK: Offers and listings can no longer be fetched from Wyvern v2.3 contract using OpenSea
For more details on each of these updates, please refer back to our detailed Seaport migration guide. If you have any questions, please reach out on Discord as we’re here to help.
Earlier today, we announced that we’ve started to migrate to Seaport, a new web3 marketplace protocol designed for safely and efficiently buying and selling NFTs. Following up on our detailed migration guide for developers 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 and listings endpoints on Mainnet
✅ API: Begin parsing new Seaport offers and listings from /assets and /bundles endpoints on Testnets
✅ SDK: Begin using new Seaport-ready functions in SDK v4.0.0 on Mainnet
June 21
✅ API+ SDK: Offers and listings can no longer be posted to Wyvern v2.3 contract using OpenSea
July 13
✅ API + SDK: Offers and listings can no longer be fetched from Wyvern v2.3 contract using OpenSea
For more details on each of these updates, please refer back to our detailed Seaport migration guide. If you have any questions, please reach out on Discord as we’re here to help.
No activity yet