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.

Sign up for GitHub

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

Jump to bottom

Rarible appears to have multiple contract addresses, one works, one fails #37

Open

Complexity opened this issue Jun 1, 2021 · 0 comments

Complexity commented Jun 1, 2021

One Rarible contract address works with NFTE endpoint: 0x60f80121c31a0d46b5279700f9df786054aa5ee5

(Example item: https://rarible.com/token/0x60f80121c31a0d46b5279700f9df786054aa5ee5:335911?tab=details)

(Working request: https://nfte.app/api/embed.js?contract=0x60f80121c31a0d46b5279700f9df786054aa5ee5&tokenId=335911)

An alternative Rarible address is not included in knowncontracts/Rarible.js and fails: 0xd07dc4262bcdbf85190c01c996b4c06a461d2430

(Example item: https://rarible.com/token/0xd07dc4262bcdbf85190c01c996b4c06a461d2430:542153?tab=history)

(Failing request: https://nfte.app/api/embed.js?contract=0xd07dc4262bcdbf85190c01c996b4c06a461d2430&tokenId=542153)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment