Well I woke up this morning and rig 1 was down.. Funny it, shouldn't have overheated... well lets boot it back up.. hit the switch.. I've been playing with these things since 82' I've seen the "blue flash" of death a few times.. I've never seen the "acrid smoke while spitting bright orange sparks" of death before  Wow...I feel so left out.... My second card just rolled over and died. No Sparks. No Smoke. Not even a fan squeal. Just suddenly.....nothing. |
|
|
|
|
Damn...suddenly got crazy quiet here......
Should I be worried?
|
|
|
|
Although i only get 2 connections to the network blockchain loaded fast and so did sending and receiving coins. Great work! Sounds are a great idea but now i have to parse my old soundlib for some on topic sounds  addnode=74.122.234.52:9560 addnode=188.126.8.14:9560 addnode=67.191.160.195:9560 addnode=118.250.240.72:9560 This should give you a minimum of 3. Also, make sure you don't have irc=0. |
|
|
|
The NEW Client!!!
Looking for beta testers! This addresses the desync problem as a 'phase 1' solution, contains the retargeting code, and has some of the 'extra' features we've been buzzing about. The overall plan is is very aggressive, I want to have the official client out on Tuesday. In order to accomplish this we need your help. Plan on replacing your client as soon as you can when it becomes available. Pool Ops!! need I say more! Redefining our retargeting involves a "hard-fork". Here's the plan in a nutshell:This is the initial beta( 0.6.4.1 - RC1, available below). It will no longer talk to 0.6.3, but will talk to 0.6.3.1. If it proves stable it will be released as ( 0.6.4.1 ) with one change, that it will no longer talk to 0.6.3.1. At that point we will have the network prepped so that retargeting can change. This release ( 0.6.4.1 ) is a band-aid...but a very strong one. It addresses the desync problem, and the 30 minute retarget code is in place. Client 0.6.3 and 0.6.3.1 will no longer be accepted on the network, which means that the next release ( probably 0.6.5.1 ) will have a better solution for the desync, and also have some of the other features we have been talking about. By the time 0.6.5.1 is released we should have the desync completely fixed. 'RC1' is available and we need beta testers!.I've put the new client in my own github repo, with a widows version in my dropbox. This has already been tested extensively. **back up your wallet first**Source/Linux: https://github.com/lavajumper/sexcoinWindows Binary: https://www.dropbox.com/s/i0tesee13rhqg3f/Sexcoin-0.6.4.1-win32-RC1.zip If this proves to be stable, and no serious issues occur, then I will push this into the main repository, and start building binaries. |
|
|
|
Sexcoin is now traded on coinex.pw too  !!!!! No fanfare on that one, but this is GREAT! |
|
|
|
|
The Lavapit is back up.
It was down for awhile. The guys at the datacenter made some changes to their routers and snarfed some of my firewall entries.
Its back up now and ready for business.
Dammit. Sorry about that guys. Nothings been lost. No attack. Stupid human error.
|
|
|
|
PLEASE, if you are running client 0.6.3,
PLEASE upgrade to 0.6.3.1.
The next release will probably refuse to talk to 0.6.3.
PLEASE!
Links for the client are on the OP.
|
|
|
|
|
Some other good news:
I've got a RHEL 6.0 build which will be available in the next release. Should work on CentOS also.
|
|
|
|
|
Here are some stable nodes. I've set up at least two so we will always have some available. Over the next month I'm going to hunt down more servers and spread em open....er.... spread the daemons....er....dammit.
addnode=74.122.234.52:9560
addnode=188.126.8.14:9560
addnode=67.191.160.195:9560
addnode=118.250.240.72:9560
If anyone puts up working nodes, please let us know so we can list them, also let us know if they are intermittent, or 24/7
We would like as many as we can get to help keep the coin stable.
One other thing. PLEASE, if you are running client 0.6.3, PLEASE upgrade to 0.6.3.1. The next release will probably refuse to talk to 0.6.3.
PLEASE.
|
|
|
|
Welcome to SXC we are all about team work!
do you have content for the forum yet ? its been up over a week and only a couple of users You are absolutely correct Zack. I would like to encourage people to use http://sexcoinforum.org . This thread will still be here, but zack is graciously allowing some latitude that bitcointalk.org cannot. Post your pools, Post your sites, Post your art, just please don't post your sister. |
|
|
|
Fantastic! You should definitely touch base with lyno. |
|
|
|
The windows client is dead...
Keeps loading infinitely, trying to load ~320640 blocks+
Eg, you can't mine with it, because it never appears to be synced. There is not that many blocks, so something it corrupted in the windows compiled version.
Was a nice coin while it lasted. Sad that it just died...
I'm no expert. But in the first post, there is rpcport=9561, imho port 9560 is for nodes only.
This is true. 9560 allows your client to connect to the block-chain. 9561 allows your miner to talk to your client. Please read the first post on this thread. Also this post from the old one: https://bitcointalk.org/index.php?topic=218158.msg2637857#msg2637857. If you are still having problems, try this: https://bitcointalk.org/index.php?topic=218158.msg2615324#msg2615324. As for mining: https://bitcointalk.org/index.php?topic=218158.msg2653865#msg2653865The de-sync issue is our TOP priority. We have a strategy, but the implementation requires a lot of attention to detail and is difficult to test, so it is taking longer than the first fix nomaxpi put out. Just thought I'd repost this for all the newcomers. I'm collecting a list of current nodes. |
|
|
|
Checked out the source. 2,000,000 coins premined in the first two blocks. if(nHeight < 3) //premine bounties
{
nSubsidy = 1000000 * COIN;
}
Obvious scamcoin is obvious. Yeah, we all are having to live with this unfortunate fact. Believe it or not, this coin has A SHITLOAD of history in the short time its been around. We do know that a lot of this premine WAS distributed as bounties for services. We also know that the holder of this premine hasn't been heard from since early June. This coin nearly died from lack of attention. A few of us were so sold on the potential we grabbed the dropped ball and started doing some real work on it. So here we are, premine from a possible scammer and all. Nothing we can do about that except work with what we have. |
|
|
|
why doesn't my client ever sync?
That's a well known issue that is being addressed. Your coins are safe, mining is safe. Take a read on the OP and also a lot of posts in here. |
|
|
|
P2Pool is back up.
Well, I'm not sure what made the p2pool lose its mind today, but I think I've got it back up and stable. I'll have time to scrutinize the logfiles tonight. More when I find out what the hell that was.
Ok I found the exact issue with the p2pool. |
|
|
|
|
P2Pool is back up.
Well, I'm not sure what made the p2pool lose its mind today, but I think I've got it back up and stable. I'll have time to scrutinize the logfiles tonight. More when I find out what the hell that was.
|
|
|
|
And just because I can never really let go: LAVAPIT IS IN OPEN BETA!
Yes...its out of alpha.
Yes...its out of closed beta.
So what's next! Open? NO!
LAVAPIT IS IN OPEN BETA! There's a t-shirt in here somewhere. So...No more invite tokens. Just sign up and start mining. Let me know if there are any problems. I'm going to post an official announcement this evening. Everyone that has signed up is now a permanent 'early-adapter'. Also, PM me here if you didn't use an email address when signing up, and now want to use one for down-worker notices. |
|
|
|
https://github.com/sexcoin-project/sexcoinlook at the version.h file you'll see the version bump. I appreciate you considering the coin. But please be more thorough in your research before posting misinformation about a coin. P2pool was down for about an hour today. Its up now and you can check the history. I have a job that has been sampling the network hashrate since I put up the blockexplorer ( http://sexcoin.lavajumper.com:9950 ) I'll be happy to send it to you. The source has been available to any able to do a 'git clone blah', If you simply run a search for sexcoin at the top of githubs pages it will come up. You seem like a person that can appreciate a snafu here or there. The current dev team picked up a dropped ball with sexcoin, and it has come a long way. Perhaps we could help each other instead of trying to poke holes where they don't exist.
|
|
|
|
|
Show Posts
