No way to specify block number for eth_estimateGas

[Arachnid]

At present the library doesn't provide any way to specify block number when calling estimateGas (the second parameter to that function). It'd be useful if this was provided, and especially useful if it can be made accessible when automatically estimating gas via build_transaction or transact (in order to be able to specify 'pending').

[carver]

Yup, seems reasonable.

Side note: I'm curious about the use case for pending (which isn't supported in trinity at all). Do you want to use pending because you are broadcasting several transactions in a row, and want to estimate gas based on the presumed state after the previous transaction completes?

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

This issue now has a funding of 170.0 DAI (170.0 USD @ $1.0/DAI) attached to it.

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $17,099.45 more funded OSS Work available on the Gitcoin Issue Explorer

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

This issue now has a funding of 170.0 DAI (170.0 USD @ $1.0/DAI) attached to it.

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $17,099.45 more funded OSS Work available on the Gitcoin Issue Explorer

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

Workers have applied to start work.

These users each claimed they can complete the work by 12 months from now.
Please review their action plans below:

1. sid7430 has applied to start work (Funders only: approve worker | reject worker).

   @vs77bb @Arachnid
   the current code needs to allow a way to pass an optional block number or QUANTITY as stated in the eth_estimateGas RPC method. The quantity should default to "latest" and will need a bit of testing. While we accept the block number in the object eth_estimateGas does not and hence changes in the object need to be made in estimateGas funtion.

This should not take much time but will need to test the same with different clients.

Learn more on the Gitcoin Issue Details page.

[vs77bb]

Hi @sid7430 please feel free to start work here!

[gitcoinbot]

@sid7430 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• warning (3 days)
• escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[sid7430]

Just a bit of festive weekend in my country, Ill be back today and hopefully a PR in a couple of days

…

On Sun, Aug 26, 2018 at 9:45 PM Gitcoin.co Bot ***@***.***> wrote: @sid7430 <https://github.com/sid7430> Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions! - warning (3 days) - escalation to mods (6 days) Funders only: Snooze warnings for 1 day <https://gitcoin.co/issue/ethereum/web3.py/1011/1013?snooze=1> | 3 days <https://gitcoin.co/issue/ethereum/web3.py/1011/1013?snooze=3> | 5 days <https://gitcoin.co/issue/ethereum/web3.py/1011/1013?snooze=5> | 10 days <https://gitcoin.co/issue/ethereum/web3.py/1011/1013?snooze=10> | 100 days <https://gitcoin.co/issue/ethereum/web3.py/1011/1013?snooze=100> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1011 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AjB-01mpLS1nQh07j51gmB7iCOJmpE4xks5uUsmcgaJpZM4WG_yd> .

[vs77bb]

Thanks for the update @sid7430 - definitely would appreciate updates every couple days on progress here!

[gitcoinbot]

@sid7430 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• warning (3 days)
• escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

@sid7430 due to inactivity, we have escalated this issue to Gitcoin's moderation team. Let us know if you believe this has been done in error!

• warning (3 days)
• escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[vs77bb]

@sid7430 has been removed from this ticket. It'll be opened back up soon on Gitcoin!

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

Work has been started.

These users each claimed they can complete the work by 11 months, 2 weeks from now.
Please review their action plans below:

1. ankitchiplunkar has been approved to start work.

   1. Add a new parameter option "block_identifier" in the method web3.eth.etsimateGas

2. Provide default middleware for "block_identifier" such that it can accept hashes, string or ints as inputs and default to 'latest' block in case of no block_identifier provided.

3. Write tests and update docs for the update

Learn more on the Gitcoin Issue Details page.

[vs77bb]

@ankitchiplunkar You've been approved! Please do keep us posted on your progress here, excited to see how it goes 🙂