chore: release v8.0.3 - fix Seaport initialization for custom chain deployments #1794
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add getSeaportAddress import to SDK initialization - Pass contractAddress in Seaport overrides config - Ensures chains like Somnia use correct Seaport address (Gunzilla Seaport) - Fixes "could not decode result data" error when calling getCounter Previously, the SDK was creating Seaport instances without specifying the contract address, causing seaport-js to default to the cross-chain Seaport address. This resulted in errors on chains like Somnia that use custom Seaport deployments (Gunzilla Seaport). 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
ryanio
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
What's Included
This release includes the fix from #1793 that ensures the SDK properly initializes Seaport with the correct contract address for each chain. This resolves "could not decode result data" errors on chains like Somnia that use custom Seaport deployments (e.g., Gunzilla Seaport).
Key Fix
getCounter()call failures on chains with custom Seaport contracts🤖 Generated with Claude Code