November 06, 2024, 10:28:16 AM

Welcome, Guest

News: Latest Bitcoin Core release: 28.0 [Torrent]

Bitcoin Forum>Alternate cryptocurrencies>Announcements (Altcoins)

Pages:

«
43
44
45
46
47
48
49
50
51
52
»

Author

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

fendlestick

hero member

Activity: 546

Merit: 500

Quote from: rapidfire187 on December 21, 2013, 02:24:12 AM

windows qt is not working correctly.

How is it not working? Few more details would be useful, thanks!

rapidfire187

sr. member

Activity: 252

Merit: 250

!!!INCAKOIN!!!

windows qt is not working correctly.

mightcoin

member

Activity: 103

Merit: 10

Thanks for the reply. For the record, I am not accusing any pool operator for dishonesty.

As for making profit calculations, I monitor network difficulty (network hashrate) as well during my testing period. Suppose I test a pool for 3 hours; then, I see how the difficulty changes during those three hours and use a high value as a conservative estimate.

I understand that some altcoins are notoriously inefficient with varoius losses here and there, resulting in 60% yield. Despite this, I generally have not had much problem with LTC and SXC, except recently.

LittleDigger

sr. member

Activity: 462

Merit: 251

Quote from: mightcoin on December 20, 2013, 08:17:32 PM

I am not getting a good yield on thec0de pool. Anyone having a similar issue? My yield is below 80%, i.e. my payout is less than 80% of what I expect given my hashrate and network difficulty. Any help is greatly appreciated.

On the other hand, outhashed.com p2pool used to have good yield, but the pool frequently drops.

If you guys can suggest a pool that I can join, that would be great. Thanks.

I've sat on a florin pool, and noticed that the network hashrate was 20MH, yet the pool hashrate was 40MH.. with clients reporting wildly inaccurate hashrates, how can we expect that profitability calculations are correct ? Add to that fluctuations in the network hashrate itself.

As far as I'm aware, this problem has been ignored by other developers, and it is widespread within alt-coins. Lava has not ignored this, and is reasonably confident that it will be addressed in the new client release.

Gr33k is one of our oldest pool operators, and has acted honestly and honourably, but mcKenziemining is an experienced pool op I have used..

mightcoin

member

Activity: 103

Merit: 10

I am not getting a good yield on thec0de pool. Anyone having a similar issue? My yield is below 80%, i.e. my payout is less than 80% of what I expect given my hashrate and network difficulty. Any help is greatly appreciated.

On the other hand, outhashed.com p2pool used to have good yield, but the pool frequently drops.

If you guys can suggest a pool that I can join, that would be great. Thanks.

lavajumper

hero member

Activity: 873

Merit: 1035

Sexcoin Core Dev Team Member

Lavapit Notice:

If you don't have an email address listed, and don't write an email address in the support ticket, I really have no way of responding.

DigitalNexus

newbie

Activity: 7

Merit: 0

Quote from: irraz on December 20, 2013, 01:48:43 AM

Does the proposal is more RAM is to compile or run?

For compiling, you can run "free -m" to see how much memory you're using.

I had the same problem compiling and so did this guy https://bitcointalksearch.org/topic/solved-g-internal-compiler-error-killed-program-cc1plus-304389

lavajumper

hero member

Activity: 873

Merit: 1035

Sexcoin Core Dev Team Member

Quote from: irraz on December 20, 2013, 05:02:04 AM

Hello,

I was able to compile a new client and now it works ...
...still had not seen the precompiled version.

Thanks for all!

What was the issue with your compiles?

lavajumper

hero member

Activity: 873

Merit: 1035

Sexcoin Core Dev Team Member

If you are still having problems, try this in your sexcoin.conf file:

addnode=74.122.234.52:9560
addnode=67.191.160.195:9560
addnode=4.34.200.197:9560
addnode=59.167.201.127:9560
addnode=71.33.132.69:9560

irraz

newbie

Activity: 11

Merit: 0

Quote from: karudea on December 20, 2013, 06:09:57 AM

I have the wallet issue.
Can someone explain me how to fix it? I'm pretty much bad at fixing these kind of issues...

Please i need help (and i saw that the pool mined 3X500 sxc blocks... I want those coins !!!)

Hope that one kind soul will be able to help me..

Hi,

You can try this precompiled clients: http://lavapit.lavajumper.com/download.php

Regards

karudea

member

Activity: 106

Merit: 10

I have the wallet issue.
Can someone explain me how to fix it? I'm pretty much bad at fixing these kind of issues...

Please i need help (and i saw that the pool mined 3X500 sxc blocks... I want those coins !!!)

Hope that one kind soul will be able to help me..

irraz

newbie

Activity: 11

Merit: 0

Hello,

I was able to compile a new client and now it works ...
...still had not seen the precompiled version.

Thanks for all!

irraz

newbie

Activity: 11

Merit: 0

Still I have problems.
Chain block is not updated. Sad

Sad

I'm desperate!

irraz

newbie

Activity: 11

Merit: 0

Thank you guys!

It seems today is a fixed??

I orphaned the last 4 blocks, but now run seems ok ....

I will continue to review all this up.

Code:

/sexcoin# ./sexcoind getpeerinfo
[
{
"addr" : "23.94.28.23:9560",
"services" : "00000001",
"lastsend" : 1387521793,
"lastrecv" : 1387521793,
"conntime" : 1387521753,
"version" : 60011,
"subver" : "/Sexcoin:0.6.4.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 321326,
"banscore" : 0
}

{
"version" : 60401,
"protocolversion" : 60011,
"walletversion" : 60000,
"balance" : 2096.51971474,
"blocks" : 401784,
"connections" : 1,
"proxy" : "",
"difficulty" : 4.09126491,
"testnet" : false,
"keypoololdest" : 1386881233,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00010000,
"errors" : ""
}
]

Does the proposal is more RAM is to compile or run?

lavajumper

hero member

Activity: 873

Merit: 1035

Sexcoin Core Dev Team Member

Quote from: irraz on December 19, 2013, 06:17:29 PM

Hello,

I have sexcoin-qt-v0.6.4.1-RC1-beta.linux64.tar.gz
And my wallet is bloqued in Current Block 400537 and no confirmations received...

Code:

keypool reserve 54
keypool return 54
ThreadRPCServer method=getmininginfo
ThreadRPCServer method=getdifficulty
ThreadRPCServer method=getblockcount
ThreadRPCServer method=getblock
ThreadRPCServer method=gettransaction
ThreadRPCServer method=getblock
ThreadRPCServer method=gettransaction
ThreadRPCServer method=getblock
ThreadRPCServer method=gettransaction
connection timeout

/sexcoin# ./sexcoind getinfo
{
   "version" : 60401,
   "protocolversion" : 60011,
   "walletversion" : 60000,
   "balance" : 2096.51971474,
   "blocks" : 400537,
   "connections" : 1,
   "proxy" : "",
   "difficulty" : 4.70175179,
   "testnet" : false,
   "keypoololdest" : 1386881233,
   "keypoolsize" : 101,
   "paytxfee" : 0.00000000,
   "mininput" : 0.00010000,
   "errors" : ""
}

This is a bug?

I tried to compile new versión but error ocurred... :-(

g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.

Help me! please!

Could you run "getpeerinfo" and post the output?

DigitalNexus

newbie

Activity: 7

Merit: 0

@irraz

How much ram do you have? Try increasing your available ram to at least 1gb.

irraz

newbie

Activity: 11

Merit: 0

Hello,

I have sexcoin-qt-v0.6.4.1-RC1-beta.linux64.tar.gz
And my wallet is bloqued in Current Block 400537 and no confirmations received...

Code:

keypool reserve 54
keypool return 54
ThreadRPCServer method=getmininginfo
ThreadRPCServer method=getdifficulty
ThreadRPCServer method=getblockcount
ThreadRPCServer method=getblock
ThreadRPCServer method=gettransaction
ThreadRPCServer method=getblock
ThreadRPCServer method=gettransaction
ThreadRPCServer method=getblock
ThreadRPCServer method=gettransaction
connection timeout

/sexcoin# ./sexcoind getinfo
{
   "version" : 60401,
   "protocolversion" : 60011,
   "walletversion" : 60000,
   "balance" : 2096.51971474,
   "blocks" : 400537,
   "connections" : 1,
   "proxy" : "",
   "difficulty" : 4.70175179,
   "testnet" : false,
   "keypoololdest" : 1386881233,
   "keypoolsize" : 101,
   "paytxfee" : 0.00000000,
   "mininput" : 0.00010000,
   "errors" : ""
}

This is a bug?

I tried to compile new versión but error ocurred... :-(

g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.

Help me! please!

lavajumper

hero member

Activity: 873

Merit: 1035

Sexcoin Core Dev Team Member

:: Lavapit update ::

I've re-enabled getwork/pushpool protocol on the Lavapit for testing. It will be up unless I determine that it is causing something bad to happen.

After I can test this for a while, and things run ok, I will re-open registration.

lavajumper

hero member

Activity: 873

Merit: 1035

Sexcoin Core Dev Team Member

It should only effect the prebuilt windows binaries.

IF you are stuck at block 400000 or close to it, then you probably have the issue.

If you are experiencing it, and you are on another pre-built, please let me know.

If you built the client yourself, you can check the source code. The block of code that does a height-check should be commented out:

open main.cpp
check around line 2527

The "Sanity check" block of code.

I checked the source on github, and its commented out there.

wedge

full member

Activity: 187

Merit: 100

Quote from: lavajumper on December 19, 2013, 12:54:13 PM

If your client is stuck around block 400000, download the fixed client below!

In the zip file is a replacement sexcoin-qt.exe
Close your client, overwrite sexcoin-qt.exe with the one in the zip file.
Restart your client.

Nothing else is necessary.

Blockheight Fix Windows Client:

http://lavapit.lavajumper.com/dl/sexcoin-qt.blockheightFix.zip

https://www.dropbox.com/s/2snyqxgndv8my54/sexcoin-qt.blockheigtFix.zip

Does this only affect the windows client?

Pages:

«
43
44
45
46
47
48
49
50
51
52
»

Bitcoin Forum>Alternate cryptocurrencies>Announcements (Altcoins)

Jump to: