Closed MooncatDEXT closed 3 months ago
As stated above our correct token pair pool should be 0x154c6f3072506288f05042bB6287Fe926Bca62E4. Currently a token pair for our contract does not exist on Dextools, even though we index on multiple other places i.e. dexscreener, coingecko ect. The aggregator on Dextools is pulling the token pair 0x4ffb5c0b47be8f19c754917bb7d57de5d12492ef, and I think its because both contracts share the same Ticker on PulseX.
This is what happens when we search for our contract:
Additionally I submitted the form for the only token pair on Dextools by searching MRINC directly. The only token pair that showed was the incorrect pair. I didn't think anything of it, but you'll clearly see the pools don't match.
Here you can see our correct pool, and the incorrect pool. Thank you for the consideration in the matter. I know my community greatly appreciates it. Visibility is important to a project.
Incorrect pool:
Linked to dextools-io/backend#548
Is there a time-frame on how long this might take? Days or weeks? I'm impartial to either but a rough estimate would help. I need to follow up with my team so we can plan accordingly. ect.
Any updates?
Just a heads up. Someone has attempted to create duplicate scam of our token at https://www.dextools.io/app/en/pulse/pair-explorer/0x2f00d7f77deb16a94607c792bf4b886a0ccb12b5?t=1712327066866
Our token is still CA 0xFd71636E0ec2cB2307eD5b790B13249Bc6ef1Be2 Token pair is still 0x154c6f3072506288f05042bB6287Fe926Bca62E4
I know you guys are busy, but wanted to keep the confusion to a minimum. Thanks again for your help!
With all due respect its been almost 3 weeks now. Is anyone actually working on this issue???
Fixed
Steps
... The token is not findable on Dextools. MRINC on Pulsechain.
Ticker: $MRINC Contract address: 0xfd71636e0ec2cb2307ed5b790b13249bc6ef1be2 Pair address: 0x154c6f3072506288f05042bb6287fe926bca62e4
CMC dexscan: https://coinmarketcap.com/dexscan/pulsechain/0x154c6f3072506288f05042bb6287fe926bca62e4/
Which device are you using
(if aplicable) In which browsers are you seeing the problem?
No response
(if aplicable) What version of the browser are you using?
No response
(if aplicable) What mobile OS device are you using?
None
(if aplicable) Which mobile devices are you using?
No response
(if aplicable) Which version of the device OS are you running?
No response
In which page do you see the problem?
No response
Additional Info
No response