At this moment network works fine. To get back on track do the following steps: 1. Download latest DB https://www.dropbox.com/s/rk4n2i1rppmmwwo/AmberCoin_0512.rar?dl=0 2. Delete peers.dat 3. Use this .conf to sync correctly:listen=0 connect=ambercoin01.mooo.com 4. When wallet is synced turn it off. 5. Change .conf to:listen=1 addnode=ambercoin01.mooo.com 6. Start wallet again. 7. Turn on POS minting
made exactly this and my wallet say its sync at 612700.. and i have -31000 coins in my wallet than normal.. so still not working for me.. can someone tell me what in his .conf file is? because with that listen=0 connect=ambercoin01.mooo.com is nothing working for me Retry this but only with steps 1 and 2, without any conf file.
|
|
|
Hey there. Currently I am not getting data from bluetrade, you will have to get this on a supported exchange first. That is polo, bittrex, cryptsy, bter or ccex.
|
|
|
Skein coins (MYR and DGB) show in the frontpage list but you can't input your hashrate at the top. Why is that?
They were never enough skein coins to add a form for it. At some point I have removed DGB and MYR skein from the main list, but someone asked for them to be returned. No one ever requested any skein coins and I would rather have one spot open just in case.
|
|
|
My pool's wallet had 8 peers now and stable for more than 24h now! No fork, few orphans... seems good for the moment. Keep crossing my fingers! Join now ! My wallet seems to be on your chain, 7 active connections. Question is, if this is the correct chain. Will join the pool to raise PoW difficulty and help to secure it.
|
|
|
FYI, DGB forked to digispeed today. Block reward needs adjusting.
Thanks for the info, the daily amount should stay the same though, updated. Taking down DGB for now till I can find a reliable source that is not forked
|
|
|
I have finally made a successful update.
Reverted back to wallet state of 24th of November (before fork), deleted only peers.dat Launched wallet 3.0.3 and it synced without problems. Now sitting on 7 connections and staking.
Maybe it will help someone.
Sounds promising. Could you please post your conf file. I'm not sure if I have the right one. Thanks. I am not using any. Just fired 3.0.3 wallet on 24th of November files. (But deleted peers.dat) It may require a pre-fork copy of ambercoin appdata to work. Still going nice with 7 connections, no conf file used and just checked to be on the same chain as ssdpool.
|
|
|
I have finally made a successful update.
Reverted back to wallet state of 24th of November (before fork), deleted only peers.dat Launched wallet 3.0.3 and it synced without problems. Now sitting on 7 connections and staking.
Maybe it will help someone.
Sounds promising. Could you please post your conf file. I'm not sure if I have the right one. Thanks. I am not using any. Just fired 3.0.3 wallet on 24th of November files. (But deleted peers.dat) It may require a pre-fork copy of ambercoin appdata to work.
|
|
|
I have finally made a successful update.
Reverted back to wallet state of 24th of November (before fork), deleted only peers.dat Launched wallet 3.0.3 and it synced without problems. Now sitting on 7 connections and staking.
Maybe it will help someone.
|
|
|
The reported difficulty is too low for the real network hashrate.
This leads to crazy profitability calculations, as this difficulty of 7-10 would be more appropriate for 2,5Mhash network. For example, currently MUE (also a quark coin) is having around 350Mhash network with difficulty of 880. Yours should be even higher. Also, MUE had the same problem recently and they fixed it.
Could you please look into this?
Yes I will look into this. Any news?
|
|
|
The reported difficulty is too low for the real network hashrate.
This leads to crazy profitability calculations, as this difficulty of 7-10 would be more appropriate for 2,5Mhash network. For example, currently MUE (also a quark coin) is having around 350Mhash network with difficulty of 880. Yours should be even higher. Also, MUE had the same problem recently and they fixed it.
Could you please look into this?
|
|
|
Someone named "Di Cabrio" requested a wallet update from my site and to report back here. Just for the record my site does not host wallets, but uses external stats (suprnova pool in this case), so no update is required. Thank you for the notification though, whoever you are As far as I can see, we are not changing any specs? Just a security update?
|
|
|
Possible that its trying to counter the low diff we had earlier. (many blocks insterted) I wonder what `gethashespersec` is wallet returning now.
|
|
|
Replaced chacha16 with chacha14 due to Ultracoin switch.
|
|
|
Added support for NiceHash ChaCha(16) algo.
|
|
|
Hey, Is the ScryptJane(Nf16) the same algo as Ultracoin(UTC)? I cant find any ANN of this leocoin to confirm, pretty shady
|
|
|
So who still has hope?
|
|
|
As of recent DGB Digibyte block reward calculation is perfectly on spot. On a side note, nicehash mining is producing the most stable results, just pick your favourite algo https://www.nicehash.com/index.jsp
|
|
|
Cryptonit was the promotion / lottery about cloud shares concluded? I mean the latest one that was supposed to sell 160 tickets (I think), but was cut short.
|
|
|
|