Repository navigation
What's Changed
- fix: drop expired orders from a batch fulfill instead of failing it by @erkancamli in #1063
- fix: bulk orders use the passed account as offerer and reject signatures Seaport cannot parse by @ryanio in #1069
- chore(deps): update node.js to v26 by @renovate in #1067
- chore: bump version to 4.6.0 by @ryanio in #1070
Behavior changes
fulfillOrdersdrops orders whoseendTimehas passed at the latest block, the same way it already drops cancelled and fully filled ones. Seaport skips them onchain, so one expired order no longer fails the whole batch on its offerer's balance or approvals, and the fulfiller is no longer charged for it in the balance check or the nativevalue. Orders that have not started yet are kept.createBulkOrdersuses theaccountAddresspassed in as the offerer, ascreateOrderdoes. Before, it always used the signer's address, so a contract wallet's owner signing on its behalf produced bulk orders for the signer instead.signBulkOrder, andcreateBulkOrdersthrough it, now throw when the signature is not 64 or 65 bytes after compaction. Seaport only parses a bulk order signature of that length followed by the proof, so a longer one (for example a multi-owner Safe's 130 bytes) produced orders that could never be filled. Sign such orders one at a time withsignOrderorcreateOrder. This new throw, and the offerer change above, are why the release is a minor. Fixes #1060.- CI and
.nvmrcmove to Node 26.enginesstays at>=20.0.0.
Community Contributions
- Expired orders in a batch fulfill, thanks @erkancamli (#1063)
- Bulk order offerer, thanks @furkan3152 (#1068)
- Bulk order signature length, thanks @nftpoetrist (#1061, #1060)
Full Changelog: v4.5.0...v4.6.0