I just deployed a contract earlier today on Sepolia. Here is the address -
0x3d5aCBa6df0EAD5d5f9CC285B10BD6d3a71933f3
I am noticing something weird which is that the royalties seem to point to the address itself. You can look on the royalty registry -
(make sure you are on sepolia)
It seems to be reverting. Here is a screenshot of this transaction from tenderly -
0x911995e96cc877550832565516cd78e5b3ec740a7f3ca22efda63f3cea408ace
which is line 466 here…
Any ideas?
Interestingly looking at etherscan for this contract I see some behavior that confuses me.
I guess it’s just weird the royalty address is by default the token contract address…
I guess this is the code -
which is 4 years old, so I guess should be fine… will keep digging
Ah OK I think the issue is maybe the royaltyEngineV1 is 0x0000000000000000000000000000000000000000…?
Maybe similar to this? Royalty Registry Data Mismatch - #2 by yungwknd.xyz
It’s because by default royalty info returns that if not configure.
The address returned doesn’t matter because the royalty value is 0
Any idea why it reverts on the marketplace contract?
It seems like (based on tenderly) it’s trying
try IRoyaltyEngineV1(0x000000...000).getRoyalty(...)
Sepolia marketplace? What marketplace address are you using?
Sepolia yeah 0x5246807fb65d87b0d0a234e0f3d42374de83b421
Ya, we just never initiated the royalty registry on the sepolia marketplace, my bad. We’ll do it asap.
All good! Kinda figured it was something weird and just psyopsed myself out of it in that other thread.
No rush on it tonight, lmk if you get around to it tomorrow.
thank you!
Ok. Should be configured now.
Works! Thank you Wilkins
https://sepolia.etherscan.io/tx/0x6ae3887e16633947831ac1a88556fba84496b7f1863898f0dba433f3d3b64f7d
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.