You are viewing a single comment's thread from:
RE: Echelon has been launched
Did you manage to run your node?
No, looks like I can't connect, low peer count (0).
At first, I wanted a running node in the current sidechain. Later, if that works, maybe a Witness “upgrade” :-)
This is how it looks at the moment:

My .env:
# Database
MONGO_URL=mongodb://127.0.0.1
#MONGO_DB=echelon # empty
MONGO_DB=meeray # DB from mongorestore
# Kafka
KAFKA_BROKER=10.70.85.104:9092
KAFKA_ADVERTISED_LISTENER=PLAINTEXT://10.70.85.104:9092
# Notification System (must run Kafka)
USE_NOTIFICATION=false
# Steem
STEEM_ACCOUNT=echelon-m3
# Witness Keys => Maybe later
# WITNESS_PUBLIC_KEY=
# WITNESS_PRIVATE_KEY=
# P2P Networking
# comma-separated list, e.g. ws://23.94.30.150:6001,ws://peer2:6001
# Peers from https://api.meeray.com/peers
# PEERS="ws://::ffff:23.94.30.150:59428,ws://23.94.30.150:6001"
PEERS=""
P2P_PORT=6002
# HTTP API
API_PORT=3002
USE_STEEM_BRIDGE=false
STEEM_BRIDGE_ACCOUNT=echelon-node1
STEEM_BRIDGE_ACTIVE_KEY=XXX
STEEM_TOKEN_SYMBOL="STEEM"
SBD_TOKEN_SYMBOL="SBD"
#
LOG_LEVEL=info
NODE_ENV=development
Any ideas? I'm standing in the forest...
You must publish your public key using the witness_register contract
I know how to do this with cli_wallet for Steem-Witness, but unfortunately I have no idea how to do it here.
It would be great if you could give me a tip on this. I'd be happy to reward you with some of my newly created ThankYouTokens (TYT) :-)
Ok first empty your db (npm run reset) then change your NODE_ENV to production and use ws://23.94.30.150:6001 as one of your peers, then just run npm run start ✌️ if you don’t want to replay the whole history you can simply do npm run restore after your reset too.
Edit your problem was probably about the node_env set to development
Okay, now something's happening :-) Thank's a lot! The node is reading blocks, but unfortunately the following message keeps appearing:
warn: [PEER_LIST] Below consensus threshold! (1/2)Can you tell me a second peer?