-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support direct import of contracts compiled with Truffle #226
Comments
I'm implemented this in a fork, along with tests. |
Hmm. Seems there's a requirement that AbiDefinition's equal and hashCode methods include all the ivars. But, given that Solidity functions have flags that don't factor into the uniqueness requirements of the function (e.g., you can add "pure" to a function but that doesn't change the function's uniqueness, which is determined solely by name + argument types, except for constructors where the uniqueness is by name). so, enforcing this in Java seems not to line up with the thing being modeled. |
Implemented in #228. |
Better support for a hybrid dev env in which Truffle is used for the Solidity code including testing and deployment.
This would allow, for example, access to the deployed addresses without manual intervention.
It would also mean that the .abi and .bin inputs would be precisely those generated and used by Truffle.
As a side-effect, keeping track of addresses would allow support for looking up contract addresses on the generated instance - though integration with web3j's deploy mechanism means those values would not survive restart but would revert to the values in the generated code.
The text was updated successfully, but these errors were encountered: