Open moses966 opened 4 days ago
Might need to wait on 0.9 as this requires web3.py v7
Hi @bitwise-constructs ,
Did you mean waiting on eth-ape version 0.9
from the current version of 0.8.15
?
@moses966 correct, the current 0.9 branch raises a lot of pins including web3 https://github.com/ApeWorX/ape/tree/feat/0-9
The issue is actually in the provider (ape-alchemy):
https://github.com/ApeWorX/ape-alchemy/blob/main/ape_alchemy/provider.py#L116-L122
amoy's chain ID just needs to be added to that list.
Also, we should make ape-alchemy
behave like ape-node
where if it encounters this error, it will automatically add the middleware as well:
https://github.com/ApeWorX/ape/blob/main/src/ape_ethereum/provider.py#L1511-L1530
The issue is actually in the provider (ape-alchemy):
https://github.com/ApeWorX/ape-alchemy/blob/main/ape_alchemy/provider.py#L116-L122
Quicknode too
Description:
I encountered an error while trying to use the ApeWorx Polygon plugin. The error message suggests that the plugin is not handling Proof-of-Authority (POA) chains properly due to missing middleware.
Error Details:
The error seems to indicate that the necessary middleware for handling POA chains has not been injected correctly.
Steps to Reproduce:
pip install ape-polygon
.ape run deploy --network polygon:amoy:alchemy
Expected Behavior:
The plugin should inject the necessary middleware to handle POA chains, similar to what Web3.py’s middleware does for POA networks.
Actual Behavior:
The plugin fails with a
BlockNotFoundError
due to theextraData
field being 100 bytes instead of the expected 32 bytes, indicating missing middleware support for POA chains.Environment:
0.8.15
0.8.0
3.10.12
Ubuntu 22.04.4 LTS
Additional Context:
The error occurs when interacting with a Proof-of-Authority chain like Polygon. According to the Web3.py documentation, the missing middleware should handle the
extraData
field for POA networks by adjusting its size appropriately.Thank you for looking into this!