New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing r when I was trying to get transactions from block #4635
Comments
@yarikMyroniuk You can try out this code to retrieve all transactions from the latest block
If you want all transaction details from a specific block, just change the 'blockNumber' value to your desired block number, then run the code to get all the transactions.
|
@mahatotarit I wanted to do without method getTransaction by hash |
Could you please explain exactly what you want in detail ? I'm here to help with your work. |
@mahatotarit |
Can you provide example ? |
You sent example with this code
but this method has a better alternative like getBlock(block, true) which already has transactions in field "prefetchedTransactions", but with zkSync and with zkLinkNova, it doesn't work because I received this error: |
@mahatotarit |
Same error now after successful transaction on Gnosis. 100% reproducible on our projects. |
Please provide your full code. |
Seems reliably reproducible by me on gnosis chain on different wallets (Metamask and Rabby) |
It looks like they are using a custom type |
@ricmoo |
@ricmoo Gnosis doesn't use any non-standard type but the bug is repeatable about 70% of the time. If you could point me out where to start debugging - I'd love to dive in. |
Ethers Version
6.7.1
Search Terms
I saw the same issue but about missing v
Describe the Problem
I have the same issue but about missing r instead of missing v but only with zkSyncEra
But If I use method getTransaction(hash), I don't receive any errors
version lib: "ethers": "^6.7.1",
UPD: I was trying to do this with latest version ethers 6.11.1
Code Snippet
Contract ABI
No response
Errors
Environment
node.js (v12 or newer)
Environment (Other)
No response
The text was updated successfully, but these errors were encountered: