Looks like we are good. Everything seems to line up, let me know if anyone sees anything unusual. Thanks
Seems fine, started to sync
Awesome. Glad we caught it quick
Topic: [ANN] [SPOT] | SUCCESSFUL FORK COMPLETE - On CoinPayments.net/Cryptsy/Coins-e - page 65. (Read 166041 times)
July 31, 2013, 11:07:34 AM
Looks like we are good. Everything seems to line up, let me know if anyone sees anything unusual. Thanks
Seems fine, started to sync
Awesome. Glad we caught it quick
July 31, 2013, 11:01:57 AM
Looks like we are good. Everything seems to line up, let me know if anyone sees anything unusual. Thanks
Seems fine, started to sync
July 31, 2013, 10:58:52 AM
Looks like we are good. Everything seems to line up, let me know if anyone sees anything unusual. Thanks
July 31, 2013, 09:48:23 AM
July 31, 2013, 09:45:20 AM
Any Spotter Blocks found?
Nope. Only a .01% per block so it could be the next 10 or there may never be one ever.
Quick way to check...go here:
http://altcha.in/chain/Spots
Take total coins / 49
If that is equal to the block number then we don't have any yet. If it doesn't match up then subtract 10045 until you get to the block number. Each time you subtract that's a spotter block
Still no spotter blocks found. At block 5166 with 253134 outstanding. 253134 / 49 = 5166.
Now I have to wait to test the new Next Block Reward predictor script for Spots
July 31, 2013, 09:18:41 AM
wallet suddenly stopped syncing (it worked few hours ago)
Here is debug info:
trying connection 68.103.6.158:4588 lastseen=354243.5hrs
connection timeout
trying connection 97.89.174.206:4588 lastseen=0.0hrs
connected 97.89.174.206:4588
send version message: version 60001, blocks=5142, them=97.89.174.206:4588, peer=97.89.174.206:4588
Added time data, samples 2, offset +0 (+0 minutes)
receive version message: version 60001, blocks=7163, them=97.89.174.206:4588, peer=97.89.174.206:4588
trying connection 68.41.11.231:4588 lastseen=30.6hrs
Added 2 addresses from 97.89.174.206: 6 tried, 500 new
received block 73fd6be90e91db982c0c
disconnecting node 97.89.174.206:4588
Disconnected 97.89.174.206:4588 for misbehavior (score=100)
ERROR: ProcessBlock() : block with timestamp before last checkpoint
Here is debug info:
trying connection 68.103.6.158:4588 lastseen=354243.5hrs
connection timeout
trying connection 97.89.174.206:4588 lastseen=0.0hrs
connected 97.89.174.206:4588
send version message: version 60001, blocks=5142, them=97.89.174.206:4588, peer=97.89.174.206:4588
Added time data, samples 2, offset +0 (+0 minutes)
receive version message: version 60001, blocks=7163, them=97.89.174.206:4588, peer=97.89.174.206:4588
trying connection 68.41.11.231:4588 lastseen=30.6hrs
Added 2 addresses from 97.89.174.206: 6 tried, 500 new
received block 73fd6be90e91db982c0c
disconnecting node 97.89.174.206:4588
Disconnected 97.89.174.206:4588 for misbehavior (score=100)
ERROR: ProcessBlock() : block with timestamp before last checkpoint
July 31, 2013, 01:23:21 AM
you should make a mining calculator, that always motivates people
July 30, 2013, 11:56:55 PM
I wonder what the August 8th announcement could be...
July 30, 2013, 10:40:34 PM
Looks like we will be hitting block 5000 today
Definetly
WHat will happen on block 5000 ? any changes ?
No, just a milestone. These are still relatively rare
July 30, 2013, 05:19:45 PM
Looks like we will be hitting block 5000 today
Definetly
WHat will happen on block 5000 ? any changes ?
July 30, 2013, 04:18:22 PM
Looks like we will be hitting block 5000 today
July 30, 2013, 03:29:17 PM
Is it possible/profitable to solo mine still on an i5?
The difficulty retargeting is very quick. Sometimes it's at a very low difficulty and other times it is very high. If you watch coinchoose.com, when it jumps to the top of the list for profitability, that's when the diff is lowest
July 30, 2013, 03:19:10 PM
Is it possible/profitable to solo mine still on an i5?
July 30, 2013, 03:12:00 PM
Don't do same mistake as UNOCS
What mistakes would that be? I have paid 0 attention to them. Not interested at all in umbrellas
That would be announcing date for releasing something very cool, then some problems happen and they can't release at that day, community goes crazy for more than week and don't believe any word they say and part of people start to dump their coins and coin value goes 2x down
Either give yourself big margin in case problems will happen (eg additional week) or don't post precise date, it can seriously damage this coin if things will not go smootly
Not that I think you will get into problems, simply worried about coin, I like this one
Ah, thanks. Now I understand what people were talking about on Cryptsy today.
August 8th is not the release date for what we have planned. It's the day we are announcing what is going to be coming. And it's big
July 30, 2013, 02:54:16 PM
Don't do same mistake as UNOCS
What mistakes would that be? I have paid 0 attention to them. Not interested at all in umbrellas
That would be announcing date for releasing something very cool, then some problems happen and they can't release at that day, community goes crazy for more than week and don't believe any word they say and part of people start to dump their coins and coin value goes 2x down
Either give yourself big margin in case problems will happen (eg additional week) or don't post precise date, it can seriously damage this coin if things will not go smootly
Not that I think you will get into problems, simply worried about coin, I like this one
July 30, 2013, 02:47:59 PM
Don't do same mistake as UNOCS
What mistakes would that be? I have paid 0 attention to them. Not interested at all in umbrellas
July 30, 2013, 02:43:33 PM
Don't do same mistake as UNOCS
July 30, 2013, 01:50:49 PM
July 29, 2013, 11:33:14 PM
Hashrate is 400Mh now ~~ 
Yep. Expect difficulty to get pretty high for an hour or so. Don't get deterred, though, it'll come back down very quickly when the big hashers bounce somewhere else
July 29, 2013, 11:18:46 PM
Hashrate is 400Mh now ~~
Jump to: