You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue is that the ENS labels.ens table is outputting more than one address for the same ENS with every other part of the datapoint being the same.
Current behavior
Expected behavior
For that particular ENS, the wallet that currently holds it is 0x93ca6ea0d4d8d066e64173e7eb983148a306858, which received the ENS from the 0x63bc9fdc6b27e0c67a1d047819c4d36bc08a8c39 about 1 year ago, as can be seen in the OpenSea NFT page.
The text was updated successfully, but these errors were encountered:
gm. can you map backwards from labels.ens spell and find the raw query in spellbook? then test from there? are you familiar with that data enough to help identify and fix for us?
Description
The issue is that the ENS
labels.ens
table is outputting more than one address for the same ENS with every other part of the datapoint being the same.Current behavior
Expected behavior
For that particular ENS, the wallet that currently holds it is
0x93ca6ea0d4d8d066e64173e7eb983148a306858
, which received the ENS from the0x63bc9fdc6b27e0c67a1d047819c4d36bc08a8c39
about 1 year ago, as can be seen in the OpenSea NFT page.The text was updated successfully, but these errors were encountered: