Moxie Official

That's annoying... somebody submitted the Moxie ERC20 contract with the wrong ABI (this is something you'd have to explicitly do?) now we have to wait a few days for @dune.eth to update the ABI 😐 

Screenshot shows my name but that's not true - I've submitted an ABI change request, not the original request. Note: the name on the contracts/new screen ("moxie_base.MoxieToken") doesn't match the name on the data explorer ("moxie.MoxieTokenLockWallet") but that's the link Dune gives me when I click on it 🤷‍♂️

I guess we'll decode the events manually for now.

https://dune.com/contracts/new

Husband, dad, dev • @dune.eth wizard • Ultimate Ⓜ️oxie Dashboard https://tinyurl.com/moxiedash •  I'm just zis guy, you know?

Weird, abis are usually automatically decoded from the address tho. Not sure how someone could submit a wrong abi?

airstack

Husband, dad, dev. Host of /wr.

⭐ DEGEN Tips FAQ: https://paragraph.xyz/@rjs/degen-tips-ultimate-faq-v8 ⭐

Not financial advice. Not a KOL.

@dune.eth I think this is a Dune bug

Steps to reproduce:
1. Go to https://dune.com/contracts/new
2. Choose base and use '0x8c9037d1ef5c6d1f6816278c7aaf5491d24cd527'  as the contract address
3. Observe that the system reports "Contract already decoded via manual submission." and has a blue link named "moxie_base.MoxieToken"
4. Hover over the blue link and see it says: https://dune.com/queries?category=decoded_project&namespace=moxie&contract=MoxieTokenLockWallet&blockchains=base
5. Note this doesn't match the contract name in the HTML label; follow the link and observe it's the wrong contract

Expected:
4. Should link to: https://dune.com/queries?category=decoded_project&namespace=moxie&contract=MoxieToken&blockchains=base

In this case it looks like a @dune.eth UI bug that's linked to the wrong decoded project, but it does appear possible to overwrite the ABI and 'poison' the decoder? (Not going to test this theory for obvious reasons 😅 )

ex-/airswap. part time node runner, full time shitcaster, all time higher

In this case it looks like a @dune.eth UI bug that's linked to the wrong decoded project, but it does appear possible to overwrite the ABI and 'poison' the decoder? (Not going to test this theory for obvious reasons 😅 )

https://warpcast.com/rjs/0xaa5ed24b

Always thought the abi section couldn't be overwritten from the default. Or prob need manual approval if so. But yeah ui bug probably would explain it heh

Yeah I have no idea if there's a manual approval step; the docs say you can provide an ABI but not what happens if you provide one that differs from the chain explorer:

Yes, if it can't auto fetch the abi you can enter one manually

Yeah I have no idea if there's a manual approval step; the docs say you can provide an ABI but not what happens if you provide one that differs from the chain explorer: https://docs.dune.com/web-app/decoding-contracts