Topic: [NSFW] Official Sexcoin Thread - New MANDATORY upgrade: KGW Timewarp attack FIX - page 42. (Read 307641 times)

Happy New Year guys....

I solo mined multiple coins with 9 to ~14 MH/s and can confirm that 1% of the network hashrate is the bare minimum to be "ok". 2% is much better, except if the block time is too long (>2mn).

There's no real gain to solo mine. If you don't have a very low ping you can have a good amount of stales or orphans easily, especially on short block time coins.

I often prefer to find a pool that made public it's last n blocks found, and look if there's no "bug" in the stats and if on the last 100+ blocks, real shares are near 100% expected shares.
If I have a good ping on it, if it has more than 5% the network hashrate, and if it does not have any bad history with community for other coins, I set it up as my main pool, and try to find at least 1 or 2 others pools as failover.

If cgminer finds a block, the wallet and cgminer have found a 'working solution', however, this doesn't 100% insure that the block will be accepted by the block chain. If another miner has found a 'working solution' at the same time, whichever miner can propagate that information to the network fastest gets the block. The winner will get the reward, and the other miner gets an 'orphan'. This is usually registered in your wallet as a mined block with a '?' beside it for longer than 2 blocks.

This is one of the strongest arguments for mining in a pool unless you have both a competitive hashrate and a good solid connection to the network.

To answer your other question, it is possible for someone to 'interfere' with your wallet under a narrow set of circumstances if your wallet is not encrypted or encrypted with a weak password AND someone has obtained your private key. If this happens your wallet is compromised and whoever has the private key can spend your coins at will.

Always keep in mind that mining calculations are NOTHING but an estimate. It is possible to have a run of bad luck, especially when the network hash rate jumps, and fall in way below the estimated reward. This is exactly why I don't solo mine anymore. I figure solo mining would require somewhere on the order of 1% of the total network hashrate to negate the 'bad luck' risk. Some people have this kind of hashpower, I don't. Add into that the flash mining and it really is a strong case for pool mining. I mined litecoin for months in pools and solo and in my entire mining career I have found a grand total of one block for one pool, never one solo. My calculations predict that I would find one block every 9.5 days ( back when difficulty was under 300). So, it seems to me (and this is an uncalculated, unproven opinion) that there is a 'critical hashrate level' that one must achieve in order to solo mine.

That being said, take a look through your debug.log file to investigate what is happening to these blocks. My guess is that they are being orphaned, but its worth looking into.

[EDIT] All someone needs is your private key, which can be obtained if you don't have your wallet encrypted, or encrypted with a weak password. Encrypting the wallet protects your private key.

HAPPY NEW YEAR !!!

Happy New Year - and a prosperous 2014 for SXC

I have a question to the experts
I have twice discovered - solo mining - that I have found a block - cgminer - accepted and so forth - and then the wallet pops up that little incoming message - but when I open the wallet nothing is incoming - not even after a while..!?
Is it possible that someone somehow can interfere with your wallet w/o you knowing it - and then redirect the incoming to an outside wallet..?
if so - how can that happen?

when I have encountered this I have deleted the whole wallet dir except the wallet and conf - restarted the qt and waited for the whole chain to be downloaded.
 but I continue to suspect something wrong because I am still losing a lot of coins which I normally mine over one day - not even just a bit less due to increased diff - but a lot less - almost to a standstill..

DO IT

the cam site should be the easy part.

If any1 can make a cam site i could get some girls and we could go 50/50 on it

Something is up with your installation.
It sounds like you _may_ have corruption in your blockchain:

• copy 'wallet.dat' and sexcoin.conf to a safe place
• delete the old installation ( not your wallet backup!!! )
• install new
• start the new client and see if it syncs, if it does.....
• close the client
• copy your old wallet.dat ( the one with your coins) to the new installation, overwriting the wallet.dat that the new install created
• restart client

Other things:
-what block are you stuck at?
-is your wallet encrypted?
-have you run an anti-virus to make sure its not something like that
-have you checked to see if maybe your firewall decided it didn't like crypto-traffic?


If you want to copy your 'debug.log' file to a drop-box or something, I'll be happy to take a look.

oh I actually meant the whole conf file - or do you only have those addnodes in it..?

I found this info earlier - never used it - but might be worth a try
# If you have issues try this:
 # -delete peers.dat
 # -use, instead of addnode:
    # connect=74.122.234.52:9560
    # connect=81.166.156.164:9560
    # connect=67.191.160.195:9560
..obviously you remove the # sign for the address you want to try..
and make sure that port is open on your modem/router or whatever you use..

and remember that connect means that you only get info from that ip - addnodes are in addition to all other connections the client finds itself..

of further info I can tell you that I sometimes delete or # all info in a wallet conf file - save it - close the wallet and open it again - that may or may not work better sometimes..

addnode=46.39.246.24:9560
addnode=68.52.140.186:9560
addnode=84.253.217.35:9560
addnode=67.191.160.195:9560
addnode=223.27.19.38:9560
addnode=74.122.234.52
addnode=23.94.28.23:9560


It's worked fine with both P2P and solo mining in the past, without changing the config or client. So I don't believe it's the .conf that's the problem.

I'm not trying to question your knowledge, but
- is your sexcoin.conf spelled correct?
- is it in the correct directory?

maybe copy/paste here your contents of the sexcoin.conf file..

Haven't been able to sync the wallet for days.
I've got active connections and I've added the nodes from the OP.

Coins are not lost. Keep client open it will rebroadcast transaction till it goes through.

Status: 0/unconfirmed
Date: 12/30/2013 20:37
To: SC7Un3ssgd7rJKiwoiaajNaAfVYdJ21k1h
Debit: -288.00 SXC
Net amount: -288.00 SXC
Transaction ID: e3422419eceee2a21cc2546f9b2adcd1b79f944f2f36bbebbbd2fea5bc86f906

2 hours, no confirm....lost coins

yay

Great news that it's mentioned in the Washington Post, meanwhile.................newbie and member of the public trying for two days

to get help to get his wallet back in sync, no luck there, must be xmas, or who cares about that he's not a miner,

come on guys as I have stated not everyone is a rocket scientist geek into code,

It would be most appreciated if someone could explain in simple laymans language the procedure for

getting my wallet back online PLEASE, PRETTY PLEASE 

It was ok until December 13 2013 now all I get is 1 or 2 connections then 0 after half hour,

I have tried to download updated version , no good , unless I have messed up something, tried posting on forums for help no luck there,

Just noticed on Coinmarket cap slight dip in the price, I wonder why?

Sorry to be a pain in the arse but do remember their are millions of pains in the arse like me who might

like to adopt or invest in this coin.

Sorry to sound pissed off , but I am 

I do not own some super duper quad core computer, just a poxy vaio laptop, windows 7

Thanks any help would be appreciated 




   

N of M signature transactions for the win!

http://rehost.bitcoinhistory.net/sexcoin-init