Closed 0xcivita closed 8 months ago
@0xcivita does your script have type=3
somewhere in it? We don't support type 3 transactions (not even sure what EIP that type is)
@fubuloubu not that I can see. I pulled example.py
from the silverback repo but renamed to main just to test the setup and get started. Removed the event handlers and only kept the new block handler.
Opened the repo up for the script. Works on mainnet though so not sure where the issue is?
@fubuloubu not that I can see. I pulled
example.py
from the silverback repo but renamed to main just to test the setup and get started. Removed the event handlers and only kept the new block handler.Opened the repo up for the script. Works on mainnet though so not sure where the issue is?
Can try adding type=2
to your transactions, if that works then maybe it is an improper default somewhere
Hm ok, but in the example.py
there are no transactions yet? Simply polling for new blocks unless I'm mistaken. There's a call to block.transactions
to get number of transactions in a block which executes a query I think, but when I comment this out and simply return context.state.block_count
I get the same error.
but when I comment this out
The block.transactions
call makes sense, since that indeed executes a query to fetch a range of transactions from the current block, and perhaps there's a new transaction type we are not accounting for yet. However, can you make sure this is indeed commented out in the version of the bot that you are running? Would help us chase down root cause here.
Also if you can somehow figure out which transaction hash it is tripping up on, we can definitely fix the bug by repeating it
Okay, I think I figured it out, EIP-4844 adds new type 3 transactions for blob support: https://eips.ethereum.org/EIPS/eip-4844
Found a relevant txn type that Ape currently does not decode: https://goerli.etherscan.io/tx/0xd2882bae0d79a6c8e0fbf0089bbcb4b2eef3a1365471ad9f779b06a41ba47d3c
Oh, that's actually super cool to see on testnet! Guess it's an ape
level issue
On our end will focus on testing the script on another network until type 3 blob support is in ape
:)
Oh, that's actually super cool to see on testnet! Guess it's an
ape
level issue
yes it is, we are tracking here: https://github.com/ApeWorX/ape/pull/1928
nice! will keep an eye out on progress
merged it but didn't release until right now!
upgrade to Ape v0.7.9 please
Environment information
ape
and plugin versions:What went wrong?
Attempted to run the
example.py
file renamed asmain.py
And obtained the following error
when attempting for both sepolia and goerli.
ethereum:mainnet:alchemy
runs the example app fine for me.Full output
How can it be fixed?
Unsure if this is an
ape
issue or asilverback
issue given the error seems to stem fromape_ethereum
plugin.