|
Sheldor333
|
 |
January 04, 2014, 02:23:04 PM |
|
Don't worry if the developer doesn't respond he is probably busy doing something. When I PMed him it usually takes some time but it doesn't matter. Hope you will get a lot of donation to develop it since this is an amazing coin and it is worth the trouble.
|
|
|
|
|
|
cobrabyte
Member
 Offline
Activity: 70
Merit: 10
|
|
January 04, 2014, 08:25:53 PM |
|
Bump. If you haven't updated your StableCoin client to v1.5, you're about to be left behind. The scheduled fork is scheduled to occur in ~250 blocks @ 317,000.
This should occur within the next 8 to 10 hours. I suspect there will be some extra hashing power jumping on nearer to the fork point so that miners can build their round shares for maximum payout potential on the other side of the fork.
|
|
|
|
|
filipe3x
|
|
January 05, 2014, 12:51:17 AM |
|
sbc.bitember.com is ready for the transition.  |
|
|
|
|
|
thimo
|
|
January 05, 2014, 01:00:38 AM |
|
sbc.bitember.com is ready for the transition. 187 blocks to go. |
i can rent this1
|
|
|
profall
Full Member
Offline
Activity: 298
Merit: 100
dApps Development Automation Platform
|
|
January 05, 2014, 07:45:41 AM |
|
100 blocks to go!
|
|
|
|
|
thimo
|
|
January 05, 2014, 12:08:37 PM |
|
In 40 blocks a hard fork will occur. Make sure you have updated to 1.5!
|
i can rent this1
|
|
|
Sunny94
Newbie
Offline
Activity: 32
Merit: 0
|
|
January 05, 2014, 12:55:19 PM |
|
The dev have not connected since 28/12/2013, that's some inactivity.
So i do not really want to mine this even after the fork
|
|
|
|
|
|
gnode
|
|
January 05, 2014, 01:52:38 PM |
|
In 40 blocks a hard fork will occur. Make sure you have updated to 1.5!
So about another 15 blocks and then the diff will start to go down to a more reasonable value!!! |
|
|
|
|
|
Catswold
|
|
January 05, 2014, 01:57:55 PM |
|
The dev have not connected since 28/12/2013, that's some inactivity.
So i do not really want to mine this even after the fork
You are not alone in noticing this, nor in your reluctance. |
|
|
|
|
|
gnode
|
|
January 05, 2014, 02:11:41 PM |
|
In 40 blocks a hard fork will occur. Make sure you have updated to 1.5!
So about another 15 blocks and then the diff will start to go down to a more reasonable value!!! 10 more blocks and we will see. |
|
|
|
|
cobrabyte
Member
Offline
Activity: 70
Merit: 10
|
|
January 05, 2014, 02:43:14 PM |
|
Over the hump. Should retarget at block 317010... |
|
|
|
Nanolucas
Newbie
Offline
Activity: 56
Merit: 0
|
|
January 05, 2014, 02:45:37 PM |
|
Difficulty 7.57905579
Est Next Difficulty 1.17337981
I guess now we wait and see how accurate this is. With a maximum of 12% down that should take a while still though  |
|
|
|
|
Sejnt
Newbie
Offline
Activity: 42
Merit: 0
|
|
January 05, 2014, 03:42:12 PM |
|
It works!
|
|
|
|
|
cobrabyte
Member
Offline
Activity: 70
Merit: 10
|
|
January 05, 2014, 03:42:35 PM |
|
GetNextWorkRequired RETARGET
nTargetTimespan = 600 nActualTimespan = 672
Before: 1c21c6db 0000000021c6db00000000000000000000000000000000000000000000000000
After: 1c25d47a 0000000025d47a66666666666666666666666666666666666666666666666666
SetBestChain: new best=3d6de0773f0ca262b454 height=317010 work=1215750526522949 date=01/05/14 15:40:54
ProcessBlock: ACCEPTED
Nice, we're back in business. |
|
|
|
|
Catswold
|
|
January 05, 2014, 03:43:43 PM |
|
Difficulty 7.57905579
Est Next Difficulty 1.17337981
I guess now we wait and see how accurate this is. With a maximum of 12% down that should take a while still though Yep. Now 6.77 difficulty. Gonna be a while. |
|
|
|
|
|
gnode
|
|
January 05, 2014, 03:44:06 PM |
|
diff is now 6.767!! It won't take long to drop way down, goes down about 1.0 every hour.
|
|
|
|
|
ChevaL
Member
Offline
Activity: 71
Merit: 10
|
|
January 05, 2014, 03:49:15 PM |
|
Glad it's working. I'll throw 1.5 MH in to help you guys |
|
|
|
|
cobrabyte
Member
Offline
Activity: 70
Merit: 10
|
|
January 05, 2014, 03:51:09 PM |
|
Really glad @artos was here to ensure everything went well...  |
|
|
|
ChevaL
Member
Offline
Activity: 71
Merit: 10
|
|
January 05, 2014, 04:04:45 PM |
|
Really glad @artos was here to ensure everything went well... I assume he knew what he was doing, let's just assume he's confident |
|
|
|
|
|
