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

Over the next few days, OpenSea will be migrating to Seaport, a brand new web3 marketplace protocol designed for safely and efficiently buying and selling NFTs. We’re going to be one of the first marketplaces using the core Seaport smart contract to build new features for the OpenSea community. 

Seaport as a protocol is decentralized and open source - anyone can use it, with no contract owner, upgradeability, or other special privileges. In that spirit, we’re also sharing the Seaport Dune abstraction table that will allow anyone to easily and quickly query transactions made on Seaport. 

While it’s most directly useful for Dune wizards, we believe this query structure and explanation could also be useful for any on-chain sleuths, and any services utilizing blockchain data. The query structure should help you understand how the on-chain data maps into transaction data -- including variables such as purchase types (e.g. if transaction was a standard offer, collection offer or attribute offer) and number of NFTs transacted.

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.

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 Code4rena contest.

The new Seaport protocol will open up a range of new paths for OpenSea and the developer ecosystem more broadly:

• A composable, open-source contract on top of which developers can build their own marketplaces
• The ability to create custom rulesets for the fulfillment of a listing or offer, using a concept called “zones”
• Support for multiple fees and custom creator fees
• Potential for new types of transactions: collection offers and batch fulfillment (including floor sweeping), batch listing, and more

That’s a wrap! The Replit and OpenSea virtual hackathon “Hello NFT World” has ended! We’d also like to give a shoutout to our partners, DoraHacks, and Buildspace.

Hello World meets web3 🖥️

The Hello NFT World Hackathon encouraged the advancement of web3 by bringing together creators, artists, developers, and entrepreneurs as “BUIDLers” to create innovative web3 NFT Projects.

Together, they pushed the boundaries of NFTs and surfaced new types of utility. Over the course of eight days, projects explored various concepts ranging from web3 education, NFT DeFi, and even blockchain dating!

Hello Devs,
Welcome to the inaugural OpenSea Developer Newsletter!

In this first edition, we’re sharing a recap of recent news and updates to the OpenSea Developer platform - including our API, SDK and developer events.

Let’s dive in!

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’ve built the Stream API to better support a range of use cases that rely on dynamic data, such as price fluctuation, listings, bids, and ownership changes. Instead of polling for updates, you can subscribe to receive events as they occur - whether for specific collections or globally across the entire OpenSea marketplace.

The Stream API makes it easier to build many new features, such as: