Author

Topic: [ANN][DGC] Digitalcoin | Multi-algo & Masternodes | Established 2013 - page 207. (Read 523478 times)

member
Activity: 90
Merit: 10

If you are looking for a pool; Server next.afraid.org:8119 still there and fully reliable since the first day.


I use this server (http://next.afraid.org:8119), and everything is fine there. A good choice.

I'm still here: http://next.afraid.org:8119, this one is solid and efficient with a low dead on arrival... When we have a good pool, it's  important to support it. And continue to have the expected payout.

This one is fine, my rigs has worked a while on this server without any issue.
sr. member
Activity: 448
Merit: 250
could use some more hashrate at mine, http://digitalcoin.scryptmining.com , but I digress.  Look forward to the future of this coin regardless of whether my pool ever picks up the pace. Great work by dev and everyone else who's been so involved  from the start.
member
Activity: 115
Merit: 10

If you are looking for a pool; Server next.afraid.org:8119 still there and fully reliable since the first day.


I use this server (http://next.afraid.org:8119), and everything is fine there. A good choice.

I'm still here: http://next.afraid.org:8119, this one is solid and efficient with a low dead on arrival... When we have a good pool, it's  important to support it. And continue to have the expected payout.
legendary
Activity: 966
Merit: 1052
Should have an update fixing any wallet issues Tuesday if all goes well.
sr. member
Activity: 662
Merit: 250
I just keep the wallet closed until I want to accept my miner earnings, then close it again.  I don't have to do this with any other wallet, but it's a minor annoyance is all. I won't be forwarding a port, btw, personal choice.
hero member
Activity: 1395
Merit: 505
My p2pool is still cranking along up for 4.6 continuous days now zero downtime.  Finding ~20 blocks per hour at current diff

http://www.p2pool-dgc.com:9500/static/
full member
Activity: 154
Merit: 100
Hack The Planet
Well i have the wallet issue too ... i never worried cuz i close and reopen and works fine .... hope is not going to be worse ... and probably we need to address this sooner than later . Grin

Finally a good pool http://digicoinpool.com/ ->after going thru 4 or 5 bad managed or scam pools.  Shocked
legendary
Activity: 966
Merit: 1052
Looking into it and how to avoid it. Yeah, everyone seems to experience it at the early stage, but I think it can be avoided.
sr. member
Activity: 447
Merit: 250
I'm working on the dnsseed but keep getting busy with other things. Maybe someone can help with it? Smiley

I haven't heard of this wallet thing for days, did it just start happening?

Also, having the proper port forwarded makes sure the client can connect to appropriate nodes and doesn't look elsewhere.
My two machines have the wallet trying to sync with the litecoin network a lot.  When one client goes out-of-sync, the other follows shortly afterwards.  I cannot port forward a specific address as both wallets are being used.  I had some pages opened to show that other scrypt clients have had the same issue and what they did to correct it, but I miss clicked with my mouse and closed my browser.  I will go through the history to see if I can find them, but it may take awhile.  I just got back from playing poker and drinking to much, so my train of thought is very random and pauses quite a bit on me.  
legendary
Activity: 966
Merit: 1052
There's a client update scheduled for Tuesday.


Also, there is important news for our community:

https://bitcointalksearch.org/topic/ann-a-revolution-in-crypto-currency-216267


legendary
Activity: 2268
Merit: 1092
I'm also still experiencing my client going off with the fairies. The odd thing is that when it latches onto another chain it downloads the blocks really really slowly... like one block per 5 seconds. To download the 328k estimated blocks it wants to (LTC?) would take 20 days.

I don't think port forwarding has anything to do with it as my workstation has a globally routed IP and port 7999 is open.

When will a client with checkpointing or some other verification method be released?
legendary
Activity: 966
Merit: 1052
Try it and let me know.
full member
Activity: 163
Merit: 100
Do you guys have port 7999 forwarded in your router?

Nope
legendary
Activity: 966
Merit: 1052
legendary
Activity: 966
Merit: 1052
I'm working on the dnsseed but keep getting busy with other things. Maybe someone can help with it? Smiley

I haven't heard of this wallet thing for days, did it just start happening?

Also, having the proper port forwarded makes sure the client can connect to appropriate nodes and doesn't look elsewhere.
sr. member
Activity: 359
Merit: 250
Do you guys have port 7999 forwarded in your router?

What's the reason of it?
full member
Activity: 134
Merit: 100
Do you guys have port 7999 forwarded in your router?

I know it's not ideal, but could you possibly hardcode a trusted node (and perhaps a couple failsafes...) into the client until the network is big enough to avoid this? I'm not a developer, so feel free to shoot this down as I don't really know what I'm talking about  Grin
legendary
Activity: 1311
Merit: 1000

My client did this at least 5 times today, for now i am ignoring it. Restart of client works well for me  Grin But i also followed troubleshooting guide, it stops for a while, but then it came back.  Huh

My client just started to download the entire blockchain again after sitting idle for a few hours. Never seen a client do that before. Interesting...

Update: Well it started to download the blockchain again and locked up.

Restarted and synced fine. The client seems a bit unstable...
legendary
Activity: 966
Merit: 1052
Do you guys have port 7999 forwarded in your router?
full member
Activity: 163
Merit: 100
My DGC client has started losing sync with the network again, after following all steps in the troubleshooting guide. Any suggestions for fixing it?

My client did this at least 5 times today, for now i am ignoring it. Restart of client works well for me  Grin But i also followed troubleshooting guide, it stops for a while, but then it came back.  Huh
Jump to: