fix: pydantic v2 API; incorrect encoding

[fubuloubu]

What I did

fixes: #

How I did it

How to verify it

Checklist

• Passes all linting checks (pre-commit and CI jobs)
• New test cases have been added and are passing
• Documentation has been updated
• PR title follows Conventional Commit standard (will be automatically included in the changelog)

[fubuloubu]

@antazoey, do you know why ReceiptAPI.transaction_hash is now a bytesarray-like list of uint8 integers? (see 2740493)

[antazoey]

@antazoey, do you know why ReceiptAPI.transaction_hash is now a bytesarray-like list of uint8 integers?

I don't think Receipt has a field named transaction_hash:

In [3]: tx.transaction_hash
ERROR:    (ApeAttributeError) 'Receipt' object has no attribute 'transaction_hash'. Also checked extra(s) 'transaction'.

There is a field called txn_hash though; it's always been called that.

In [7]: tx.txn_hash
Out[7]: '0xb96c723ea53398faa98ad3b746cf9f94b76f09241f0a7e48fb3c00b232c23e03'

For 0.9, I would good with renaming the field to transaction_hash though.

[fubuloubu]

@antazoey, do you know why ReceiptAPI.transaction_hash is now a bytesarray-like list of uint8 integers?

I don't think Receipt has a field named transaction_hash:

In [3]: tx.transaction_hash
ERROR:    (ApeAttributeError) 'Receipt' object has no attribute 'transaction_hash'. Also checked extra(s) 'transaction'.

There is a field called txn_hash though; it's always been called that.

Okay I have to trace down how that gets in there...

In [7]: tx.txn_hash
Out[7]: '0xb96c723ea53398faa98ad3b746cf9f94b76f09241f0a7e48fb3c00b232c23e03'

For 0.9, I would good with renaming the field to transaction_hash though.

We shouldn't have to do that, no