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
I think ethcontract should create its own runtime representation of contract data instead of using the Truffle artifact representation. I think it would look something like this:
Doing this would also allow us to distinguish between what is needed at runtime (contract ABI and networks map) and what is additionally needed at generation time (documentation). Doing this could also simplify some of the contract traits that are currently needed for linking, fetching the deployed contract for a network, and new deployments as they could all operate over this runtime representation.
The text was updated successfully, but these errors were encountered:
I think
ethcontract
should create its own runtime representation of contract data instead of using the Truffle artifact representation. I think it would look something like this:Doing this would also allow us to distinguish between what is needed at runtime (contract ABI and networks map) and what is additionally needed at generation time (documentation). Doing this could also simplify some of the contract traits that are currently needed for linking, fetching the deployed contract for a network, and new deployments as they could all operate over this runtime representation.
The text was updated successfully, but these errors were encountered: