Replies: 2 comments 1 reply
-
Use Erigon3 |
Beta Was this translation helpful? Give feedback.
0 replies
-
Also without logs of erigon we don’t know what your node doing |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey guys,
I've been trying for almost 4 weeks to get Erigon running properly, and it's been a real struggle. I desperately need a local node to stream directly from the mempool for a time-sensitive project.
Even with my nvme m.2 ssd, the sync process is painfully slow. Last attempt, I finally reached step 10 out of 12 snapshots, but the execution part alone took about 5 days before crashing again. Is this normal, or is something wrong with my setup?
Additionally, I'm struggling with ZMQ for real-time mempool monitoring. With Erigon 2.61.2, I had to set up a Python bridge to connect WebSockets to ZMQ since native support wasn't available. Has anyone successfully used the native ZMQ functionality in newer Erigon versions? Is it significantly more stable than using a bridge? Which kind of flags are you using
This is my current configuration:
nano start-erigon.sh
#!/bin/bash
/mnt/d/ethereum-node/erigon/build/bin/erigon
--datadir="/mnt/d/ethereum-node/erigon-data"
--chain=mainnet
--http
--http.api=eth,txpool,erigon,engine,debug,net,web3
--http.port=8545
--http.vhosts=*
--ws
--ws.port=8546
--prune=htc
--prune.h.older=10000
--prune.r.older=10000
--prune.t.older=10000
--prune.c.older=10000
--snapshots
--maxpeers=100
--private.api.addr=localhost:9090
--db.read.concurrency=40
--txpool.gossip.disable=false
--torrent.download.rate=75m
--torrent.upload.rate=50m
--log.console.verbosity=info
--nat=none
--torrent.port=42069
chmod +x start-erigon.sh
./start-erigon.sh
Any tips to accelerate the process or at least get it running stably would be hugely appreciated!
Beta Was this translation helpful? Give feedback.
All reactions