Hi everybody, wondering what my best option is for getting the ABI of a compiled smart contract (source unpublished). Are there any tools that can rebuild it from a decompiled version of the contract perhaps? Or am I best recreating it based on known interactions with the contract?
Jun 25, 2021, 11:16 AM
I think there is a decompiler on etherescan and the decompiled code would take some extra work to (manually) extract ABIs, but I'm not sure.
Jun 25, 2021, 12:00 PM
Yep I think that might be the process here. Cheers
Jun 25, 2021, 12:00 PM
A quick question: if a contract factory has generated quite a bunch of contracts by cloning, and one parameter is desired to be updated across all such contracts, what is the best approach for achieving that? Suppose a setter is available for all such contracts. And a good measure would be low gas costs, and easy to implement and quick in execution.
Jun 25, 2021, 12:10 PM
In my opinion, the best solution would be if you store this value in the factory contract, and request it from the clone contract when necessary.
Jun 25, 2021, 12:50 PM
Yes, this is a good approach. I forgot to mention one more constraint, which is the generated contracts do not belong to me, or any known individual. They are in the wild.
Jun 25, 2021, 12:52 PM
I do not understand. What prevents the clone contract constructor from accepting the factory address to which the contact will contact?
Jun 25, 2021, 12:55 PM
I think we cannot assume that contract owners would update contracts by contacting the factory, and in the worst, they perhaps do not even know about it.
Jun 25, 2021, 12:57 PM