Update Docs to Show Return of Eth.sendRawTransaction() to be HexBytes, not string.

[ghost]

What was wrong?

The documentation was not clear that the return type of Eth.sendRawTransaction is a HexBytes object, as originally pointed out by @wjmelements in Issue #1367.

How was it fixed?

updating web3.eth.rst, line ~638.

Cute Animal Picture

[kclowes]

Thanks for the doc update @crawfordleeds! What was your reasoning behind changing the address in the example?

[ghost]

Good catch, that was a mistake, and likely a remnant of some copy and pasting with another project. Sorry about that. I pushed a reversion to the original address. Thanks!

[kclowes]

Awesome, thanks! 🚢

[ghost]

Actually, now that I look into it, don't these addresses need to use the EIP 55 checksum address encoding? I just tried to run the code with the original address, '0xd3cda913deb6f67967b99d67acdfa1712c293601', and receive the following error:

TypeError: Transaction had invalid fields: {'to': '0xd3cda913deb6f67967b99d67acdfa1712c293601'}

It works fine with the one I originally changed it to, '0xF0109fC8DF283027b6285cc889F5aA624EaC1F55'.

Am I mistaken about that? If not, perhaps this is deserving of its own issue because there are a few instances of the docs not using EIP 55 checksummed addresses. I'm happy to take a crack at it too.

[kclowes]

Yep, you're right. They should be using checksummed addresses. Let's keep this PR as-is and open up a new issue to make sure all addresses in the docs are checksums

[ghost]

Sounds great, I'll keep an eye out for that issue.

[kclowes]

@crawfordleeds added the issue! #1388 if you want to take a crack at it. Thanks again!