-
Notifications
You must be signed in to change notification settings - Fork 229
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update addresses #445
update addresses #445
Conversation
UnsupportedProtocol was also deployed for all the cases of NFT protocols not being available on some chains, even if v2 was supported! |
@@ -1,4 +1,3 @@ | |||
{ | |||
"UniversalRouter": "0x78e7F1502A9e4115dEbd6876E0AC4FaEBDB96880", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👀 how come you removed this?
This is URV2, it supports v4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ohh i thought u said we should remove it #445 (comment)
or should i just change it to URV2?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh yeah youre right lol
Co-authored-by: Alice <[email protected]>
UR v1 - doesn't support as many NFT protocols
UnsupportedProtocol - deployed if there is no support for v2 or for some nft protocols
UR v1.2 (v2 support or no v2 support) - added support for more NFT protocols
UR v2 - doesn't support NFT protocols, has v4 support