You are viewing a single comment's thread from:
RE: Echelon has been launched
I played around a bit more, and the port you told doesn't seem to be working anymore.
[2025-12-08 04:55:14] info: [kafka-producer] Runtime detection: host, default broker: localhost:29092
[2025-12-08 04:55:14] info: Correctly using NodeJS v20.19.4
[2025-12-08 04:55:14] info: Starting MeeRay Node...
[2025-12-08 04:55:14] info: Connected to mongodb://127.0.0.1/meeray
[2025-12-08 04:55:14] info: [mongo] Loading and registering token decimals from database...
[2025-12-08 04:55:14] info: [mongo] Finished registering decimals for 8 token(s).
[2025-12-08 04:55:14] info: MongoDB initialized via mongo.init.
[2025-12-08 04:55:14] info: Initializing modules to resolve dependencies
[2025-12-08 04:55:14] info: Core modules initialized.
[2025-12-08 04:55:14] info: Block store initialized with head block ID: 218749
[2025-12-08 04:55:14] info: 1511 accounts loaded in RAM in 75 ms
[2025-12-08 04:55:14] info: 0 tokens loaded in RAM in 3 ms
[2025-12-08 04:55:14] info: 3 witnesses loaded in RAM in 4 ms
[2025-12-08 04:55:14] info: #218749 is the latest block in our db
[2025-12-08 04:55:14] info: Filled 1000 blocks into memory.
[2025-12-08 04:55:15] info: P2P ID: jKhSLChebfmMPQKUHcsG1wazpWFDQgea8FuBRkFJYBPs
[2025-12-08 04:55:15] info: Listening websocket p2p port on: 6001
[2025-12-08 04:55:15] info: Version: 1.6.6
[2025-12-08 04:55:15] info: [notifications] Notifications WebSocket server listening on port 6005
[2025-12-08 04:55:15] info: [kafka-consumer] USE_NOTIFICATION disabled; skipping Kafka consumer initialization.
[2025-12-08 04:55:15] info: Node daemon started successfully.
[2025-12-08 04:55:15] info: All available API endpoints initialized
[2025-12-08 04:55:15] info: HTTP server listening on :::3001
[2025-12-08 04:55:15] info: All modules initialized successfully
[2025-12-08 04:56:15] warn: [DISCOVERY] Critically low peer count (0)! Using witness endpoints as emergency fallback
[2025-12-08 04:57:15] warn: [DISCOVERY] Critically low peer count (0)! Using witness endpoints as emergency fallback
[2025-12-08 04:57:25] warn: Peer connection failed: ws://23.94.30.150:6001
[2025-12-08 04:58:15] warn: [DISCOVERY] Critically low peer count (0)! Using witness endpoints as emergency fallback
There is no fallback to echelon-node1 or node2. Critically low peer count (0) keeps coming up, and I'm not getting any blocks.
So, is it hopeless, or do you have suggestions?
Definitely not hopeless. The problem is that you were trying to sync with the network while being in development mode and without emptying your db. From your logs I can see that you replayed a certain number of blocks already. The low peer count is just a warning (it’s a discovery function for active witnesses). The port I gave you will work if you make sure to first delete your db.
The issue is that you might be missing mongosh so the npm run reset script is not working.
Please just make sure that you have emptied you db, so the last block is 0 before your very first sync and that you are in production mode. Then you won’t have issues anymore. You can add REPLAY_OUTPUT=100 to your .env to have more logs about your replay.
Edit: nevermind the node that I gave you was stuck for some reason. You may want to try again a bit later since it is now replaying. I’ll give more peers addresses soon.
Um, when is soon, roughly? :-)
Hi,
I see that you are mining too :)
Good job
Yes, I'm really happy that it's working now. Big thanks for your help.
What about the front ends we see on meeray.com, dex.meeray.com, etc. - do you plan to make these available as open source as well?
Yes everything in the scope of the proposal was meant to be open source. All the dapps are made with vuejs and share the same architecture so if you are familiar with vue it will be easy to continue to develop them.
Will try to pass all the repositories in public in the coming week.
Great to hear! I'm excited, even though vue is new territory for me. As the saying goes: never stop learning :-)
Currently, only node1 is still producing blocks. I have set up a second node, but it doesn't help.
My question now is, will the sidechain be discontinued in 4 months? I assume that you will then shut down node1 & 2 and without node1 the chain will die, right?
Sorry for the late answer, you can possibly set up an hardfork at a certain block. The chain will not necessarily die without my nodes.
By the way since there is no official discussion channel… we had to introduce a temporary hard fork to lower the number of nodes. You can see it on GitHub. Because you or some other nodes were constantly missing blocks making it hard to reach a consensus (this is mostly due to the low peers count). After syncing back so in few days we will again increase the number of witnesses.
Thanks for your understanding.
Oh, sorry, I only saw your comment by chance, as it wasn't addressed to me. Yes, something went wrong; my node stopped producing blocks, as I wrote in my comment above 21 days ago. I didn't know what else to do, so I switched off the nodes.