iGotSpots (OP)
Legendary
Offline
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
|
|
January 17, 2014, 11:11:38 PM |
|
This is not good. I'm missing stg here..
This coin is the most unprofitable thing to mine atm according to coinwarz. and it has been, for the last couple of weeks. nobody mining this coin is an idiot! Yet you're all here..
you all know stg everybody else is missing out on?
That's because it will jump back up when difficulty drops back down. It'll go from first to last several times a day
|
|
|
|
iGotSpots (OP)
Legendary
Offline
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
|
|
January 17, 2014, 11:22:26 PM |
|
|
|
|
|
|
|
|
|
iGotSpots (OP)
Legendary
Offline
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
|
|
January 18, 2014, 08:45:13 PM |
|
10 SPOTS to anyone who posts an address before we get to page 68 - Only do it once or I'll skip both of your posts
|
|
|
|
Shivoreun
Member
Offline
Activity: 130
Merit: 10
|
|
January 18, 2014, 08:52:09 PM |
|
MVD3rtLUnm6RifpB4bRCpoRUcxNSLmNrgj Plz
|
P.S. Sorry for errors in English - it's not my native language...
|
|
|
Zeraful
|
|
January 18, 2014, 09:48:40 PM |
|
MJFTCDuWGzS9tTgcBM8cRXEL48kMkgRqTa D:
|
|
|
|
fearisfearless
|
|
January 19, 2014, 12:18:24 AM |
|
we still have another 3800+ blocks. It will be another 2 weeks before the hard fork kicks in 70 seconds, so 4433 minutes, or around Sunday. I'm going to keep everything saying Friday, though, to encourage people to update right away and not put it off 70 seconds? what kind of math are you using? So 3742 more blocks in the next 48 hours? Not looking good boss. The target block time is 70 seconds, and it's actually been a little quicker than that so far today. 1440 blocks per day is the target. Either way, whenever we hit that block it doesn't matter. The fork is coded for 81,000, so whether it's Sunday or next Wednesday, it makes no difference as far as the network is concerned The main point of the whole update was to fix the client, we only decided to do the hard fork because we needed an update anyway, super blocks are retarded, and it allowed us to do some network changes to the backend. I'm getting 60+ peers now within minutes of the QT being open, and that's not even on a VPS Don't you want to change the code to block 78000 instead of 81000? As I said before, it is going to take 2 weeks before this hard fork kicks in. BTW...how are you coming up with a target block time of 70 seconds? I am just trying to understand the logic before this coin.
|
|
|
|
CryptoMer
Newbie
Offline
Activity: 29
Merit: 0
|
|
January 19, 2014, 12:32:00 AM |
|
Can someone explain why the spots daemon has an open TCP connection to coinchoose?
~# host data.coinchoose.com data.coinchoose.com has address 162.243.78.234
:~# netstat -apn | grep 162.243.78.234 tcp 0 0 0.0.0.0:58743 162.243.78.234:4588 ESTABLISHED 2308/spotsd
|
|
|
|
iGotSpots (OP)
Legendary
Offline
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
|
|
January 19, 2014, 01:07:31 AM |
|
we still have another 3800+ blocks. It will be another 2 weeks before the hard fork kicks in 70 seconds, so 4433 minutes, or around Sunday. I'm going to keep everything saying Friday, though, to encourage people to update right away and not put it off 70 seconds? what kind of math are you using? So 3742 more blocks in the next 48 hours? Not looking good boss. The target block time is 70 seconds, and it's actually been a little quicker than that so far today. 1440 blocks per day is the target. Either way, whenever we hit that block it doesn't matter. The fork is coded for 81,000, so whether it's Sunday or next Wednesday, it makes no difference as far as the network is concerned The main point of the whole update was to fix the client, we only decided to do the hard fork because we needed an update anyway, super blocks are retarded, and it allowed us to do some network changes to the backend. I'm getting 60+ peers now within minutes of the QT being open, and that's not even on a VPS Don't you want to change the code to block 78000 instead of 81000? As I said before, it is going to take 2 weeks before this hard fork kicks in. BTW...how are you coming up with a target block time of 70 seconds? I am just trying to understand the logic before this coin. That's the target block time in the code
|
|
|
|
ckoeber
Member
Offline
Activity: 182
Merit: 10
|
|
January 19, 2014, 02:20:23 AM |
|
Don't you want to change the code to block 78000 instead of 81000? As I said before, it is going to take 2 weeks before this hard fork kicks in. BTW...how are you coming up with a target block time of 70 seconds? I am just trying to understand the logic before this coin.
I say leave it the way it is; too many people downloaded the new client to now update to another client. With your suggestion there will be two groups of "new" clients out there and that will cause more headaches than simply waiting the extra week or so...
|
|
|
|
iGotSpots (OP)
Legendary
Offline
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
|
|
January 19, 2014, 02:29:59 AM |
|
Don't you want to change the code to block 78000 instead of 81000? As I said before, it is going to take 2 weeks before this hard fork kicks in. BTW...how are you coming up with a target block time of 70 seconds? I am just trying to understand the logic before this coin.
I say leave it the way it is; too many people downloaded the new client to now update to another client. With your suggestion there will be two groups of "new" clients out there and that will cause more headaches than simply waiting the extra week or so... Don't worry, that's not happening. Whenever we hit block 81,000, it will fork. Whether it's tomorrow or next week makes no difference
|
|
|
|
fearisfearless
|
|
January 19, 2014, 05:49:17 AM |
|
Don't you want to change the code to block 78000 instead of 81000? As I said before, it is going to take 2 weeks before this hard fork kicks in. BTW...how are you coming up with a target block time of 70 seconds? I am just trying to understand the logic before this coin.
I say leave it the way it is; too many people downloaded the new client to now update to another client. With your suggestion there will be two groups of "new" clients out there and that will cause more headaches than simply waiting the extra week or so... Don't worry, that's not happening. Whenever we hit block 81,000, it will fork. Whether it's tomorrow or next week makes no difference What difference does it make, there is PLENTY of time to have "everyone" update to a new client. I am not sure who everyone is, but whatever. So is there a fix for confirming blocks as well? I was on a pool in which our last block was 8 hours ago and it still has not completed the 60 confirmations. It still has 36 more to go. I am sorry to sound like I am complaining, but damn if your going to release something like this, at least have a plan or a dev team. From the looks of it this is a solo setup, which is probably not a good thing. I'll continue to mine these useless as Coinye's and see where their destiny lies
|
|
|
|
ckoeber
Member
Offline
Activity: 182
Merit: 10
|
|
January 19, 2014, 06:14:43 AM |
|
What difference does it make, there is PLENTY of time to have "everyone" update to a new client. I am not sure who everyone is, but whatever. So is there a fix for confirming blocks as well? I was on a pool in which our last block was 8 hours ago and it still has not completed the 60 confirmations. It still has 36 more to go.
Problem is a lot of people don't check things as often as you do; they see updated client and then go wherever the latest link they can find. Not even all of the pools have updated to the 1.0.1 update; and the deadline was last Friday. You think people will check what version/fork they are on?
|
|
|
|
Desten
|
|
January 19, 2014, 06:19:10 AM |
|
Meantime the price is already 18xx.. Noone want to invest and buy 57290.13074426 at 2315-2308?
|
|
|
|
iGotSpots (OP)
Legendary
Offline
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
|
|
January 19, 2014, 06:35:49 AM |
|
Don't you want to change the code to block 78000 instead of 81000? As I said before, it is going to take 2 weeks before this hard fork kicks in. BTW...how are you coming up with a target block time of 70 seconds? I am just trying to understand the logic before this coin.
I say leave it the way it is; too many people downloaded the new client to now update to another client. With your suggestion there will be two groups of "new" clients out there and that will cause more headaches than simply waiting the extra week or so... Don't worry, that's not happening. Whenever we hit block 81,000, it will fork. Whether it's tomorrow or next week makes no difference What difference does it make, there is PLENTY of time to have "everyone" update to a new client. I am not sure who everyone is, but whatever. So is there a fix for confirming blocks as well? I was on a pool in which our last block was 8 hours ago and it still has not completed the 60 confirmations. It still has 36 more to go. I am sorry to sound like I am complaining, but damn if your going to release something like this, at least have a plan or a dev team. From the looks of it this is a solo setup, which is probably not a good thing. I'll continue to mine these useless as Coinye's and see where their destiny lies Not sure what any of this has to do with the dev team. It's taking a long time to confirm because difficulty is high right now and blocks are slow. We offer 10% off when using Spots for gold, silver, and copper right now, and it also has a few other merchants that started accepted it this week The longer it takes to hit block 81000 the longer people have to update. Before 81000 it doesn't matter which client you are using
|
|
|
|
iGotSpots (OP)
Legendary
Offline
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
|
|
January 19, 2014, 07:27:54 AM |
|
we still have another 3800+ blocks. It will be another 2 weeks before the hard fork kicks in 70 seconds, so 4433 minutes, or around Sunday. I'm going to keep everything saying Friday, though, to encourage people to update right away and not put it off 70 seconds? what kind of math are you using? So 3742 more blocks in the next 48 hours? Not looking good boss. The target block time is 70 seconds, and it's actually been a little quicker than that so far today. 1440 blocks per day is the target. Either way, whenever we hit that block it doesn't matter. The fork is coded for 81,000, so whether it's Sunday or next Wednesday, it makes no difference as far as the network is concerned The main point of the whole update was to fix the client, we only decided to do the hard fork because we needed an update anyway, super blocks are retarded, and it allowed us to do some network changes to the backend. I'm getting 60+ peers now within minutes of the QT being open, and that's not even on a VPS Don't you want to change the code to block 78000 instead of 81000? As I said before, it is going to take 2 weeks before this hard fork kicks in. BTW...how are you coming up with a target block time of 70 seconds? I am just trying to understand the logic before this coin. I see the problem. Coinchoose has been using coins-e price, which isn't accurate at all. Cryptsy is way more active
|
|
|
|
Bitcoin!
|
|
January 19, 2014, 12:52:57 PM |
|
MDKc3XMJzGXVzZf2f7YS9mChqZdNy7tL6Q
Thanks!
|
Report to moderator _///// [XVG] ★★★★★WE ARE ON THE VERGE ★★★★★ [SCRYPT] /////_ _//// TOR // I2P // LINUX . WINDOWS . MAC . ANDROID . ELECTRUM . WEBWALLET . GITHUB // WEBSITE // RADIO // IRC ////_
|
|
|
|