Wallet won't sync need more nodes plz.
You should have no issue with the DNS seednodes that are hardcoded, but here you go:
"addr" : "45.32.178.232",
"addr" : "108.61.216.195",
"addr" : "54.37.46.84",
"addr" : "71.213.38.4",
"addr" : "82.70.129.110",
"addr" : "208.38.200.241",
"addr" : "90.196.80.78",
"addr" : "185.220.100.247",
"addr" : "191.177.203.233",
If peers are dropping you, you may want to verify your copy of the blockchain against an explorer. If you find you've forked, a recent snapshot is available via the sterlingcoin.org website (Download > Recent Snapshot).
Sorry it is giving you difficulties.
Happy Mother's Day any moms out there!
How do I know if I forked without an explorer now? My wallet syncs to 49,466 blocks to go and seems to be stuck there.
And a lot of mined coins the wallet says generated but not accepted.
thx
Sorry for the current absence of an explorer. One is planned to re-launch in the near future. Funding constraints.
An easy way to know if you are on the supported blockchain is to enter the
faucet. If you receive the faucet payout (sent every 24 hrs), you'll know you are "on-chain." Peer count is another indicator, but not necessarily indicative alone. As the current network stands, if you have a small handful of peers or more (>= 3, I'd say), you most likely are on the supported chain.
If the wallet appears stuck for long, give it a restart or two.
Blocks will say, "generated but not accepted," until your copy of the blockchain reaches that point in the history of the public ledger when it occurred. A recent snapshot was posted to the website for download, if that is helpful to anyone.
Again, sorry for the 'explorer absence.' It will not remain that way for long.
Happy Spring 2023, Sterlingcoiners!
Thx
Sorry for the very late response but this is my wallet synced by date but not blocks. Note the date.
I tried the faucet too.
Its like there are 2 chains its trying to sync. It flipped back and forth displaying 6,000 and then 104,989 blocks to go.
Hi mate, sorry for the slow reply, also.
Thanks for reporting this. But I've not seen any of the infrastructure nodes on another chain, and certainly not one 100k blocks ahead. I suppose there could be an unmaintained node out there somewhere that has spun up that many blocks in its own fork over a long time. That node would be banned of course, but bans expire. It would try, and fail, to peer again with other nodes. This
may have been what you observed.
The network has had issues of slow blocks as of late. A few large bag holders have been moving and reorganizing coins out of wallets that are many years old. This has led to inconsistent nethash, resulting in inconsistent block times. This could have contributed to the glitch you observed also. At any rate, you do want to be sure your node conforms with
https://chainz.cryptoid.info/slg/. Thank you for taking the time to maintain your node!
On a different note, and happy to announce, SLG has a new exchange:
https://mubadil.com/en/?market=slg_usdt
