[ANN][1000 SYNC] Proof of Stake now run by BLOCKCHAIN DEVELOPMENT COMPANY

[1fixxer]

Can someone help me resolve the problem? Restared my pc and got this http://puu.sh/aM6md/3e8069f4ee.png http://puu.sh/aM6sm/ba20667c94.png

This happens when the local copy of the block chain is damaged.
First find where your wallet.dat is stored and make a copy of it in a safe place (backup).
Then delete everything in that directory and the subdirectories, except the wallet.dat and the Sync.conf
Now restart your Qt wallet, it should start normally and tell that it is out of sync, it will then download the block chain from the start
to rebuild its database that was corrupted. Once it has re-sync'ed you are back in business.
Success!

But now it says '0 active connections to network' and my balance is at 0. What to do?

[1714929952]

1714929952

[1fixxer]

Also there wasn't sync.conf in the directory

[youngwebs]

Also there wasn't sync.conf in the directory

you have to make to make the Sync.conf yourself *see start post*. once the wallet syncs, your balance will return!

[1fixxer]

Made .conf, redownloaded wallet, but still 0 conections... dont understand wtf happend

[Cor2]

Made .conf, redownloaded wallet, but still 0 conections... dont understand wtf happend

If you are using Windows then make sure that the file name extension is not hidden, because it is easy for the file name to be
sync.conf.txt but you do not see the txt extension if that part is hidden (this is Windows default....)
If you are not using Windows then make sure that the file name starts with a capital 'S': Sync.conf
because that is a different name (in for example Linux) than sync.conf (with small caps) so it won't find that name....
Without the sync configuration (which has the addresses of peer nodes) the sync wallet may not synchonise,
although you can be lucky - I have managed to get a wallet to sync, but this was *after* another wallet on the same network
was already running, so for a long time the second wallet only showed 1 connection...
You should get many connections pretty fast if the wallet reads the Sync.conf file.
Success!

BTW, no need to re-download the Qt wallet, just stop the program, make sure the Sync.conf is correct and restart the Qt wallet.

[Biomech]

Made .conf, redownloaded wallet, but still 0 conections... dont understand wtf happend

Make sure your firewall is allowing the port. If it's Windows or Linux, and you're still having trouble, I can probably help. But usually connections are a port problem if you have the right addnodes in your .conf file.

Also, make sure the .conf file is in the data directory, not the directory where your .exe file is.  (/home/user/.Sync for linux, \users\username\appdata\roaming\Sync for Windows)

Unfortunately I know jack shit about Mac. Hope it helps.

EDIT: Ninja'd again See the above post as well, good points.

[1fixxer]

Cor2, Biomech, yeah, I did all of that and checked everything fucking 10 times! And no result still. I installed fresh windows, runned the wallet, it worked fine for 1 day, then I reseted my PC and the wallet crashed. Is there anything else can I do, like reinstall windows or runtime C++ library or smth...?

[Biomech]

Cor2, Biomech, yeah, I did all of that and checked everything fucking 10 times! And no result still. I installed fresh windows, runned the wallet, it worked fine for 1 day, then I reseted my PC and the wallet crashed. Is there anything else can I do, like reinstall windows or runtime C++ library or smth...?

I'm quite puzzled.

I've had no problems with either the windows or the linux wallet since Nite got involved.

PM me, I'll see if I can help.

[1fixxer]

Big thanks to Biomech for help! He gave me valid nodes, since ones in OP post didn't worked for me:

addnode=60.242.23.7:24241
addnode=220.245.200.69:24241

[youngwebs]

Big thanks to Biomech for help! He gave me valid nodes, since ones in OP post didn't worked for me:

addnode=60.242.23.7:24241
addnode=220.245.200.69:24241

Maybe update the OP, with some more permantent nodes.

[lifebennder]

Is there anywhere where you could show how a example config could look like, whats the syntax and the possible options you can put in it?

and to load the config properties do you have to always have the option -conf=<configfile> when launching?

and the peers.dat file holds the know peers so far. So it checks that and establishes connections right? So the peers list should grow right, making connecting faster eventually? correct me if i am wrong.

Whats a sensible amount of connections to have,because mine is quite low? (more nodes would be appreciated)

Thanks

[mikeyfinn]

Is there anywhere where you could show how a example config could look like, whats the syntax and the possible options you can put in it?

and to load the config properties do you have to always have the option -conf=<configfile> when launching?

and the peers.dat file holds the know peers so far. So it checks that and establishes connections right? So the peers list should grow right, making connecting faster eventually? correct me if i am wrong.

Whats a sensible amount of connections to have,because mine is quite low? (more nodes would be appreciated)

Thanks

The example conf file in the OP will work great. Only change I use is under the line "rpcport=24240" i add "port=24241". Name the file Sync.conf (it must be Sync.conf, not sync.conf or it'll only work in windows, not linux or mac) and put Sync.conf in the same folder as the wallet and pers.dat, etc.

[polanskiman]

Not sure if this has been discussed before or what but my Mac Wallet needs to be force quite nearly every time I keep the wallet open for a few hours. Usually I see the spinning beach ball of death and nothing but a force quite solves the problem.

[MystPhysX]

Not sure if this has been discussed before or what but my Mac Wallet needs to be force quite nearly every time I keep the wallet open for a few hours. Usually I see the spinning beach ball of death and nothing but a force quite solves the problem.

Can you PM me the Qt and total ram usage when it happens? The code is vanilla so there should be no issues in theory.

[polanskiman]

Not sure if this has been discussed before or what but my Mac Wallet needs to be force quite nearly every time I keep the wallet open for a few hours. Usually I see the spinning beach ball of death and nothing but a force quite solves the problem.

Can you PM me the Qt and total ram usage when it happens? The code is vanilla so there should be no issues in theory.

Sure will do so when it happens again. It actually just happened now but I read your message after I forced quite.

[tc61]

looking at the x11 multipool...it looks like its not worth mining there.. the payout are every 2-3 day and it not much for the hashrate...am i missing something?..want to get some more sync but im not calculating something right

[ChekaZ]

Any suggestions for getting connections? I've set up the config and portforwarded the p2port, still no connections.

[Cor2]

Is there anywhere where you could show how a example config could look like, whats the syntax and the possible options you can put in it?

and to load the config properties do you have to always have the option -conf=<configfile> when launching?

and the peers.dat file holds the know peers so far. So it checks that and establishes connections right? So the peers list should grow right, making connecting faster eventually? correct me if i am wrong.

Whats a sensible amount of connections to have,because mine is quite low? (more nodes would be appreciated)

Thanks

I think the working config file is the one in the OP, with the addition of the two better IP addresses in the recent post.
Once your wallet connects to *one* other wallet, it will request the peer list from that wallet and then try to connect to those peers itself, quickly building a large number of reachable IP addresses with Sync wallets.
If your port configuration does not allow incoming connections, then the number of peers tend to stay around a dozen, connections that your wallet makes *to* others. If you allow incoming connections, you can have many dozens connections from your wallet. Indeed the found IP addresses are stored in the peers.dat file. You can dump a list of some of the recent IP addresses with a console command.

The config file should load automatically if you store it in the default place (same directory as wallet.dat) and give it the default name:
Sync.conf

You can quickly see the status of your wallet connections, staking and block nr by hovering your mouse over the symbols in the bottom right corner of the wallet (while the wallet is the active application). You can also see more info by going to Help -> Console -> Information
Your wallet will work with even 1 connection, but I typically see around a dozen in my wallet.

[InfN8Void]

looking at the x11 multipool...it looks like its not worth mining there.. the payout are every 2-3 day and it not much for the hashrate...am i missing something?..want to get some more sync but im not calculating something right

There is nothing profitable to mine right now.  Crypto is pretty dead.  All multipool prof is down and the only x11 they are mining is uro.  If you want to mine x11 mine @ waffle then buy your own Sync. Waffle i think still pays out whenever you hit .005 btc so it depends on how much hash you have how often you get payout.  i used to mine there and got paid almost daily.

[youngwebs]

looking at the x11 multipool...it looks like its not worth mining there.. the payout are every 2-3 day and it not much for the hashrate...am i missing something?..want to get some more sync but im not calculating something right

There is nothing profitable to mine right now.  Crypto is pretty dead.  All multipool prof is down and the only x11 they are mining is uro.  If you want to mine x11 mine @ waffle then buy your own Sync. Waffle i think still pays out whenever you hit .005 btc so it depends on how much hash you have how often you get payout.  i used to mine there and got paid almost daily.

X11 mining is just not very profitable, most x11 coins are POS these days and POW coins are sucked dry by the multipools (including the SYNC multipool).
We support x11 because there are enough miners who want to use low energy/heat mining on their systems that run anyhow.

With the current prices of SYNC, it will take a lot of time however before you get some serious SYNC.

If you expect SYNC to rise (we DO) you could still mine at the multipool with the idea that the SYNC you do get, will increase conserably, meaning that in e.g. about 4 weeks from now the mining is suddenly profitable for you.

If you are in for the short run, it is not profitable...