[ANN][SBC] From Death Comes Life – The Rebirth of StableCoin - URGENT UPDATE

[educatedwarrior]

Judging from artos' reply and cobra's description of the two branches, if your pool is showing a difficulty of 5.255, it's on the correct branch.

Does that mean http://sbc.cryptoculture.net/index.php is on the wrong branch? Am I mining for no reason?

We updated to the 1.4 hours ago.  http://sbc.cryptoculture.net should be on the correct branch.   For some reason deposits are not working.  

The pool was updated to 1.4 and I downloaded the 1.4 client for my wallet - I 'm personally having issues with deposits.

I'm double checking right now.

[1714220191]

1714220191

[1714220191]

1714220191

[1714220191]

1714220191

[1714220191]

1714220191

[educatedwarrior]

Artos I have some serious issues at Cryptoculture Pool where users are not getting payouts and I think it has to do with a possible mismatch between Linux and Windows StableCoin Clients

I recently upgraded to 1.4 on my pool which uses Ubuntu.   I also downloaded the Windows client.  It appears the Linux and Windows clients are on different forks even though they are supposed to be the same 1.4 version... they are mining at different blockchain heights, also notice the difficulties are not the same.

When I do getinfo on the Ubuntu Server I get this
{
    "version" : 1040000,
    "protocolversion" : 1040000,
    "walletversion" : 60000,

    "blocks" : 314360,
    "connections" : 0,
    "proxy" : "",
    "difficulty" : 3.66631454,
    "testnet" : false,
    "keypoololdest" : 1387902646,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00010000,
    "errors" : ""
}

Windows 1.4 Client I get this


{
"version" : 1040000,
"protocolversion" : 1040000,
"walletversion" : 60000,

"blocks" : 313979,
"connections" : 16,
"proxy" : "",
"difficulty" : 2.16682822,
"testnet" : false,
"keypoololdest" : 1385871005,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00010000,
"errors" : ""
}

[MinermanNC]

Artos I have some serious issues at Cryptoculture Pool where users are not getting payouts and I think it has to do with a possible mismatch between Linux and Windows StableCoin Clients

I recently upgraded to 1.4 on my pool which uses Ubuntu.   I also downloaded the Windows client.  It appears the Linux and Windows clients are on different forks even though they are supposed to be the same 1.4 version... they are mining at different blockchain heights, also notice the difficulties are not the same.

When I do getinfo on the Ubuntu Server I get this
{
    "version" : 1040000,
    "protocolversion" : 1040000,
    "walletversion" : 60000,

    "blocks" : 314360,
    "connections" : 0,
    "proxy" : "",
    "difficulty" : 3.66631454,
    "testnet" : false,
    "keypoololdest" : 1387902646,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00010000,
    "errors" : ""
}

Windows 1.4 Client I get this


{
"version" : 1040000,
"protocolversion" : 1040000,
"walletversion" : 60000,

"blocks" : 313979,
"connections" : 16,
"proxy" : "",
"difficulty" : 2.16682822,
"testnet" : false,
"keypoololdest" : 1385871005,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00010000,
"errors" : ""
}

Miner is still hashing and shares accepted, so are we on the blockchain or a fork right now? PS: Luv this pool please correct issues!
Merry Christmas!

[Sheldor333]

Don't know if this will help but I just restarted my miner and everything was fine after that. Shares are accepted and I get what I mine. Try paying out some small amount to be sure it works, that is the best way to test it I think.

[MinermanNC]

Don't know if this will help but I just restarted my miner and everything was fine after that. Shares are accepted and I get what I mine. Try paying out some small amount to be sure it works, that is the best way to test it I think.

Seems credit is building in the unconfirmed but not confirming?...I never have this many unconfirms and 0 confirms. also, looks like about 600 coins have not credited to my cryptsy account,,, the ones shown in the transactions with no blocks or showing n/a ....  not good last payout was at 14:00 or 2pm today.... into my cryptsy account.

[Hazard]

Artos I have some serious issues at Cryptoculture Pool where users are not getting payouts and I think it has to do with a possible mismatch between Linux and Windows StableCoin Clients

I recently upgraded to 1.4 on my pool which uses Ubuntu.   I also downloaded the Windows client.  It appears the Linux and Windows clients are on different forks even though they are supposed to be the same 1.4 version... they are mining at different blockchain heights, also notice the difficulties are not the same.

When I do getinfo on the Ubuntu Server I get this
{
    "version" : 1040000,
    "protocolversion" : 1040000,
    "walletversion" : 60000,

    "blocks" : 314360,
    "connections" : 0,
    "proxy" : "",
    "difficulty" : 3.66631454,
    "testnet" : false,
    "keypoololdest" : 1387902646,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00010000,
    "errors" : ""
}

Windows 1.4 Client I get this


{
"version" : 1040000,
"protocolversion" : 1040000,
"walletversion" : 60000,

"blocks" : 313979,
"connections" : 16,
"proxy" : "",
"difficulty" : 2.16682822,
"testnet" : false,
"keypoololdest" : 1385871005,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00010000,
"errors" : ""
}

Delete the block chain and redownload it. The chain listed on http://sbc.blockexplorer.io/chain/Stablecoin is the correct one.

[educatedwarrior]

Message from Cryptocult Pools - http://sbc.cryptoculture.net

Fellow miners, I learned a hard lesson tonight. Our late update to version 1.4 really screwed us up. I am very dedicated to providing the best service to my customers, so I am very sorry and I understand you disappointment as a fellow miner.

The late update to 1.4 caused the following issues. 1. Caused our pool to get corrupted. Therefore we had to create a new pool from scratch. 2. Many users received confirmed transactions for blocks that exists on the wrong blockchain - therefore were invalid. These invalid transactions corrupted the metadata of the pool and rendered it in-operational.

I hope everyone had autopayout enabled and got all of their valid StableCoins out of the pool.

The new pool is up, and you will have to recreate your login id.

This issue will NEVER HAPPEN AGAIN!!! I hope you will continue to support us.

[educatedwarrior]

Artos I have some serious issues at Cryptoculture Pool where users are not getting payouts and I think it has to do with a possible mismatch between Linux and Windows StableCoin Clients

I recently upgraded to 1.4 on my pool which uses Ubuntu.   I also downloaded the Windows client.  It appears the Linux and Windows clients are on different forks even though they are supposed to be the same 1.4 version... they are mining at different blockchain heights, also notice the difficulties are not the same.

When I do getinfo on the Ubuntu Server I get this
{
    "version" : 1040000,
    "protocolversion" : 1040000,
    "walletversion" : 60000,

    "blocks" : 314360,
    "connections" : 0,
    "proxy" : "",
    "difficulty" : 3.66631454,
    "testnet" : false,
    "keypoololdest" : 1387902646,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00010000,
    "errors" : ""
}

Windows 1.4 Client I get this


{
"version" : 1040000,
"protocolversion" : 1040000,
"walletversion" : 60000,

"blocks" : 313979,
"connections" : 16,
"proxy" : "",
"difficulty" : 2.16682822,
"testnet" : false,
"keypoololdest" : 1385871005,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00010000,
"errors" : ""
}

Delete the block chain and redownload it. The chain listed on http://sbc.blockexplorer.io/chain/Stablecoin is the correct one.

Hazard, thank you for the suggestion.  I do have a snapshot of the old pool and if I can fix it I will restore it.  In the meantime, I set up SBC CryptoPool 2.0 for miners to use.

[thimo]

Message from Cryptocult Pools - http://sbc.cryptoculture.net

Fellow miners, I learned a hard lesson tonight. Our late update to version 1.4 really screwed us up. I am very dedicated to providing the best service to my customers, so I am very sorry and I understand you disappointment as a fellow miner.

The late update to 1.4 caused the following issues. 1. Caused our pool to get corrupted. Therefore we had to create a new pool from scratch. 2. Many users received confirmed transactions for blocks that exists on the wrong blockchain - therefore were invalid. These invalid transactions corrupted the metadata of the pool and rendered it in-operational.

I hope everyone had autopayout enabled and got all of their valid StableCoins out of the pool.

The new pool is up, and you will have to recreate your login id.

This issue will NEVER HAPPEN AGAIN!!! I hope you will continue to support us.

what in the hell, i'm getting double my hashrate. What was in that update? GPU cocaine?

[invisibel]

Just FYI, FedoraCoin adapted SBC's 1.4 difficulty algo for itself but it turns out the difficulty only adjusts up, not down, eg. we had 1gH/s when FedoraCoin started and the difficulty jumped to 38+, but when people left and the hashrate went down to 400mH/s the difficulty didn't change, and it hasn't changed since, so we had to go back to DogeCoin's difficulty algo for now

[sockf]

Greetings, I am getting an error with the new version of the wallet (1.4.0.0-g3aaa7ba-beta). When it tries to update, it says:

EXCEPTION:11DbException
Db::get: Not enough space
<path to wallet exe> in ProcessMessages()

There is over 18gigs available on that SSD, shouldn't be an issue there. Anyone know what is going on here?

[Sheldor333]

Just FYI, FedoraCoin adapted SBC's 1.4 difficulty algo for itself but it turns out the difficulty only adjusts up, not down, eg. we had 1gH/s when FedoraCoin started and the difficulty jumped to 38+, but when people left and the hashrate went down to 400mH/s the difficulty didn't change, and it hasn't changed since, so we had to go back to DogeCoin's difficulty algo for now

Doesn't mean that it is same with SBC. Since that would be a problem. I also think there was a larger hype at the begining as it is with every coin but it stabilize after a while. If such an issue exists with StableCoin hope it will get fixed.

[inzan1ty]

So, is SBC dead now after the initial hype or is it coming back in 2014?

[CrytoEnthusiast]

I definitely think it's going to rise. Artos is a dedicated developer, he's just taking a small holiday break.

[invisibel]

Just FYI, FedoraCoin adapted SBC's 1.4 difficulty algo for itself but it turns out the difficulty only adjusts up, not down, eg. we had 1gH/s when FedoraCoin started and the difficulty jumped to 38+, but when people left and the hashrate went down to 400mH/s the difficulty didn't change, and it hasn't changed since, so we had to go back to DogeCoin's difficulty algo for now

Doesn't mean that it is same with SBC. Since that would be a problem. I also think there was a larger hype at the begining as it is with every coin but it stabilize after a while. If such an issue exists with StableCoin hope it will get fixed.

It probably does, looking at the difficulty for SBC it doesn't seem to have dropped once since their new algo came in.

I think I've figured out why this is, in the new algo (and the one FedoraCoin adopted up until block 2500, for any fedora fans reading) he does

Code:

nActualTimespanMax = nTargetTimespan * (112/100); //12% down
nActualTimespanMin = nTargetTimespan * (100/111); //10% up

Where nActualTimespanMax/nActualTimespanMin and nTargetTimespan are all int64's, and from what I remembered int64's couldn't do floating point arithmetic directly without something bad happening

So I wrote some simple code to test it (long long is the VC++ name for int64):

Code:

	long long nTargetTimespan = 600;
	long long nActualTimespanMax = nTargetTimespan * (112 / 100); //12% down
	long long nActualTimespanMin = nTargetTimespan * (100 / 111); //10% up

	float expectedMax = (float)nTargetTimespan * (float)(112.f / 100.f);
	float expectedMin = (float)nTargetTimespan * (float)(100.f / 111.f);

	printf("ActualTimespanMax: %lld, ActualTimespanMin: %lld, expectedMax: %g, expectedMin: %g", nActualTimespanMax, nActualTimespanMin, expectedMax, expectedMin);

Which output:

Code:

ActualTimespanMax: 600, ActualTimespanMin: 0, expectedMax: 672, expectedMin: 540.541

So yeah, something is definitely wrong, he needs to fix this asap otherwise the difficulty will probably stick for SBC miners too, wish I found this out before I switched back to DogeCoin's algo, I don't think the FedoraCoin miners would like another hard fork update so soon...

[Maxon]

SO if we didnt have auto payout enabled we just lost all of our coins???

This really sux,,,


I lost around 40 coins, not much but it is to me....








sRFFQv5H8cLgDcfkYD31dd7DsFJAPrnDJe

[cobrabyte]

It's funny, as I was putting the code together for the restructuring of the difficulty algorithm patch, I noticed the same thing. I thought it was odd to see an integer type representing floating point data. However, I see the int64 datatype used all over the Bitcoin codebase for similar calculations. I wonder if the rest of the codebase is simply dropping precision and rounding up/down on those calculations.

In any case, it probably is just a simple fix to force floating point precision on those calculations. Hard to test this bit of code... I ran into that issue while writing the code that's currently sitting as a pull request.

Edit: updated my pull request with the change required to fix the loss-of-precision issue. Good find!

[udjin123]

Welcome to new pool.

SBC.FORKPOOL.COM!

Live support.
24/7 monitiring.
Good admin, does not bite.  
Stratum.
Prop payouts.

[FaT]

Message from Cryptocult Pools - http://sbc.cryptoculture.net

Fellow miners, I learned a hard lesson tonight. Our late update to version 1.4 really screwed us up. I am very dedicated to providing the best service to my customers, so I am very sorry and I understand you disappointment as a fellow miner.

The late update to 1.4 caused the following issues. 1. Caused our pool to get corrupted. Therefore we had to create a new pool from scratch. 2. Many users received confirmed transactions for blocks that exists on the wrong blockchain - therefore were invalid. These invalid transactions corrupted the metadata of the pool and rendered it in-operational.

I hope everyone had autopayout enabled and got all of their valid StableCoins out of the pool.

The new pool is up, and you will have to recreate your login id.

This issue will NEVER HAPPEN AGAIN!!! I hope you will continue to support us.

Remove pool fee? Lost a lot of shares

[Catswold]

Difficulty's now at 7.579!!!!  Really? 

This is beginning to look like one giant clusterf***