Seaport 1.5 is released and currently being used by all new orders on the OpenSea website.
Developers have a 7 day deadline, May 9th, to make the changes required. On May 9th, all future orders using Seaport 1.4 will be rejected.

The cross-chain address for Seaport 1.5 is 0x00000000000000ADc04C56Bf30aC9d3c0aAF14dC.

Seaport 1.4 orders will remain fillable until May 16th. When reading orders, users will continue to be able to read the protocol_address field to differentiate Seaport 1.4 orders from Seaport 1.5.

For more information on why OpenSea is upgrading Seaport, see 0age's tweet.

API Users

When signing orders, the domain needs to be changed to use Seaport 1.5.
When sending orders using the API, protocol_address is now a required field. Previously, if you did not provide a protocol_address, we chose a default address. Orders need to send the protocol_address matching the signature used when signing the order.

"domain": {
  "name": "Seaport",
  "version": "1.5",
  "chainId": "1",
  "verifyingContract": "0x00000000000000ADc04C56Bf30aC9d3c0aAF14dC"
}

SDK Users

The SDK, opensea-js,, has been updated to use the Seaport 1.5 protocol starting with version 5.0.0.

Update your app or package's dependencies.

"opensea-js": "^5.0.0",

The default contract for signing is Seaport 1.5.

Seaport Library Users

The seaport library, seaport-js, has added the Seaport 1.5 protocol in version 1.2.0.

If you are using the Seaport library, upgrade your package.
```
"seaport-js": "^1.2.0",
```

Make sure to initialize with seaportVersion: "1.5".

this.seaport_v1_5 = new Seaport(providerOrSinger, {
  seaportVersion: "1.5",
});

Changelog