Bitcoin Forum
November 19, 2024, 09:43:18 AM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 [75] 76 77 78 79 80 81 82 »
  Print  
Author Topic: [ANN] [SPOT] | SUCCESSFUL FORK COMPLETE - On CoinPayments.net/Cryptsy/Coins-e  (Read 166068 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
SWKineo
Newbie
*
Offline Offline

Activity: 45
Merit: 0


View Profile
February 13, 2014, 10:58:38 PM
 #1481

With any luck, the difficulty algorithm will see how long it took to find 79992 and set the diff super low. We just have to hope that multipools won't jump on at that point.
ckoeber
Member
**
Offline Offline

Activity: 182
Merit: 10


View Profile
February 13, 2014, 11:12:50 PM
 #1482

With any luck, the difficulty algorithm will see how long it took to find 79992 and set the diff super low. We just have to hope that multipools won't jump on at that point.

Too late for that;' they will be jumping in. I think with luck most of the multipools will be on the old fork(s) and thus won't be able to capitalize.
Desten
Sr. Member
****
Offline Offline

Activity: 357
Merit: 250


View Profile
February 13, 2014, 11:18:53 PM
 #1483

I think with luck most of the multipools will be on the old fork(s) and thus won't be able to capitalize.
They will see after few blocks that something wrong and will update their wallets.. And will jump in and out again.
To protect coin from multipools there must be twice or triple miners power more than all jumping multipools together.
Now we at price point 15'000-130'000 times lower than doge... 130 thousand times (!) lower. It's a crazy number.
Coin need good PR. Very good and strong PR.
SWKineo
Newbie
*
Offline Offline

Activity: 45
Merit: 0


View Profile
February 13, 2014, 11:23:44 PM
 #1484

I think with luck most of the multipools will be on the old fork(s) and thus won't be able to capitalize.
They will see after few blocks that something wrong and will update their wallets.. And will jump in and out again.
To protect coin from multipools there must be twice or triple miners power more than all jumping multipools together.
Now we at price point 15'000-130'000 times lower than doge... 130 thousand times (!) lower. It's a crazy number.
Coin need good PR. Very good and strong PR.

The new site's supposedly going up this month. At the very least, that should make the coin easier to find and more appealing.
Desten
Sr. Member
****
Offline Offline

Activity: 357
Merit: 250


View Profile
February 13, 2014, 11:36:56 PM
 #1485

SWKineo, you working on it (site)?
I know who dumps now. Know for sure. This man was in our group. He turned out as awful creature and scum. He decided to make money on others in group. He is a rat. Moscow vile creature. And i see that he reads this topic. Now i'm 100% sure.
Do not fall for his provocation if you believe in this coin and wish it to skyrocket. Do not let him buy back coins that he spent for dump. It's craziness to sell coin that are very rare, very hard to mine, eats so much electricity to mine one block. You decide, but think of that. There are not so much coins mined and will be total, block reward is not so big. It's not litecoin or doge, but it can be traded much-much higher.
Hello, moscow bastard!
SWKineo
Newbie
*
Offline Offline

Activity: 45
Merit: 0


View Profile
February 14, 2014, 12:16:29 AM
 #1486

SWKineo, you working on it (site)?
I know who dumps now. Know for sure. This man was in our group. He turned out as awful creature and scum. He decided to make money on others in group. He is a rat. Moscow vile creature. And i see that he reads this topic. Now i'm 100% sure.
Do not fall for his provocation if you believe in this coin and wish it to skyrocket. Do not let him buy back coins that he spent for dump. It's craziness to sell coin that are very rare, very hard to mine, eats so much electricity to mine one block. You decide, but think of that. There are not so much coins mined and will be total, block reward is not so big. It's not litecoin or doge, but it can be traded much-much higher.
Hello, moscow bastard!

Eh... I was just repeating a possibly inaccurate piece of information from back in mid January.

Believe me, I haven't sold since Spots were worth 18579, and I've bought back nearly ten times the total amount I've ever sold. I understand the potential value of the coin. However, I can not understand who your post was aimed at, or what you were trying to demonstrate by alluding to them as a character rather than as a real person.
Desten
Sr. Member
****
Offline Offline

Activity: 357
Merit: 250


View Profile
February 14, 2014, 12:23:31 AM
 #1487

SWKineo, first line of my prev message was to you. Other lines, except last line - for all peoples here. Last line - for that dumper russian moscow bastard.
Sorry for confusing/misunderstanding.
iGotSpots (OP)
Legendary
*
Offline Offline

Activity: 2548
Merit: 1054


CPU Web Mining 🕸️ on webmining.io


View Profile WWW
February 14, 2014, 12:38:19 AM
 #1488

The fork will make diff jumps moved much slower instead of large leaps from 0 to 20

The new website for both the coin and metals market is on hold right now while we catch up on orders.  The new year set us back a bit with having new licenses to file for this year and we ended with a backlog of about 8 weeks

Once all the orders are filled it'll be reopened when everyone's order is filled instead of increasing the backlog

djmuk
Newbie
*
Offline Offline

Activity: 14
Merit: 0


View Profile
February 14, 2014, 11:13:27 AM
 #1489

Can you confirm version numbers for new wallet as I am getting an error:

WARNING: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade

I thought I had the latest version:

Getinfo gives me:

"version" : 1010000,
"protocolversion" : 60080,
"walletversion" : 60000,

Thanks
SWKineo
Newbie
*
Offline Offline

Activity: 45
Merit: 0


View Profile
February 14, 2014, 02:17:58 PM
Last edit: February 14, 2014, 02:29:19 PM by SWKineo
 #1490

OK, it's awesome that we've officially hit the hardfork, but I'm having the same problem as djmuk.

On a separate topic, how is it that the difficulty of block 78992 went up by a factor of four (to 13.53539526) after the previous block, 78991 (diff 3.38384881) , took fourteen hours to find?

EDIT: Removing the bad addnodes and adding in
Code:
addnode=54.201.183.106
addnode=72.78.100.12
resulted in the error going away and the block sync bar appearing, but it's stuck at 12 blocks left (79902 downloaded)
Desten
Sr. Member
****
Offline Offline

Activity: 357
Merit: 250


View Profile
February 14, 2014, 02:51:47 PM
Last edit: February 14, 2014, 03:05:27 PM by Desten
 #1491

block 79002, out of sync, crosschatting.
iGotSpots?

Upd:
hardfork has shorter blockchain vs previous wallets....
"12 blocks left...."

Cryptsy is on new wallet or old? What wold happen, if cryptsy is on old wallet? This 12 (now) block will flood cryptsy, then more. What would be next? Cryptsy will delist spots?
iGotSpots, coin need your attention NOW.

[
{
"addr" : "54.201.183.106:4588",
"services" : "00000001",
"lastsend" : 1392389879,
"lastrecv" : 1392389886,
"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" : 1392389887,
"lastrecv" : 1392389877,
"conntime" : 1392389563,
"version" : 60080,
"subver" : "/Satoshi:1.1.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 79002,
"banscore" : 0
},
{
"addr" : "72.8.181.74:4588",
"services" : "00000001",
"lastsend" : 1392389886,
"lastrecv" : 1392389874,
"conntime" : 1392389569,
"version" : 60001,
"subver" : "/Satoshi:1.0.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 79014,
"banscore" : 0
},
{
"addr" : "193.68.21.38:4588",
"services" : "00000001",
"lastsend" : 1392389885,
"lastrecv" : 1392389874,
"conntime" : 1392389570,
"version" : 60080,
"subver" : "/Satoshi:1.1.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 79002,
"banscore" : 0
},
{
"addr" : "162.220.246.58:4588",
"services" : "00000001",
"lastsend" : 1392389888,
"lastrecv" : 1392389847,
"conntime" : 1392389578,
"version" : 60001,
"subver" : "/Satoshi:1.0.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 79014,
"banscore" : 0
},
{
"addr" : "216.56.62.132:4588",
"services" : "00000001",
"lastsend" : 1392389887,
"lastrecv" : 1392389879,
"conntime" : 1392389591,
"version" : 60001,
"subver" : "/Satoshi:1.0.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 79014,
"banscore" : 0
},
{
"addr" : "178.79.190.235:4588",
"services" : "00000001",
"lastsend" : 1392389879,
"lastrecv" : 1392389884,
"conntime" : 1392389665,
"version" : 60001,
"subver" : "/Satoshi:1.0.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 79014,
"banscore" : 0
}
]
iGotSpots (OP)
Legendary
*
Offline Offline

Activity: 2548
Merit: 1054


CPU Web Mining 🕸️ on webmining.io


View Profile WWW
February 14, 2014, 07:23:06 PM
 #1492

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

iGotSpots (OP)
Legendary
*
Offline Offline

Activity: 2548
Merit: 1054


CPU Web Mining 🕸️ on webmining.io


View Profile WWW
February 14, 2014, 07:26:14 PM
 #1493

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

iGotSpots (OP)
Legendary
*
Offline Offline

Activity: 2548
Merit: 1054


CPU Web Mining 🕸️ on webmining.io


View Profile WWW
February 14, 2014, 07:48:01 PM
 #1494

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?

Desten
Sr. Member
****
Offline Offline

Activity: 357
Merit: 250


View Profile
February 14, 2014, 08:26:07 PM
 #1495

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
}
]
iGotSpots (OP)
Legendary
*
Offline Offline

Activity: 2548
Merit: 1054


CPU Web Mining 🕸️ on webmining.io


View Profile WWW
February 14, 2014, 10:06:13 PM
 #1496

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

Code:
        if(pfrom->nVersion != 60080)
            badVersion = true;

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

forzendiablo
Legendary
*
Offline Offline

Activity: 1526
Merit: 1000


the grandpa of cryptos


View Profile
February 15, 2014, 12:20:10 PM
 #1497

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

yolo
SWKineo
Newbie
*
Offline Offline

Activity: 45
Merit: 0


View Profile
February 15, 2014, 06:43:06 PM
 #1498

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

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

Activity: 910
Merit: 1000



View Profile
February 17, 2014, 06:45:53 AM
 #1499

http://spots.cryptcoins.net/  is up to date and working.
NUFCrichard
Legendary
*
Offline Offline

Activity: 1218
Merit: 1003


View Profile
February 17, 2014, 11:51:23 AM
 #1500

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?
Pages: « 1 ... 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 [75] 76 77 78 79 80 81 82 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!