[ANN] [SPOT] | SUCCESSFUL FORK COMPLETE - On CoinPayments.net/Cryptsy/Coins-e

[iGotSpots]

1) Blockexplorer #1 permanently down, blockexplorer #2 shows nothing in "Block Count:", "Difficulty:" and "Connections:". So coinchoose cannot get information.
2) wallet is permanently knocking litecoin door. It's a waste of time and resources. Fix wallet and upload windows client. Make coind.exe available too. Link to googledocs contains Wallet v1.0.2.0-unk-nug Aug 29 2013, 20:02:03. Sources at github are ver 1.0. I haven't linux so cannot fix client myself to prevent connection to peers on port 9333.

Litecoin syncs haven't happened since the first release, at least not that I'm aware of except for you getting it. 1.0.2 is the most updated client

[iGotSpots]

For a min I thought the coin was dead!!!!!

Far from it. I haven't posted in this thread in a while because we have 3 new projects being actively developed. These are going to be payable only with Spots, Copper Bars, and Tickets, which I am doing the marketing for now

I really want to tell you guys more, but I really can't, yet. We don't post or bump our threads to just stay on the first page. We only update with live, relevant services or stores accepting the coin. Our silence recently is not due to anything bad happening; it is quite the contrary.

Ahhhhhh fuck it, here's a little dish

The first project is web-based and will create a LOT of opportunities for the users to "earn" the coin of their choice. No, it's not fill out surveys or some stupid shit

The second one does have to do with advertising, and we can release more info on that very soon, it's kind of been placed on the backburner for the above project right now

The third, and most exciting, project is our renewable energy miners. The goal is 0 electricity cost while being able to power enough hardware to produce 150 gHash on Sha, or about 20 scrypt mHash (rough estimate for the scrypt numbers) with no energy bills. We are focusing on powering ASIC's for now due to their lower requirements with increased numbers, but these are not chips or anything like that. You can use these on anything, even your kitchen if you wanted to.  Again, this is our most in depth project and will not be updating regularly with details. We will do press releases and videos when we are closer to completion. Right now we only have the first build up and running. It's currently powering 10 erupter blades with about 120ish gHash and $0 electricity costs as I type this. For how long, though? That's the question we are going to answer before we post any updates. We've recently added an engineer to the team locally to help with size and noise restraints to make these more miner friendly

Thanks for sticking around, everyone. Please remember...in the case of Spots, CPR, and TIX...silence does not indicate inactivity, but quite the opposite. Feel free to PM me any questions and I'll do my best to answer them in case they are missed in this thread

-Pfeff

[Desten]

iGotSpots, i think you can add in todo-list this: calc difficulty not only for last 2/3 blocks or what there now. As i wathing last 5 days - huje jumps in networkhash happening: from 7-9Mh to 100-350Mh... And because of that there are not correct blocks_per_hour value if we watch more that 1-2-3 hours. In 5 days period there is a big divergence from what you planned. So wallets/network can correct difficulty not just in last 2/3 blocks but with coefficient that includes blocks_per_week or something to be more stable blocks_per_hour rate at big periods and to prevent instamining at one time when multipools/huge miners are switching to coin when there are low difficulty.
This will protect coin from future dumping by huge&fast instaminers.
How do you think?

PS: blocked litecoin network/port from wallet only by rule in Kaspersky Internet Security if you don't want to fix wallet

[MobGod]

iGotSpots, i think you can add in todo-list this: calc difficulty not only for last 2/3 blocks or what there now. As i wathing last 5 days - huje jumps in networkhash happening: from 7-9Mh to 100-350Mh... And because of that there are not correct blocks_per_hour value if we watch more that 1-2-3 hours. In 5 days period there is a big divergence from what you planned. So wallets/network can correct difficulty not just in last 2/3 blocks but with coefficient that includes blocks_per_week or something to be more stable blocks_per_hour rate at big periods and to prevent instamining at one time when multipools/huge miners are switching to coin when there are low difficulty.
This will protect coin from future dumping by huge&fast instaminers.
How do you think?

PS: blocked litecoin network/port from wallet only by rule in Kaspersky Internet Security if you don't want to fix wallet

100% need to get multi pool away

[iGotSpots]

iGotSpots, i think you can add in todo-list this: calc difficulty not only for last 2/3 blocks or what there now. As i wathing last 5 days - huje jumps in networkhash happening: from 7-9Mh to 100-350Mh... And because of that there are not correct blocks_per_hour value if we watch more that 1-2-3 hours. In 5 days period there is a big divergence from what you planned. So wallets/network can correct difficulty not just in last 2/3 blocks but with coefficient that includes blocks_per_week or something to be more stable blocks_per_hour rate at big periods and to prevent instamining at one time when multipools/huge miners are switching to coin when there are low difficulty.
This will protect coin from future dumping by huge&fast instaminers.
How do you think?

PS: blocked litecoin network/port from wallet only by rule in Kaspersky Internet Security if you don't want to fix wallet

Difficulty adjustment has worked very well for Spots. Earlier when the multipools were hopping on it, the quick retarget and longer block times were causing their miners to get disconnected from the multipool from switching coins too many times too fast. That caused us to be dropped from most (if not all) of them, which is awesome for the people mining Spots directly. I believe the difficulty targeting is working pretty perfectly

I'm glad you found a ghetto work around for the litecoin cross chatter. You can also manually ban nodes you catch trying to send the much longer blockchain to your client

[iGotSpots]

iGotSpots, i think you can add in todo-list this: calc difficulty not only for last 2/3 blocks or what there now. As i wathing last 5 days - huje jumps in networkhash happening: from 7-9Mh to 100-350Mh... And because of that there are not correct blocks_per_hour value if we watch more that 1-2-3 hours. In 5 days period there is a big divergence from what you planned. So wallets/network can correct difficulty not just in last 2/3 blocks but with coefficient that includes blocks_per_week or something to be more stable blocks_per_hour rate at big periods and to prevent instamining at one time when multipools/huge miners are switching to coin when there are low difficulty.
This will protect coin from future dumping by huge&fast instaminers.
How do you think?

PS: blocked litecoin network/port from wallet only by rule in Kaspersky Internet Security if you don't want to fix wallet

100% need to get multi pool away

I'm not aware of any that still hop on Spots. If you are, please let me know which so I can watch them a little closer and figure out a way to dissuade their forumulas from trying to jump on

Even if they do, they are only getting maybe 5 blocks at the absolute max before it adjusts higher and they get off. And being 70 second blocks, that's like 5 minutes of them mining nothing. Downtime is exactly what they are against, and it's proven to be our strongest defense against them

[gr33k]

Hey noticed no more node connections on spotsd. Overall hashrate seems low - client works for me but spotsd doesn't.

Do you have new source code for spotsd which is based on current code? The link to the latest source crashed my server I'm not going to compile it again as it also seems to be dated. Do you have a github with the latest sources?

Also - overall spots network hashrates seem low - Coin's outlook looking grim.

Thank you 

[iGotSpots]

Hey noticed no more node connections on spotsd. Overall hashrate seems low - client works for me but spotsd doesn't.

Do you have new source code for spotsd which is based on current code? The link to the latest source crashed my server I'm not going to compile it again as it also seems to be dated. Do you have a github with the latest sources?

Also - overall spots network hashrates seem low - Coin's outlook looking grim.

Thank you 

I'll take a look this weekend. It's not grim at all. Spots is about to be added to WorkForCrypto.com

[gr33k]

Cool thank you

Sounds cool that it's being added - but maybe I'm using old spotsd daemon? how many have you released thus far?

Was working fine up until yesterday pretty much. stuck on block 46355

[iGotSpots]

Cool thank you

Sounds cool that it's being added - but maybe I'm using old spotsd daemon? how many have you released thus far?

Was working fine up until yesterday pretty much. stuck on block 46355

We haven't had to update the client for months. Your only issue is being stuck on that block? Current block is 47167

[gr33k]

Well that being due to not being able to connect to any nodes I guess yep.

I had 2 on there - removed and added all on your original post - no dice. Rebooted server and all that normal stuff to test -

[iGotSpots]

Well that being due to not being able to connect to any nodes I guess yep.

I had 2 on there - removed and added all on your original post - no dice. Rebooted server and all that normal stuff to test -

addnode=67.167.228.42
addnode=69.85.86.195
addnode=68.103.6.158
addnode=71.187.248.95
addnode=70.69.238.84
addnode=108.185.218.246
addnode=70.98.114.229

Those are what I have in my .conf right now and synced up no problem. We'll have a few more nodes up this weekend when we add it to WorkForCrypto, too

[Desten]

addnode=[deleted]

how to make blocknotify=xxx work without creating new window at top of all windows when, for example, i edited conf like this:
blocknotify=somebatfile.bat
blocknotify=start /b cmd /q /d /c somecommand..
blocknotify=wscript somescript.vbs
blocknotify=somescript.vbs
?
All of these are creating new window that f**cks my fullscreen applications that running when block found.
And walletnotify didn't work at all.
Want spotscoind.exe for windows. Compile it, please.

[lorr4crypto]

Ahhhhhh fuck it, here's a little dish

The first project is web-based and will create a LOT of opportunities for the users to "earn" the coin of their choice. No, it's not fill out surveys or some stupid shit

The second one does have to do with advertising, and we can release more info on that very soon, it's kind of been placed on the backburner for the above project right now

The third, and most exciting, project is our renewable energy miners. The goal is 0 electricity cost while being able to power enough hardware to produce 150 gHash on Sha, or about 20 scrypt mHash (rough estimate for the scrypt numbers) with no energy bills. We are focusing on powering ASIC's for now due to their lower requirements with increased numbers, but these are not chips or anything like that. You can use these on anything, even your kitchen if you wanted to.  Again, this is our most in depth project and will not be updating regularly with details. We will do press releases and videos when we are closer to completion. Right now we only have the first build up and running. It's currently powering 10 erupter blades with about 120ish gHash and $0 electricity costs as I type this. For how long, though? That's the question we are going to answer before we post any updates. We've recently added an engineer to the team locally to help with size and noise restraints to make these more miner friendly

Good to know there will be more to do with Spots- it was one of the earliest Scrypt coins I mined on a regular basis.  I'm sitting on almost 4k and have my 700kh/s pointed at Spots while the network looks soooooo thin.  I think there might be a multipool trying to connect because the network bumps up to 28mh/s from 8mh/s right after the low difficulty blocks (or maybe the network hashrate meter on the vircurpool SPT pool is inaccurate).  Either that or some big fish solo-miner is trying to hit those profit blocks or trying to fork it?  Anyway, I'm excited about the miners you're developing, any estimation of costs?  Particularly in Spots?

Edit: The network hashrate seems to have stabilized around 15mh/s over the past few difficulty adjustments- but it seemed for a while that those extra 20mh/s were showing up right after the easy difficulty blocks.  Actually, maybe it's just lag- network hashrate is usually an average over a period of time.

[kslavik]

Good to know there will be more to do with Spots- it was one of the earliest Scrypt coins I mined on a regular basis.  I'm sitting on almost 4k and have my 700kh/s pointed at Spots while the network looks soooooo thin.  I think there might be a multipool trying to connect because the network bumps up to 28mh/s from 8mh/s right after the low difficulty blocks (or maybe the network hashrate meter on the vircurpool SPT pool is inaccurate).  Either that or some big fish solo-miner is trying to hit those profit blocks or trying to fork it?  Anyway, I'm excited about the miners you're developing, any estimation of costs?  Particularly in Spots?

Edit: The network hashrate seems to have stabilized around 15mh/s over the past few difficulty adjustments- but it seemed for a while that those extra 20mh/s were showing up right after the easy difficulty blocks.  Actually, maybe it's just lag- network hashrate is usually an average over a period of time.

You are quite right about extra 20Mhs that jumps on the network when difficulty is low :-), Last 2-3 days when the price dropped so much , it was not profitable to jump on this coin even with a low difficulty.

Edit: network speed is calculated based on the time it took the network to find the last block (may be several blocks). The reason you see the network hash rate stable at 15mhs, is because the profitability of SPT is too low to mine it even with low difficulty.

[iGotSpots]

No problem. I'll post the daemon once we compile it to add Spots to WorkForCrypto.com

[gr33k]

The only node I was able to connect to (and I had to use the spots console on my windows machine) is:

216.56.62.132

now I have THREE active connections on spotsd:

 # spotsd getpeerinfo                                                                                                                                                                            [22:05:07]
[
    {
        "addr" : "216.56.62.132:4588",
        "services" : "00000001",
        "lastsend" : 1383890816,
        "lastrecv" : 1383890817,
        "conntime" : 1383890540,
        "version" : 60001,
        "subver" : "/Satoshi:1.0.0/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 50304,
        "banscore" : 0
    },
    {
        "addr" : "135.0.19.87:9333",
        "services" : "00000001",
        "lastsend" : 1383890808,
        "lastrecv" : 1383890819,
        "conntime" : 1383890716,
        "version" : 70002,
        "subver" : "/Satoshi:0.8.3.7/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 456028,
        "banscore" : 0
    },
    {
        "addr" : "95.223.14.90:9333",
        "services" : "00000001",
        "lastsend" : 1383890816,
        "lastrecv" : 1383890816,
        "conntime" : 1383890718,
        "version" : 70002,
        "subver" : "/Satoshi:0.8.5.1/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 456028,
        "banscore" : 0

Hope those help anyone else having connectivity issues

However - I've put the pool on maintenance mode (aka closed for the time being) until we get that new source code out.

The stability issues are causing problems with my other pool and services running

Thank you for the update though! Hope to see Spots get back to booming  

EDIT: now I have anywhere from 6-8...The fix was adding 216.56.62.132 to my nodes

[Desten]

Port 9333 is litecoin port. Spots always connects to other coins. I asked iGotSpots for the fix but he said that there is nothing to fix.
So, you have only one connection for the spots network. There are no more nodes. I think that coin now is really dead. My compassion.. and i'm little upset of that, but there is nothing to do.
My distant wallet is online for some time little more (maybe 2-3 weeks), you can add it to your addnodes:
addnode=[deleted]

[lorr4crypto]

Well...

The vircurpool is closing down, the mining network is extremely thin, and only one node out of about a dozen addnodes is working.

Seems like it's dead- sad because I have a soft Spots in my heart... lol.  And because I spent the last day or two increasing my SPT holdings by 50%.  Defibrillator anyone?

[Desten]

iGotSpots give a lot of promises, but i see that this was just promises. It's like Jagrapolite's & zacklark promises about adt - there is nothing behind them.. nothing. So this coins like other is dying hard.