Topic: [ANN] [SFR] SaffronCoin | Latest Version - 1.4.2/2.6.2 | Mandatory Wallet Update - page 110. (Read 437833 times)

[20:38] Hi, The SaffronCoin wallet is still disabled
[20:38] I sent a mail to update to v1.3.4
[20:38] But didn't get any reply yet
[20:39] nothing i can do
[20:39] its waiting on richie
[20:40] Oh ok
[20:40] Is Richie not available?
[20:41] he's at blackhat
[20:42] so he's very busy I'm sure he'll get to it today
[20:42] Ok thanks

why nomp.cloudapp.net appear only half hash power ?
my rig have 6.1 Gh, but on pool only 2.44 Gh   

Good to know 

news bittrex?

Maybe my window 7 

But it working fine now

I've no crash with the linux multi tasking wallet, sync is ok with it  

Problem is Classic Verison is syncing good,
Multifeature wallet is crash during syncing,

So we can just sync block chain with Class Wallet then Use with Feature Wallet

That how I'm using now.

do you have any news from pool-coins admin?
I have messaged him 10 days ago here but he never replied.
I have SFR in his pool

Hi.

I found the solution with a colleague of an other forum .

The solution was  to delete all files except the wallet.dat .

Concerning the version , i prefered the classic one because i never tried the other one .

Yeah I want to buy more 

They may be on vacation 

More details please.

Out of curiosity, why do you prefer the Classic version?

The SFR hfr pool is a groestl pool .

Dev, for sfrpay I think you should add an email confirmation box, in case of

The correct chain is now the longest, and the one being mined by every major pool. There is no reason to keep the wallet suspended any longer on Bittrex. A few solo miners, and a Scrypt pool with only 3 users are still on the wrong chain. That smaller fork is now irrelevant and any transactions on it will not be confirmed by the network, so it is no longer a concern.

Algos in perfect health:
Groestl, Scrypt and Blake

Algos nearly back to normal:
Sha

Algos still in need of more miners:
X11

The great thing about a multi-algo coin, is that it is functioning perfectly well even with only 3/5 algos finding blocks as expected. This is the resilience of a multi-algo coin, and what makes it so great, we don't just rely on one type of miner, but have the back up of 4 others. X11 and Sha are still finding blocks, just infrequently. The difficulty will soon adjust back down.

Again, props to the dev for sorting out this mess so quickly and professionally.

I managed to solo mine 2 Blake blocks while the Blake pool was down, which was pretty nice considering I just had just one GPU going at 1.4g/hash, and diff was 15k... very lucky!

BTW, here is the Scrypt pool still on the wrong chain, it only has 3 miners though: http://sfr.hfrpool.fr/index.php?page=statistics&action=pool - It has one user with 300mhash, which I'm sure he will be gutted when he realizes his rig is pointed at the wrong fork and his coins are worthless.

Optimized SaffronCoin (Groestl algo) pool is now using the new wallet version 1.3.4.

http://cryptohunger.com:81

Seriously, what is the deal with Bittrex? When are they going to get it together?

+1
Amazing the way you guys handled this issue.

Yes LOLed at the apology as well. There are DEVs that have promised and missed dates by weeks if not months.

Couldn't stay up late enough last night to get my miners moved back over to Saffron, but did first thing this morning.  I had left one small miner working in hopes of it helping with the issues after the hardfork. 

No surprise, but great job getting through the minor hiccups with the hardfork!

I had to laugh at your apology for the one delay on the feature you guys are currently working on.  You guys have been fricken machines since you launched this coin.  I think we would all agree, we are happy to wait even a few days.  You all have certainly earned a break!

Thank you so much for all your hard work guys, REALLY!!

Comon man,

A few more details.... 

Windows version, Mac, 32bit, 64bit, etc, etc then maybe someone can help ?

Hi.

My wallet 1.3.4 doesn't start .

What can i do to solve the problem ?