Klaasje
Legendary
 Offline
Activity: 1080
Merit: 1000
BTC - 14ZVqS5UGqhY77d5u9aUSW24ipRJ2g9wmm
|
 |
August 09, 2015, 05:06:45 PM |
|
Network and chain synced here with the pool. Looks good but I still get some other client connections. Like above.
On what chain are you? with what nodes? and on what block are you? |
Bitcoin - 14ZVqS5UGqhY77d5u9aUSW24ipRJ2g9wmm
|
|
|
|
Hobbyist
|
|
August 09, 2015, 10:07:37 PM |
|
Network and chain synced here with the pool. Looks good but I still get some other client connections. Like above.
On what chain are you? with what nodes? and on what block are you? The pool has this following connections. {
"version" : 1000001,
"protocolversion" : 60003,
"walletversion" : 60000,
"blocks" : 1391454,
"connections" : 11,
"proxy" : "",
"difficulty" : 0.00140321,
"testnet" : false,
"keypoololdest" : 1439110711,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.01000000,
"errors" : ""
}
rabbitcoind getblockhash 1391454
ba474a9bda51977bd31375555b81beeaef61b70f9125c4f17b71efcc04a7a62f
rabbitcoind getpeerinfo
[
{
"addr" : "87.76.236.188:63694",
"services" : "00000001",
"lastsend" : 1439157801,
"lastrecv" : 1439157800,
"conntime" : 1439063405,
"version" : 60003,
"subver" : "/Satoshi:1.0.0.1/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 1388235,
"banscore" : 0
},
{
"addr" : "117.6.130.233:17020",
"services" : "00000001",
"lastsend" : 1439157797,
"lastrecv" : 1439157797,
"conntime" : 1439064238,
"version" : 60003,
"subver" : "/Satoshi:1.0.1.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1460032,
"banscore" : 0
},
{
"addr" : "87.76.240.79:51757",
"services" : "00000001",
"lastsend" : 1439157800,
"lastrecv" : 1439157800,
"conntime" : 1439065656,
"version" : 60003,
"subver" : "/Satoshi:1.0.0.1/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 1388235,
"banscore" : 0
},
{
"addr" : "67.80.46.211:22556",
"services" : "00000003",
"lastsend" : 1439157800,
"lastrecv" : 1439157800,
"conntime" : 1439068411,
"version" : 70001,
"subver" : "/Shibetoshi:1.5.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 145119,
"banscore" : 0
},
{
"addr" : "37.233.101.127:17020",
"services" : "00000003",
"lastsend" : 1439157797,
"lastrecv" : 1439157786,
"conntime" : 1439072880,
"version" : 70002,
"subver" : "/NewYorkCoin:1.1.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1460318,
"banscore" : 0
},
{
"addr" : "99.63.193.158:53712",
"services" : "00000001",
"lastsend" : 1439157800,
"lastrecv" : 1439157800,
"conntime" : 1439083105,
"version" : 60003,
"subver" : "/Satoshi:1.0.0.1/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 1387374,
"banscore" : 0
},
{
"addr" : "96.255.60.31:22556",
"services" : "00000001",
"lastsend" : 1439157800,
"lastrecv" : 1439157800,
"conntime" : 1439085100,
"version" : 60003,
"subver" : "/Satoshi:0.6.4/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 104738,
"banscore" : 0
},
{
"addr" : "98.115.147.74:17020",
"services" : "00000001",
"lastsend" : 1439157800,
"lastrecv" : 1439157800,
"conntime" : 1439086975,
"version" : 60003,
"subver" : "/Satoshi:1.0.0.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1382147,
"banscore" : 0
},
{
"addr" : "115.236.88.86:17020",
"services" : "00000001",
"lastsend" : 1439157800,
"lastrecv" : 1439157800,
"conntime" : 1439137367,
"version" : 60003,
"subver" : "/Satoshi:1.0.0.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1384103,
"banscore" : 0
},
{
"addr" : "46.44.48.223:22566",
"services" : "00000003",
"lastsend" : 1439157800,
"lastrecv" : 1439157800,
"conntime" : 1439153965,
"version" : 70002,
"subver" : "/Satoshi:0.8.6.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 820417,
"banscore" : 0
}
]
The subver /Satoshi:1.0.0.1/ are valid nodes, I know the following are listening for incoming connections... addnode=76.95.178.229:17040 addnode=99.63.193.158:17020 |
|
|
|
|
Miner-TE
|
|
August 09, 2015, 11:31:25 PM |
|
Thanks for that info. Here is my current info.
16:28:13

getinfo
16:28:13

{
"version" : 1000001,
"protocolversion" : 60003,
"walletversion" : 60000,
"balance" : xxxxxxxxx.xxxxxxxx,
"blocks" : 1391627,
"connections" : 8,
"proxy" : "",
"difficulty" : 0.00146839,
"testnet" : false,
"keypoololdest" : 1438387854,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.01000000,
"errors" : ""
}
16:28:18

getpeerinfo
16:28:18

[
{
"addr" : "76.95.178.229:53723",
"services" : "00000001",
"lastsend" : 1439162857,
"lastrecv" : 1439162878,
"conntime" : 1439083858,
"version" : 60003,
"subver" : "/Satoshi:1.0.0.1/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 1388974,
"banscore" : 0
},
{
"addr" : "87.76.240.79:57801",
"services" : "00000001",
"lastsend" : 1439162858,
"lastrecv" : 1439162856,
"conntime" : 1439084392,
"version" : 60003,
"subver" : "/Satoshi:1.0.0.1/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 1388993,
"banscore" : 0
},
{
"addr" : "99.71.77.143:59029",
"services" : "00000003",
"lastsend" : 1439162855,
"lastrecv" : 1439162867,
"conntime" : 1439088085,
"version" : 70002,
"subver" : "/NewYorkCoin:1.1.0/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 1460826,
"banscore" : 0
},
{
"addr" : "87.76.236.188:62137",
"services" : "00000001",
"lastsend" : 1439162858,
"lastrecv" : 1439162856,
"conntime" : 1439101717,
"version" : 60003,
"subver" : "/Satoshi:1.0.0.1/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 1389578,
"banscore" : 0
},
{
"addr" : "62.221.89.173:36354",
"services" : "00000001",
"lastsend" : 1439162867,
"lastrecv" : 1439162867,
"conntime" : 1439127631,
"version" : 60003,
"subver" : "/Satoshi:1.0.1.1/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 1462139,
"banscore" : 0
},
{
"addr" : "130.211.116.160:53095",
"services" : "00000001",
"lastsend" : 1439162872,
"lastrecv" : 1439162872,
"conntime" : 1439156046,
"version" : 70003,
"subver" : "Dain 0.0.1",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 826693,
"banscore" : 0
},
{
"addr" : "77.37.240.140:53856",
"services" : "00000001",
"lastsend" : 1439162891,
"lastrecv" : 1439162891,
"conntime" : 1439160552,
"version" : 60003,
"subver" : "/Satoshi:1.0.0.1/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 353286,
"banscore" : 0
}
]
16:30:48

getblockhash 1391454
16:30:48

ba474a9bda51977bd31375555b81beeaef61b70f9125c4f17b71efcc04a7a62f
|
BTC - 1PeMMYGn7xbZjUYeaWe9ct1VV6szLS1vkD - LTC - LbtcJRJJQQBjZuHr6Wm7vtB9RnnWtRNYpq
|
|
|
|
Hobbyist
|
|
August 14, 2015, 03:53:18 AM |
|
How is everyone coming along? The chain looks stable from here.
Need to get the Blockexplorers and exchanges onboard and sync up.
|
|
|
|
|
OLX
|
|
August 14, 2015, 08:59:57 AM |
|
87.76.240.79
87.76.236.188
these are two of my wallet, now disabled
fully synchronized in this blokchein only node pool (76.95.178.229)?
|
|
|
|
|
|
LordCoder
|
|
August 21, 2015, 11:24:41 PM |
|
Any valid node?
|
|
|
|
|
|
Miner-TE
|
|
August 21, 2015, 11:37:06 PM |
|
Any valid node?
See last page of this thread, I had luck with these .... If you having trouble syncing, try these nodes ...
addnode=76.95.178.229:17040
addnode=99.63.193.158:17020
|
BTC - 1PeMMYGn7xbZjUYeaWe9ct1VV6szLS1vkD - LTC - LbtcJRJJQQBjZuHr6Wm7vtB9RnnWtRNYpq
|
|
|
|
LordCoder
|
|
August 21, 2015, 11:42:12 PM |
|
Any valid node?
See last page of this thread, I had luck with these .... If you having trouble syncing, try these nodes ...
addnode=76.95.178.229:17040
addnode=99.63.193.158:17020
There are lot of nodes and didn't see those valid ones. Thanks. |
|
|
|
|
|
adoalli
|
|
August 28, 2015, 05:58:10 AM |
|
addnode=xiaotiantech.eicp.net:17020
|
|
|
|
|
OLX
|
|
September 01, 2015, 06:47:19 PM
Last edit: September 01, 2015, 07:06:04 PM by OLX |
|
addnode=xiaotiantech.eicp.net:17020
this gives the wrong blokchein +23000 blocks. there is an option that is not rabbitcoin blockhein hobbyistpool today updated and it looks like that has got to blokchein longer on 23000 we were left with 99.63.193.158 are now together on blokchein which until today were threesome with hobbyistpool "addr" : "99.63.193.158:17020", "startingheight" : 1429788 if I am not mistaken, all who were mining in the hobbipule and output to offline wallet now another chain Hobbyist, check your transaction history after today's update. connect=99.63.193.158:17020 to return to the original |
|
|
|
|
|
Hobbyist
|
|
September 02, 2015, 12:04:02 AM |
|
Yes, The pool was on another fork and behind in block count. I re-synced it last night/today and it's joined the other nodes below at Current height 1450594.
"addr" : "115.236.88.86:17020",
"addr" : "204.11.237.233:38721",
"addr" : "98.115.147.74:17020",
"addr" : "122.233.243.196:17020",
The chain I was on was causing DB exceptions during reorgs. This chain appears stable.
My apologies for any lost coins caused by the other chain.
Can someone sanity check the following block hashes?
rabbitcoind getblockhash 1400000
33b81cf2473bfb10ee6b0defb3bb68971dafef7249cb97985036fcfff6136074
rabbitcoind getblockhash 1420000
5f1dac3cbbc606053cf44d7cf762d26c1c0cbfddb7b337ba70bc1e5ea8ec0bb6
rabbitcoind getblockhash 1450594
b0f6550c9bde9b7b8e2c8a045a500b8cf9d3334166313ebf4db9853c27f35b06
|
|
|
|
|
OLX
|
|
September 02, 2015, 02:43:30 AM |
|
About 3 weeks ago, I also had this error, resync with your IP and more have not seen her.
Your pool started checking with block 14292** finished 135**** (-100 000) which was 28 July, all who mining on hobbypool last month lost their coins/
Rabbitcoin mining for the last month several people (acckkiller, miner, ariesteam and me) + someone else solo sometimes connected, and probably 90% of the blocks were in your pool. and you decided to connect to another wallet which is likely all that time working solo, excellent!
I leave my wallets at the old chain. You do as you know
|
|
|
|
|
|
Hobbyist
|
|
September 02, 2015, 03:21:12 AM |
|
About 3 weeks ago, I also had this error, resync with your IP and more have not seen her.
Your pool started checking with block 14292** finished 135**** (-100 000) which was 28 July, all who mining on hobbypool last month lost their coins/
Rabbitcoin mining for the last month several people (acckkiller, miner, ariesteam and me) + someone else solo sometimes connected, and probably 90% of the blocks were in your pool. and you decided to connect to another wallet which is likely all that time working solo, excellent!
I leave my wallets at the old chain. You do as you know
The pools coind was having the DB exception constantly with over 10000+ delayed re-orgs. Appears a TX caused the max # of locks to be exhausted. I still have the other chain, I can put the node back on that chain but most of the network is on this other chain who is greater in height. We'll need to come to some agreement on what is the official chain. A new wallet with proper checkpoints will need to be built and released. |
|
|
|
|
OLX
|
|
September 02, 2015, 03:51:17 AM |
|
well, let's say that all went back to the new blockchain.
a month later again this error and the pool will go to the other - the third chain?
if you want to cryptsy resumed replenishment rbbt-coins she needed a stable pool and not one that jumps every month on different chains at the first error
|
|
|
|
|
|
loveys
|
|
September 02, 2015, 03:58:34 AM |
|
Yes, The pool was on another fork and behind in block count. I re-synced it last night/today and it's joined the other nodes below at Current height 1450594.
"addr" : "115.236.88.86:17020",
"addr" : "204.11.237.233:38721",
"addr" : "98.115.147.74:17020",
"addr" : "122.233.243.196:17020",
The chain I was on was causing DB exceptions during reorgs. This chain appears stable.
My apologies for any lost coins caused by the other chain.
Can someone sanity check the following block hashes?
rabbitcoind getblockhash 1400000
33b81cf2473bfb10ee6b0defb3bb68971dafef7249cb97985036fcfff6136074
rabbitcoind getblockhash 1420000
5f1dac3cbbc606053cf44d7cf762d26c1c0cbfddb7b337ba70bc1e5ea8ec0bb6
rabbitcoind getblockhash 1450594
b0f6550c9bde9b7b8e2c8a045a500b8cf9d3334166313ebf4db9853c27f35b06
i have connected these nodes,thanks! |
|
|
|
|
Hobbyist
|
|
September 02, 2015, 04:05:16 AM
Last edit: September 02, 2015, 04:16:37 AM by Hobbyist |
|
well, let's say that all went back to the new blockchain.
a month later again this error and the pool will go to the other - the third chain?
if you want to cryptsy resumed replenishment rbbt-coins she needed a stable pool and not one that jumps every month on different chains at the first error
That is the risk we all take without a DEV and a properly checkpointed client. I'm in the process of switching back to the old chain. Appears Doge had a similar problem https://github.com/dogecoin/dogecoin/issues/250Is there a block explorer for the old chain? it appears https://prohashing.com/explorer/Rabbitcoin is on the new chain. The community needs to agree on what is the official chain. 1st chain (1400000, uint256("0xe7330bf983cebb0f921079f774e22af2032b367162427bda37c9dba9acfa41ce")) (1420000, uint256("0xadea4fc3a47702cc7a109047ca76054875e54d06b5e5876094d9e0ead73c5fac")) 2nd chain (1400000, uint256("0x33b81cf2473bfb10ee6b0defb3bb68971dafef7249cb97985036fcfff6136074")) (1420000, uint256("0x5f1dac3cbbc606053cf44d7cf762d26c1c0cbfddb7b337ba70bc1e5ea8ec0bb6")) |
|
|
|
|
OLX
|
|
September 02, 2015, 04:49:32 AM |
|
another blockchain "startingheight" : 1529646 "subver" : "/NewYorkCoin:1.1.0/", "subver" : "/Satoshi:1.0.1.1/", getpeerinfo (8 connections) 
[
{
"addr" : "117.6.130.233:17020",
"services" : "00000001",
"lastsend" : 1441169111,
"lastrecv" : 1441169266,
"conntime" : 1441168722,
"version" : 60003,
"subver" : "/Satoshi:1.0.1.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1529646,
"banscore" : 0
},
{
"addr" : "67.80.46.211:22556",
"services" : "00000003",
"lastsend" : 1441169217,
"lastrecv" : 1441168730,
"conntime" : 1441168728,
"version" : 70001,
"subver" : "/Shibetoshi:1.5.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 145119,
"banscore" : 0
},
{
"addr" : "37.233.101.127:17020",
"services" : "00000003",
"lastsend" : 1441169262,
"lastrecv" : 1441169263,
"conntime" : 1441168729,
"version" : 70002,
"subver" : "/NewYorkCoin:1.1.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1529646,
"banscore" : 0
},
{
"addr" : "96.255.60.31:22556",
"services" : "00000001",
"lastsend" : 1441169251,
"lastrecv" : 1441169159,
"conntime" : 1441168730,
"version" : 60003,
"subver" : "/Satoshi:0.6.4/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 104738,
"banscore" : 0
},
{
"addr" : "98.115.147.74:17020",
"services" : "00000001",
"lastsend" : 1441169275,
"lastrecv" : 1441169277,
"conntime" : 1441168731,
"version" : 60003,
"subver" : "/Satoshi:1.0.0.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1451496,
"banscore" : 0
},
{
"addr" : "115.236.88.86:17020",
"services" : "00000001",
"lastsend" : 1441169275,
"lastrecv" : 1441169275,
"conntime" : 1441168733,
"version" : 60003,
"subver" : "/Satoshi:1.0.0.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1451496,
"banscore" : 0
},
{
"addr" : "188.165.2.147:17020",
"services" : "00000001",
"lastsend" : 1441169118,
"lastrecv" : 1441169271,
"conntime" : 1441168810,
"version" : 60003,
"subver" : "/Satoshi:1.0.1.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1529646,
"banscore" : 0
},
{
"addr" : "203.20.114.252:17020",
"services" : "00000001",
"lastsend" : 1441169117,
"lastrecv" : 1441169264,
"conntime" : 1441168876,
"version" : 60003,
"subver" : "/Satoshi:1.0.1.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1529646,
"banscore" : 0
}
]
|
|
|
|
|
|
Hobbyist
|
|
September 02, 2015, 05:06:00 AM |
|
The newyorkcoin chain is just that, NewYorkCoin. Both coins use C0C0C0 as their peermagic. The clients will connect to each other.
If we ever hard-fork, get this changed... We also share port 17020.
|
|
|
|
|
Hobbyist
|
|
September 03, 2015, 04:01:31 AM |
|
addnode=76.95.178.229:17040
addnode=99.63.193.158:17020
The above nodes are back online and accepting connections. |
|
|
|
|
loveys
|
|
September 03, 2015, 08:12:27 AM |
|
well, let's say that all went back to the new blockchain.
a month later again this error and the pool will go to the other - the third chain?
if you want to cryptsy resumed replenishment rbbt-coins she needed a stable pool and not one that jumps every month on different chains at the first error
That is the risk we all take without a DEV and a properly checkpointed client. I'm in the process of switching back to the old chain. Appears Doge had a similar problem https://github.com/dogecoin/dogecoin/issues/250Is there a block explorer for the old chain? it appears https://prohashing.com/explorer/Rabbitcoin is on the new chain. The community needs to agree on what is the official chain. 1st chain (1400000, uint256("0xe7330bf983cebb0f921079f774e22af2032b367162427bda37c9dba9acfa41ce")) (1420000, uint256("0xadea4fc3a47702cc7a109047ca76054875e54d06b5e5876094d9e0ead73c5fac")) 2nd chain (1400000, uint256("0x33b81cf2473bfb10ee6b0defb3bb68971dafef7249cb97985036fcfff6136074")) (1420000, uint256("0x5f1dac3cbbc606053cf44d7cf762d26c1c0cbfddb7b337ba70bc1e5ea8ec0bb6")) have synced with 2nd chain |
|
|
|
|
