Topic: [ANN] [SPOT] | SUCCESSFUL FORK COMPLETE - On CoinPayments.net/Cryptsy/Coins-e - page 7. (Read 166083 times)

I'll be opening gold silver and copper sales back up soon when we catch up on orders

Had too many too fast and instead of increasing the wait time we decided to suspend new sales until we are all caught up

2400 now and rising. Can I hit 3000?

Pumping spots now.

I'm only post #395 in since reading from the beginning. Not sure if any ideas about SPOTS has changed since that time from the developer since I am still reading the posts. I have some questions:

1) How many spots will ever be in existence?
2) Does the value of SPOTS decrease as time goes by due to more spots being mined? I.e. will my 30,000 spots become worth 3,000 spots today if 10x more coin of spots that exist today is mined over time and put into circulation?

We've seen values above 20,000 satoshis before.
I'm not saying that I expect it to hit that point again, but that just illustrates how badly undervalued Spots are currently.

how much SPOT/Mh/day?

Woah shit. Good thing I own at least 23,000 spots.

Thanks for the reply. I guess I'll just keep holding for now then. I have noticed value has slowly been rising. I figured it is under value as well due to low trade volume.

DRobert, you can read my semi-calculations about comparison spots vs mainly doge and see that spots price now is about >100 thousands times less than doge (earlier page or two).

PS: all sell part of spots now 0.00001866 to 0.00005284 worth only 13.89 BTC. This is equivalent to doge's ONE firts sell line: 0.00000222   6175480.32981674   13.70956633.
Funny, yeah.
PPS: two days ago this sell part was from 1800 spotoshis to 2995 spotoshis and was about 8 BTC's.
This is a huge undervalue of coin.
PPPS: more PR, and take best things/ideas from other coins and price will rise from 1800 spotoshis to 180000 minimum (10 thousand times).
PPPPS: we started slow-pump @14 feb, because we protect coin from dumping by moscow bastard i talked about earlier. We have much reserves to block price falling, but we do not see much opportunity in price rising. Where are you all, guys? If we will raise price only 100times more - we will have much more miners, block finding time will stabilise and multipools will be off the border. If we raise price 500 times then new investors come from other coins. Awake from sleep, do some work for this coin.


WHY spots are not on coinmarketcap again?

SPOTS slowly appreciating again after the halving. I wonder how long until it reaches 2400 or higher again.

Aw, so I read a little more about this coin. What makes this coin worth 0.00024 btc per SPOT? I saw the spike in price twice to that amount on Cryptsy since Sept 2013. But what is keeping it from being at a much higher price than it is now if it is supposed to be aligned with gold and silver? I put a sell order up at 0.0002 just in case. Not sure when to expect those prices again, but w/e.

Anyone experienced with spots, could you please give me some insight as to what the plan for this coin is over the next few months to a year to help it appreciate in price? Thanks.

I was going to comment on this as well; the difficulty spikes have gotten better (doesn't go from 0.1 to 20) but still not as smooth as it should be.

There should be NO difficulty spike; good coins change difficulty every block and the difficulty change is not that much, like no more than 1-2% difficulty change either way based on the last block.

That way you can get smooth and predictable mining all the way through.

It's odd, that... it was obviously happening before the fork too, but in that case, it was running on the same code which had previously hit the 70 sec time quite consistently.

Quick question, now it seems the blocks are moving, but still 50 blocks between 79257 and 79307 nearly 9 hours.
50 blocks should take just under 1 hour, or is it not aiming to be 70 seconds per block anymore?

http://spots.cryptcoins.net/  is up to date and working.

I'm using ckoeber's pool, http://spotspool.chriskoeber.com/ . It's up to date and works quite well.

love the coi nbut lack of working pools is killing me.

If you are can compile your own client, you can edit main.cpp lines 2373 and 2474 to this:


That will only allow peers on 60080 protocol to connect, getting rid of all other chains, but also limiting you only to people running the 60080 protocol version of Spots

Out of sync, new lot of bad nodes in peers.
PS: how to make spoiler here?

getpeerinfo:


[
{
"addr" : "54.201.183.106:4588",
"services" : "00000001",
"lastsend" : 1392409467,
"lastrecv" : 1392409496,
"conntime" : 1392389562,
"version" : 60080,
"subver" : "/Satoshi:1.1.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 79002,
"banscore" : 0
},
{
"addr" : "72.78.100.12:4588",
"services" : "00000001",
"lastsend" : 1392409481,
"lastrecv" : 1392409494,
"conntime" : 1392389563,
"version" : 60080,
"subver" : "/Satoshi:1.1.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 79002,
"banscore" : 0
},
{
"addr" : "193.68.21.38:4588",
"services" : "00000001",
"lastsend" : 1392409522,
"lastrecv" : 1392409526,
"conntime" : 1392389570,
"version" : 60080,
"subver" : "/Satoshi:1.1.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 79002,
"banscore" : 0
},
{
"addr" : "71.4.209.204:51858",
"services" : "00000001",
"lastsend" : 1392409535,
"lastrecv" : 1392409482,
"conntime" : 1392390002,
"version" : 60080,
"subver" : "/Satoshi:1.1.0/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 79002,
"banscore" : 0
},
{
"addr" : "87.98.190.199:39921",
"services" : "00000001",
"lastsend" : 1392409515,
"lastrecv" : 1392409487,
"conntime" : 1392395124,
"version" : 60080,
"subver" : "/Satoshi:1.1.0/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 79018,
"banscore" : 0
},
{
"addr" : "67.172.235.111:45510",
"services" : "00000001",
"lastsend" : 1392409512,
"lastrecv" : 1392409530,
"conntime" : 1392395184,
"version" : 60080,
"subver" : "/Satoshi:1.1.0/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 79018,
"banscore" : 0
},
{
"addr" : "188.81.112.220:56931",
"services" : "00000001",
"lastsend" : 1392409505,
"lastrecv" : 1392409484,
"conntime" : 1392395781,
"version" : 60080,
"subver" : "/Satoshi:1.1.0/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 79018,
"banscore" : 0
},
{
"addr" : "174.100.38.43:12212",
"services" : "00000001",
"lastsend" : 1392409534,
"lastrecv" : 1392409514,
"conntime" : 1392398276,
"version" : 60080,
"subver" : "/Satoshi:1.1.0/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 79024,
"banscore" : 0
},
{
"addr" : "192.241.136.248:57992",
"services" : "00000001",
"lastsend" : 1392409488,
"lastrecv" : 1392409492,
"conntime" : 1392398712,
"version" : 60001,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 47352,
"banscore" : 0
},
{
"addr" : "68.116.172.128:58582",
"services" : "00000001",
"lastsend" : 1392409535,
"lastrecv" : 1392409534,
"conntime" : 1392402883,
"version" : 60080,
"subver" : "/Satoshi:1.1.0/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 79024,
"banscore" : 0
},
{
"addr" : "193.242.159.253:51314",
"services" : "00000001",
"lastsend" : 1392409523,
"lastrecv" : 1392409534,
"conntime" : 1392404795,
"version" : 60080,
"subver" : "/Satoshi:1.1.0/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 79024,
"banscore" : 0
},
{
"addr" : "72.133.204.106:4588",
"services" : "00000001",
"lastsend" : 1392409522,
"lastrecv" : 1392409514,
"conntime" : 1392405744,
"version" : 60080,
"subver" : "/Satoshi:1.1.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 79024,
"banscore" : 0
},
{
"addr" : "85.90.193.224:55119",
"services" : "00000001",
"lastsend" : 1392409526,
"lastrecv" : 1392409520,
"conntime" : 1392407930,
"version" : 60080,
"subver" : "/Satoshi:1.1.0/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 79028,
"banscore" : 0
},
{
"addr" : "109.152.156.86:63151",
"services" : "00000001",
"lastsend" : 1392409524,
"lastrecv" : 1392409515,
"conntime" : 1392408001,
"version" : 60080,
"subver" : "/Satoshi:1.1.0/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 79028,
"banscore" : 0
},
{
"addr" : "188.69.199.154:55752",
"services" : "00000001",
"lastsend" : 1392409530,
"lastrecv" : 1392409530,
"conntime" : 1392408912,
"version" : 60001,
"subver" : "/Satoshi:0.6.4/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 59749,
"banscore" : 0
},
{
"addr" : "74.69.66.147:62915",
"services" : "00000001",
"lastsend" : 1392409494,
"lastrecv" : 1392409466,
"conntime" : 1392409104,
"version" : 60001,
"subver" : "/Satoshi:1.0.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 79023,
"banscore" : 0
},
{
"addr" : "50.77.240.41:20683",
"services" : "00000001",
"lastsend" : 1392409528,
"lastrecv" : 1392409444,
"conntime" : 1392409159,
"version" : 60001,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 161488,
"banscore" : 0
},
{
"addr" : "111.198.246.223:63829",
"services" : "00000001",
"lastsend" : 1392409535,
"lastrecv" : 1392409521,
"conntime" : 1392409232,
"version" : 60001,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 161488,
"banscore" : 0
},
{
"addr" : "95.85.28.31:55965",
"services" : "00000001",
"lastsend" : 1392409487,
"lastrecv" : 1392409533,
"conntime" : 1392409484,
"version" : 60001,
"subver" : "/Satoshi:1.0.0/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 79023,
"banscore" : 0
}
]

Anyone still having sync issues while I wait for confirmation from the exchanges?

My client is totally synced now, check mark and everything. Everyone else all good now?

I told Cryptsy and coins-e about the fork weeks ago and they said they knew it was coming. If they didn't update, it's on them

Talking to BitJohn right now to make sure they are on 60080. Will bump when I'm sure we are all synced

Coins-e hasn't responded, so if you guys want to send them emails too to make sure they know, that would be helpful

Protocol 60080 is updated clients that are on the 79000 fork. Any other version is on either 81000 or did not update at all. Once everyone is upgraded, we can do another soft fork (not mandatory) that will ban any nodes not on 60080, eliminating ALL sync issues

You can edit your own ban rules, if you guys want to in the source, to ban any nodes not on 60080. If anyone wants me to post that info, let me know. Otherwise I will do it in a QT and update the github with the new rules in 2 weeks to give everyone time to update to the new protocol. If you downloaded the 79000 QT you are on 60080