Web3.py: Constructor Functions

Created on 22 Feb 2018  路  23Comments  路  Source: ethereum/web3.py

Continuation of #577

Add constructor method to replace and expand on the current contract.deploy() capability. Proposed API:

  • contract.constructor(*args, **kwargs).estimateGas()
  • contract.constructor(*args, **kwargs).transact()
  • contract.constructor(*args, **kwargs).buildTransaction()
picture carver

Most helpful comment

Leave a comment here to confirm that I am still working on this issue, so that gitcoin bot will not remove me from the issue :)

picture zheli on 16 Mar 2018
👍2 😄1

All 23 comments

@dangell7 started in on this with #595 -- are you interested in continuing the work? You should be unblocked now that the chainID issue is fixed. I think we can get another bounty on just this piece, since the fallback work in #577 was more than expected.

carver picture carver on 22 Feb 2018

confirmed that I'll bounty this issue with an equivalent ETH amount as the previous one.

pipermerriam picture pipermerriam on 22 Feb 2018

How about you @zheli - are you interested and available to work on this? (given that an equivalent bounty is coming soon)

carver picture carver on 23 Feb 2018

I would be happy to work on this issue :)

zheli picture zheli on 24 Feb 2018

@zheli still waiting for txn to confirm, but i just attached a 0.4 eth bounty to this. We'd like to get this closed out quick so if you're available to work on it and want to do it.... go for it!

pipermerriam picture pipermerriam on 28 Feb 2018

Yeah sorry about going mia. I鈥檝e been busy, the team switched to .js 馃様but it really should just need to be tested. I鈥檝e been using the forked repo for awhile now. You鈥檙e welcome to copy anything I wrote.

dangell7 picture dangell7 on 28 Feb 2018

I used too low a gas price yesterday evening, trying with a higher one. Either way, this issue will have a bounty.

pipermerriam picture pipermerriam on 28 Feb 2018

__This issue now has a funding of 0.4 ETH (346.49 USD) attached to it.__

  • If you would like to work on this issue you can claim it here.
  • If you've completed this issue and want to claim the bounty you can do so here
  • Questions? Get help on the Gitcoin Slack
  • $7705.12 more Funded OSS Work Available at: https://gitcoin.co/explorer
gitcoinbot picture gitcoinbot on 28 Feb 2018

__Work has been started on the 0.4 ETH (346.49 USD) funding by__:

  1. @zheli

__Please work together__ and coordinate delivery of the issue scope. Gitcoin doesn't know enough about everyones skillsets / free time to say who should work on what, but we trust that the community is smart and well-intentioned enough to work together. As a general rule; if you start work first, youll be at the top of the above list ^^, and should have 'dibs' as long as you follow through.

On the above list? Please leave a comment to let the funder (@pipermerriam) and the other parties involved what you're working, with respect to this issue and your plans to resolve it. If you don't leave a comment, the funder may expire your submission at their discretion.

gitcoinbot picture gitcoinbot on 28 Feb 2018

Thx @pipermerriam! I will probably make a new pull request based on the changes in #595.

zheli picture zheli on 28 Feb 2018
👍2

Would love to see this implemented.

nueverest picture nueverest on 5 Mar 2018

Hi @zheli Vivek from Gitcoin here checking in on behalf of Gitcoin Bot, who we're still training 馃檪 any update here? Hope you all are doing well! @pipermerriam @carver

vs77bb picture vs77bb on 8 Mar 2018

Hi @vs77bb sorry I was a bit busy with my daytime job in the past two weeks so I could only work on it during the weekend. I think I will push a work-in-progress pull request this weekend to get some early feedback.

zheli picture zheli on 8 Mar 2018

Leave a comment here to confirm that I am still working on this issue, so that gitcoin bot will not remove me from the issue :)

zheli picture zheli on 16 Mar 2018
👍2 😄1

Hi @zheli this one has returned to an open status on Gitcoin (not sure if on purpose or if it was a mistake)... are you still working on it? I've heard interest from a few people on this so would appreciate an update, if so. Hope you are well!

vs77bb picture vs77bb on 24 Mar 2018

Hi @vs77bb! Thanks for checking out. Yes I am still working on it and trying to finish it up this weekend actually. Perhaps in the future gitcoin should also watch the pull request for updates. I will submit an issue on the gitcoin repo.

Regarding to the issue status on gitcoin, it might be a bug. Who should I contact in regarding to this?

zheli picture zheli on 24 Mar 2018

Thanks @zheli this looks wrapped!

carver picture carver on 27 Mar 2018

__Work for 0.4 ETH (182.11 USD @ $455.27/ETH) has been submitted by__:

  1. @zheli

Submitters, please leave a comment to let the funder (@pipermerriam) (and the other parties involved) that you've submitted you work. If you don't leave a comment, the funder may expire your submission at their discretion.

gitcoinbot picture gitcoinbot on 27 Mar 2018

@pipermerriam will I still get the bounty for this issue? 馃槃

zheli picture zheli on 28 Mar 2018

Lol, well it definitely shouldn't go to me :P

carver picture carver on 28 Mar 2018
😄1

Triggered payment (txn may take some time to confirm)

0x012d386eaa7dd55b272f5facf784b2c17b2a465ba4453c1b8515db6a99c1f665

pipermerriam picture pipermerriam on 29 Mar 2018

@pipermerriam thx!

zheli picture zheli on 29 Mar 2018

__The funding of 0.4 ETH (162.71 USD @ $406.76/ETH) attached to this issue has been approved & issued to @zheli.__

gitcoinbot picture gitcoinbot on 29 Mar 2018
Was this page helpful?
0 / 5 - 0 ratings

Related issues

kaleb-keny picture kaleb-keny  路  4Comments
gutfeeling picture gutfeeling  路  4Comments
veox picture veox  路  5Comments
avatar-lavventura picture avatar-lavventura  路  5Comments
monokh picture monokh  路  5Comments