[SNC/❄] Snowcoin | PoS SHA256 coin | launched 7 December 2013 | Winter is coming

[atta2k15]

i have the wallet running with linux.

top! 

[1715569309]

1715569309

[atta2k15]

[2014-01-08 23:59:49] Found block for pool 0!
 [2014-01-08 23:59:50] Network difficulty changed to 3.23k (23.09Gh/s)     
 [2014-01-08 23:59:50] New block detected on network
 [2014-01-08 23:59:59] Found block for pool 0!
 [2014-01-09 00:00:00] Network difficulty changed to 3.27k (23.45Gh/s)     
 [2014-01-09 00:00:00] New block detected on network
 [2014-01-09 00:00:14] Found block for pool 0!
 [2014-01-09 00:00:15] Network difficulty changed to 3.33k (23.82Gh/s)     

[platti]

is this from cgminer?

[atta2k15]

is this from cgminer?

yes/no

never understood who was first cgminer or bfgminer
i use both.

[platti]

"moneysupply" : 65660000.00000000,

there are more than 65 million coins in circulation?

[atta2k15]

"moneysupply" : 65660000.00000000,

there are more than 65 million coins in circulation?

thats quite possible with this low diff


but cant find any documentation on this , SNOW ?

[platti]

i am mining, but i dont find any block. 3k diff is to high for me

[atta2k15]

will mine an other coin now, diff should drop every 10 min

[platti]

first 10 k blocks are 5 k coins -> 50 mio
and than 6400 with 2,5 k -> 16 mio

together 66 mio at block 16400

[Marty19]

check it again.
Or add some more debug to it.

But it works on all of my PCs...

if its released 5 days ago, why is the executable still with date 2013-12-23?  

see:
https://github.com/snowcoin/snowcoin/releases/

snowcoin-qt-1.0
snowed1 released this 5 days ago · 0 commits to master since this release

It was compiled at 2013-12-23, but I forgot to upload it.

I did a clean install on a clean machine and all worked ok. Then I copied my old wallet.dat over and the problem started again. Swapped back to the new clean wallet.dat and problems continued.

Looks like its an issue with the wallet file.

[atta2k15]

Looks like its an issue with the wallet file.

use new one, and sent over any coins.
daemon should work to make transfer


i downloaded the new one, and started working on windows.
Same as now can be downloaded.

Weird thing is that the date of executable is still the same,
but like SNOW mentioned, he forgot to upload it...

[platti]

i had this with betacoin, i killed all files in the .betacoin-folder and only let old wallet.dat in it. then i read blockchain again . and than it worked fine

[Marty19]

Looks like its an issue with the wallet file.

use new one, and sent over any coins.
daemon should work to make transfer


i downloaded the new one, and started working on windows.
Same as now can be downloaded.

Weird thing is that the date of executable is still the same,
but like SNOW mentioned, he forgot to upload it...

As soon as I use the old wallet to try to send coins it just crashes before I can do the send ....

[platti]

how many coins you have in the wallet?
you can send me your wallet, and i can try to fix it, and send you the coins to your new wallet-address

[mosmus]

Hi Marty,

You may want to try to dump your private keys with your old wallet by using the debug console under "Help":

Code:

dumpprivkey <your snowcoin address>

This will give you your private key. Then on a new wallet, you can run:

Code:

importprivkey <snowcoin private key from dumpprivkey>

You'll have to do that for each of your snowcoin addresses.

[platti]

that would not work, if he cannot open wallet

[mosmus]

that would not work, if he cannot open wallet

I understood he could open it, just not send from it. Regardless, I'm not certain my suggestion will work but I have used that in the snowcoin linux client with success.

[fire6113]

Right I have downloaded the new wallet.    I am on a win 8 x64 comp here now when I run it it loads get connections etc loads block and syncs no issues. And behaves as it should.....


BUT after that it plays up and may be the issue you are missing as I had the same happen here as the other user with the runtime errors...   

what I did was load the wallet sync it etc that went smooth...   close it reopen to test it was working it worked etc....

I then shut the wallet down and went about setting up a conf file to solo mine the coin....   

the config is as follows:

daemon=1
server=1
rpcuser=User
rpcpassword=Password
rpcallowip=127.0.0.1
rpcport=24352
addnode=50.56.121.30
addnode=cryptopool.it

saved that to the roaming/app area of the wallet...

then restarted the wallet it loaded fine no issues etc.....   But this is where the news gets bad lol

When I pointed the miner at the wallet it crashed and come up with the run time error  but I noticed the miner was mining etc so left it run to mine as the wallet was collect coins every time a block was found....  But on every new coin that came into the wallet a new run time error box came up. etc.   
Now after a while of mining I shut it down the rig and the wallet...   And reloaded the wallet and it crashed straight up with the runtime error...   So gave the computer a reboot and restarted the wallet no errors on the restart of the wallet and it behaved as it should....   But as soon as I kicked the mining rig back in again the runtime error appeared again.

Atm it appears the wallet is not liking been used as a server to mine off hence the pools also having the issue as I was with the solo mine there something in the coding play up I looked at the debug log could not find anything in that that stood out and it did not log the wallet error....   And I was unable to run the debug on the wallet it self due to the runtime error.   

It appears without knowing to much on coding it may be the way it handles the incoming connection that the issue as it played up on the start of the miner and the incoming block rewards with a error message each time...


I hope this essay may help you to debug the problem with the wallet as I want to see this coin get up as it is a another SHA which there are not many of...

Cheers

Fire6113

[sn0w]

"moneysupply" : 65660000.00000000,

there are more than 65 million coins in circulation?

thats quite possible with this low diff


but cant find any documentation on this , SNOW ?

Yeah, possible.

I did a clean install on a clean machine and all worked ok. Then I copied my old wallet.dat over and the problem started again. Swapped back to the new clean wallet.dat and problems continued.

Looks like its an issue with the wallet file.

You should try to extract private key from wallet.dat. I've updated BerkeleyDB, so maybe this is the problem.

[atta2k15]

[2014-01-09 10:05:03] Found block for pool 0!
 [2014-01-09 10:05:04] Network difficulty changed to 2.06k (14.79Gh/s)