Web3.py: Permit bytes addresses for programmatic API usage

[carver]

Update Web3.py to accept length=20 bytes values as an ABI address. This will be the only format for addresses that Web3.py accepts without a checksum.

• The pythonic_middleware and abi_middleware will need to be updated to handle this.
• The code used for contract parameter validation will need to be updated.
• The code related to filters may need to be changed too.
• Tests need to be written for contract and base API (web3.eth.getBalance, etc) use cases.
• Documentation needs to be updated to indicate that raw bytes addresses are accepted.

also see #883

The implementation should aim to be as simple as possible, potentially normalizing to a common address format using a middleware or something rather than adjusting every API to support this new format. Use your discretion on whether this is the right approach.

[pipermerriam]

Change likely involves updating pythonic_middleware and abi_middleware

[gitcoinbot]

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

---

__This issue now has a funding of 0.3 ETH (175.93 USD @ $586.42/ETH) attached to it.__

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $21,419.41 more funded OSS Work available on the Gitcoin Issue Explorer

[pipermerriam]

@iamonuwa PR should include implementation, tests, and documentation updates.

[LefterisJP]

So once this issue is addressed we will be able submit byte encoded addresses to web3.py function? Yay!

[pipermerriam]

Main description of this issue has been updated with a more complete spec. Whoever implements this will still need to do some digging to ensure they cover all of the APIs.

[iamonuwa]

@pipermerriam cool, thank you

[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 8 months, 1 week ago.
Please review their action plans below:

1) voith has started work.

I'll have a look at the code and see what's best to get this implemented!

Learn more on the Gitcoin Issue Details page.

[voith]

@iamonuwa Are you working on this? Today, in the morning I saw that the issue was claimed by you. However, the issue page on gitcoin doesn't show any info about it being claimed. Let me know if there's some problem! In fact this issue just appeared on my daily gitcoin open issues feed.
I just went ahead and claimed the issue, however if you'd like to continue then I have no problem!

[voith]

Also noticed that the gitcoin issue page shows a bounty of 0.4 ETH. However, the gitcoin bot has commented saying that its 0.3 ETH. @vs77bb Any idea why?

---

[pipermerriam]

@voith if there's no open pull request and you want to run with it, 👍

[vs77bb]

I spoke with @iamonuwa, he released the bounty so it's all yours @voith. Also, the .3ETH should update to .4ETH (I added to the contribution slightly once it opened up as I wanted to see it complete.

Will track a ticket for the update to flow through to Gitcoin Bot here when a contribution is added. Good luck with this one, @voith.

[voith]

commenting here to inform the gitcoin bot: I've opened a WIP PR at #893

[gitcoinbot]

@voith 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!

• [x] warning (3 days)
• [ ] escalation to mods (6 days)

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

[voith]

@gitcoinbot Yes I'm working on this. I've added a new commit to the WIP PR and also left a comment on some investigation that I've done.

[gitcoinbot]

@voith. :wave: thanks for the atMention, but you need to install @gitcoinbot on this repo for me to be able to respond. More details in the documentation.

:v:
@gitcoinbot

[vs77bb]

Thanks for the comment @voith!

[carver]

you need to install @gitcoinbot on this repo for me to be able to respond

I added gitcoinbot to web3.py, py-evm, and eth-account. I'm not sure how critical it is, so we can incrementally add it more places when it seems necessary.

[gitcoinbot]

@voith 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!

• [x] warning (3 days)
• [ ] escalation to mods (6 days)

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

[voith]

@gitcoinbot PR #893 is complete IMO. It did not get merged on Friday as there was one test failure which has now been resolved. But looks like @carver will be away for a week, so it might be kept on hold for some time.

[gitcoinbot]

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

---

__Work for 0.4 ETH (183.88 USD @ $459.7/ETH) has been submitted by__:

1. @voith

@vs77bb please take a look at the submitted work:

• PR by @voith

---

• Learn more on the Gitcoin Issue Details page
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
  $16,908.58 more funded OSS Work available on the Gitcoin Issue Explorer

[voith]

@vs77bb I just got a notification that the issue expires in a day. I have completed the task in #893. Please do whats needed! :)

[gitcoinbot]

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

---

__The funding of 0.4 ETH (192.06 USD @ $480.15/ETH) attached to this issue has been approved & issued to @voith.__

• Learn more at on the Gitcoin Issue Details page
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $17,846.63 more funded OSS Work available on the Gitcoin Issue Explorer

[voith]

@vs77bb Thank you, I received the bounty. @carver IMO, this issue can now be closed.
@LefterisJP you can now pass byte addresses to web3.py on master. This should be out in the next release.

[LefterisJP]

Thank you so much @voith

[pipermerriam]

Thanks to all of you.

[voith]

@LefterisJP web3 v4.5.0 has been released. Byte addresses will now be accepted in v4.50.
Let me know if there are any issues!