-
Notifications
You must be signed in to change notification settings - Fork 35
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
feat(contracts): add gas estimation layer example and use recommended layers across examples #33
Conversation
…ploy_from_contract` and `deploy_from_artifact` examples
.map(|mut tx| { | ||
tx.set_chain_id(anvil.chain_id()); | ||
tx | ||
}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Expected as a method directly accessible on contract_builder
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The default case will likely be resolved by the new FillTxLayer
proposal: alloy-rs/alloy#374 but generally still a good method to have direct access to I think.
let contract_address = | ||
contract_builder.gas(estimate).gas_price(base_fee).nonce(0).deploy().await?; | ||
let contract_address = contract_builder | ||
.from(alice) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Expected not to be required, should be implicit that alice
is the from
if set as signer
Now unblocked: alloy-rs/alloy#406 Will likely require a refactor and reconsideration of proposed changes |
Close in favor of #50 |
Closes #12
Blocked by upstream changes to improve API in alloy-rs/alloy#406
Specifically around current handling of
from
field, missingchain_id
field (handled in FillTxLayer) and ordering of layers.