-
Notifications
You must be signed in to change notification settings - Fork 43
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
[RPC] Pending txs event not working #1134
Comments
I can't seem to be able to reproduce it neither on v1.2.15.7 nor on latest zkevm Here is what I get on Cardona:
|
Hi @V-Staykov the problem is not that it connects to the event, the problem is that it doesn't emit pending txs! Is that a feature or a bug? |
Sorry, I got a bit confused, but got it now. So this currently works on a sequencer, but the RPC nodes don't hold the txpool, so they are not notified on a new pending transaction and thus the WS subscription is not updated. maybe @mandrigin can elaborate on when and if it is planned for our txpool to copy the sequencer one. |
@V-Staykov Thanks for the response and summonning @mandrigin . Me and my team are building a block explorer for zkevm (https://polygon-zkevm.txain.com/) and would like to have access to show them if possible. |
we have plans to re-introduce p2p back to cdk-erigon, then each node will have its own txpool, and then all the pending events will work as expected. |
System information
output of git branch
* (HEAD detached at v1.2.15.7) zkevm
Config File
Erigon Command (with flags/config):
./build/bin/cdk-erigon --config="/mnt/ethereum/cdk-erigon/hermezconfig-mainnet.yaml" --ws
Erigon RPC
./build/bin/rpcdaemon --datadir=/path/to/cdk-erigon/data --txpool.api.addr=localhost:9091 --private.api.addr=localhost:9091 --http.api=eth,erigon,web3,net,debug,trace,txpool,zkevm --ws --ws.compression
Expected behaviour
When I connect to the pending txs event, txs are emitted
Actual behaviour
It doesn't emit pending txs
Steps to reproduce the behaviour
The text was updated successfully, but these errors were encountered: