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
When using "Import from truffle option", ABIs for contract dependencies are not included. So for example in Solidity, if we have
contract someContract is ERC20
Only the functions in someContract are available in the ABI, ERC20 functions won't exist on the contract object.
I tried to work around this by importing an ERC20 contract separately, but since it is a dependency, the build file does not contain deployment information (eg address on Rinkeby) and thus the import form can't be saved.
Allowing editing of contract addresses in the import form, would be a fast fix to work around. Ideally, smart contract dependencies should have their ABI included with the parent.
I found that instantiating a contract directly with php-ethereum (instead of through GUI) includes all of the expect ABI items.
The text was updated successfully, but these errors were encountered:
When using "Import from truffle option", ABIs for contract dependencies are not included. So for example in Solidity, if we have
contract someContract is ERC20
Only the functions in someContract are available in the ABI, ERC20 functions won't exist on the contract object.
I tried to work around this by importing an ERC20 contract separately, but since it is a dependency, the build file does not contain deployment information (eg address on Rinkeby) and thus the import form can't be saved.
Allowing editing of contract addresses in the import form, would be a fast fix to work around. Ideally, smart contract dependencies should have their ABI included with the parent.
I found that instantiating a contract directly with php-ethereum (instead of through GUI) includes all of the expect ABI items.
The text was updated successfully, but these errors were encountered: