boki15
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 25, 2014, 08:46:50 PM |
|
Yes I did, many times. Version 3.3.3.3 syncs to block 9165, 3.3.4.3 to 1025, 3.3.4.4 to 9020.
When version 3.3.4.3 came out, I wanted to try it and wanted to see if sync is working properly. I deleted all data, started wallet and since then it did not work. I left the wallet for more than 24 hours version 3.3.4.3 open and nothing. Today I compiled new version 3.3.4.4, still does not work. Running peerinfo I can see than all peers do have version 3.3.3.3.
If new versions are broken, why are broken version posted untested? Is there anyone who can resync completly with 3.3.4.4?
|
|
|
|
kernels10
Sr. Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 408
Merit: 250
ded
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 25, 2014, 08:54:02 PM |
|
Yes I did, many times. Version 3.3.3.3 syncs to block 9165, 3.3.4.3 to 1025, 3.3.4.4 to 9020.
When version 3.3.4.3 came out, I wanted to try it and wanted to see if sync is working properly. I deleted all data, started wallet and since then it did not work. I left the wallet for more than 24 hours version 3.3.4.3 open and nothing. Today I compiled new version 3.3.4.4, still does not work. Running peerinfo I can see than all peers do have version 3.3.3.3.
If new versions are broken, why are broken version posted untested? Is there anyone who can resync completly with 3.3.4.4?
I'm fully synced with 3.3.4.4
|
|
|
|
boki15
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 25, 2014, 08:57:21 PM |
|
As you can see I was mining and staking, and I can't withdraw even if I want: ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FqD2iyUJ.png&t=665&c=h4kvMCspFzWhbA) Last confirmed block before I tried resync: ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FWkdK11G.png&t=665&c=3sxJ-tZLpgNgPw)
|
|
|
|
boki15
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 25, 2014, 08:57:57 PM |
|
Yes I did, many times. Version 3.3.3.3 syncs to block 9165, 3.3.4.3 to 1025, 3.3.4.4 to 9020.
When version 3.3.4.3 came out, I wanted to try it and wanted to see if sync is working properly. I deleted all data, started wallet and since then it did not work. I left the wallet for more than 24 hours version 3.3.4.3 open and nothing. Today I compiled new version 3.3.4.4, still does not work. Running peerinfo I can see than all peers do have version 3.3.3.3.
If new versions are broken, why are broken version posted untested? Is there anyone who can resync completly with 3.3.4.4?
I'm fully synced with 3.3.4.4 Could you try to delete all data except your wallet and resync?
|
|
|
|
|
mikelitoris
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 25, 2014, 10:04:52 PM |
|
Fak off, yer just put me off buying pink coin forever
|
6561742061206469636b
|
|
|
irlandescoin
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 25, 2014, 10:13:01 PM |
|
stuck at block 9027
|
back here after the boom in 2013
|
|
|
boki15
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 25, 2014, 10:26:58 PM |
|
DEV, WALLET DOES NOT SYNC!!!
|
|
|
|
boki15
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 25, 2014, 10:35:55 PM |
|
All wallets after 3.3.3.3 are broken, switched now 3.3.3.3 again and it shows completly different information and doesn't pass 6508 ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2F42zNfNP.png&t=665&c=NhdYPGTmtFah2w) ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FPsgg0Wp.png&t=665&c=oOLsfuYxDjT_aQ) after starting again 3.3.4.4 ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2Fl2iJBnP.png&t=665&c=0ln4NjbI1aSo_A) Seconds later I am on block 9027 and stucked again ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2F2HGD6dQ.png&t=665&c=W3veEAVE-pyFMw) And now no question marks anymore?: ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2F0ZU6js3.png&t=665&c=uyqacfslKmL0vg)
|
|
|
|
kernels10
Sr. Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 408
Merit: 250
ded
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 25, 2014, 10:42:47 PM |
|
Yes I did, many times. Version 3.3.3.3 syncs to block 9165, 3.3.4.3 to 1025, 3.3.4.4 to 9020.
When version 3.3.4.3 came out, I wanted to try it and wanted to see if sync is working properly. I deleted all data, started wallet and since then it did not work. I left the wallet for more than 24 hours version 3.3.4.3 open and nothing. Today I compiled new version 3.3.4.4, still does not work. Running peerinfo I can see than all peers do have version 3.3.3.3.
If new versions are broken, why are broken version posted untested? Is there anyone who can resync completly with 3.3.4.4?
I'm fully synced with 3.3.4.4 Could you try to delete all data except your wallet and resync? these are what I'm connected to now, after deleting everything.  [ { "addr" : "fzwpi2uqgauy225m.onion:24112", "services" : "00000001", "lastsend" : 1406327624, "lastrecv" : 1406327614, "conntime" : 1406327550, "version" : 70101, "subver" : "/Illuminatus:3.3.4.4/", "inbound" : false, "releasetime" : 0, "startingheight" : 9984, "banscore" : 1 }, { "addr" : "4mmbxrdk5xorxq4s.onion:24112", "services" : "00000001", "lastsend" : 1406327615, "lastrecv" : 1406327623, "conntime" : 1406327556, "version" : 70101, "subver" : "/Illuminatus:3.3.4.4/", "inbound" : false, "releasetime" : 0, "startingheight" : 9984, "banscore" : 1 }, { "addr" : "sv44mb2qcyxfwnbw.onion:24112", "services" : "00000001", "lastsend" : 1406327615, "lastrecv" : 1406327616, "conntime" : 1406327570, "version" : 70099, "subver" : "/Pyramid:3.3.3.3/", "inbound" : false, "releasetime" : 0, "startingheight" : 9002, "banscore" : 1 }, { "addr" : "6kickq6scfajdhot.onion:24112", "services" : "00000001", "lastsend" : 1406327679, "lastrecv" : 1406327680, "conntime" : 1406327679, "version" : 70099, "subver" : "/Pyramid:3.3.3.3/", "inbound" : false, "releasetime" : 0, "startingheight" : 9002, "banscore" : 1 } ] those two that are running 3.3.3.3 are messing with the network. if you compile yourself, edit version.h, change min proto version so its the same as the network protocol version. Then recompile. This will not allow older version to connect to you
|
|
|
|
boki15
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 25, 2014, 10:51:57 PM |
|
Yes I did, many times. Version 3.3.3.3 syncs to block 9165, 3.3.4.3 to 1025, 3.3.4.4 to 9020.
When version 3.3.4.3 came out, I wanted to try it and wanted to see if sync is working properly. I deleted all data, started wallet and since then it did not work. I left the wallet for more than 24 hours version 3.3.4.3 open and nothing. Today I compiled new version 3.3.4.4, still does not work. Running peerinfo I can see than all peers do have version 3.3.3.3.
If new versions are broken, why are broken version posted untested? Is there anyone who can resync completly with 3.3.4.4?
I'm fully synced with 3.3.4.4 Could you try to delete all data except your wallet and resync? these are what I'm connected to now, after deleting everything.  [ { "addr" : "fzwpi2uqgauy225m.onion:24112", "services" : "00000001", "lastsend" : 1406327624, "lastrecv" : 1406327614, "conntime" : 1406327550, "version" : 70101, "subver" : "/Illuminatus:3.3.4.4/", "inbound" : false, "releasetime" : 0, "startingheight" : 9984, "banscore" : 1 }, { "addr" : "4mmbxrdk5xorxq4s.onion:24112", "services" : "00000001", "lastsend" : 1406327615, "lastrecv" : 1406327623, "conntime" : 1406327556, "version" : 70101, "subver" : "/Illuminatus:3.3.4.4/", "inbound" : false, "releasetime" : 0, "startingheight" : 9984, "banscore" : 1 }, { "addr" : "sv44mb2qcyxfwnbw.onion:24112", "services" : "00000001", "lastsend" : 1406327615, "lastrecv" : 1406327616, "conntime" : 1406327570, "version" : 70099, "subver" : "/Pyramid:3.3.3.3/", "inbound" : false, "releasetime" : 0, "startingheight" : 9002, "banscore" : 1 }, { "addr" : "6kickq6scfajdhot.onion:24112", "services" : "00000001", "lastsend" : 1406327679, "lastrecv" : 1406327680, "conntime" : 1406327679, "version" : 70099, "subver" : "/Pyramid:3.3.3.3/", "inbound" : false, "releasetime" : 0, "startingheight" : 9002, "banscore" : 1 } ] those two that are running 3.3.3.3 are messing with the network. if you compile yourself, edit protocol.h, change min proto version so its the same as the network protocol version. Then recompile. This will not allow older version to connect to you Thanks for suggestion, but if that would be the problem, then version 3.3.4.4 would not stuck, as there are peers with same version, my peers are not much different than yours 00:49:41 ? [ { "addr" : "4mmbxrdk5xorxq4s.onion:24112", "services" : "00000001", "lastsend" : 1406328129, "lastrecv" : 1406328433, "conntime" : 1406328129, "version" : 70101, "subver" : "/Illuminatus:3.3.4.4/", "inbound" : false, "releasetime" : 0, "startingheight" : 9984, "banscore" : 1 }, { "addr" : "lig5vcicm6hgjggx.onion:24112", "services" : "00000001", "lastsend" : 1406328133, "lastrecv" : 1406328136, "conntime" : 1406328132, "version" : 70099, "subver" : "/Pyramid:3.3.3.3/", "inbound" : false, "releasetime" : 0, "startingheight" : 9002, "banscore" : 1 }, { "addr" : "sr77eqw7cxkc34zy.onion:24112", "services" : "00000001", "lastsend" : 1406328540, "lastrecv" : 1406328173, "conntime" : 1406328137, "version" : 70099, "subver" : "/Pyramid:3.3.3.3/", "inbound" : false, "releasetime" : 0, "startingheight" : 6508, "banscore" : 1 }, { "addr" : "mcf4bxy7ksfl2jce.onion:24112", "services" : "00000001", "lastsend" : 1406328433, "lastrecv" : 1406328397, "conntime" : 1406328142, "version" : 70099, "subver" : "/Pyramid:3.3.3.3/", "inbound" : false, "releasetime" : 0, "startingheight" : 6508, "banscore" : 1 }, { "addr" : "ufoi7dt2lv575nlh.onion:24112", "services" : "00000001", "lastsend" : 1406328417, "lastrecv" : 1406328162, "conntime" : 1406328158, "version" : 70099, "subver" : "/Pyramid:3.3.3.3/", "inbound" : false, "releasetime" : 0, "startingheight" : 9002, "banscore" : 1 }, { "addr" : "qsjqt5tpcx7qsqfy.onion:24112", "services" : "00000001", "lastsend" : 1406328398, "lastrecv" : 1406328415, "conntime" : 1406328162, "version" : 70099, "subver" : "/Pyramid:3.3.3.3/", "inbound" : false, "releasetime" : 0, "startingheight" : 9002, "banscore" : 1 }, { "addr" : "66pgszhqlte4u5n3.onion:24112", "services" : "00000001", "lastsend" : 1406328454, "lastrecv" : 1406328537, "conntime" : 1406328452, "version" : 70101, "subver" : "/Illuminatus:3.3.4.4/", "inbound" : false, "releasetime" : 0, "startingheight" : 9027, "banscore" : 1 }, { "addr" : "ywedag3i2e3ocvel.onion:24112", "services" : "00000001", "lastsend" : 1406328477, "lastrecv" : 1406328479, "conntime" : 1406328477, "version" : 70101, "subver" : "/Illuminatus:3.3.4.4/", "inbound" : false, "releasetime" : 0, "startingheight" : 9027, "banscore" : 1 } ]
|
|
|
|
boki15
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 25, 2014, 10:59:06 PM |
|
if you compile yourself, edit version.h, change min proto version so its the same as the network protocol version. Then recompile. This will not allow older version to connect to you
I am compiling now with with min proto version 70101, let's see maybe you are right and it solves the problem.
|
|
|
|
darkmatter7
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 64
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 25, 2014, 10:59:32 PM |
|
Yes I did, many times. Version 3.3.3.3 syncs to block 9165, 3.3.4.3 to 1025, 3.3.4.4 to 9020.
When version 3.3.4.3 came out, I wanted to try it and wanted to see if sync is working properly. I deleted all data, started wallet and since then it did not work. I left the wallet for more than 24 hours version 3.3.4.3 open and nothing. Today I compiled new version 3.3.4.4, still does not work. Running peerinfo I can see than all peers do have version 3.3.3.3.
If new versions are broken, why are broken version posted untested? Is there anyone who can resync completly with 3.3.4.4?
I'm fully synced with 3.3.4.4 Could you try to delete all data except your wallet and resync? these are what I'm connected to now, after deleting everything.  [ { "addr" : "fzwpi2uqgauy225m.onion:24112", "services" : "00000001", "lastsend" : 1406327624, "lastrecv" : 1406327614, "conntime" : 1406327550, "version" : 70101, "subver" : "/Illuminatus:3.3.4.4/", "inbound" : false, "releasetime" : 0, "startingheight" : 9984, "banscore" : 1 }, { "addr" : "4mmbxrdk5xorxq4s.onion:24112", "services" : "00000001", "lastsend" : 1406327615, "lastrecv" : 1406327623, "conntime" : 1406327556, "version" : 70101, "subver" : "/Illuminatus:3.3.4.4/", "inbound" : false, "releasetime" : 0, "startingheight" : 9984, "banscore" : 1 }, { "addr" : "sv44mb2qcyxfwnbw.onion:24112", "services" : "00000001", "lastsend" : 1406327615, "lastrecv" : 1406327616, "conntime" : 1406327570, "version" : 70099, "subver" : "/Pyramid:3.3.3.3/", "inbound" : false, "releasetime" : 0, "startingheight" : 9002, "banscore" : 1 }, { "addr" : "6kickq6scfajdhot.onion:24112", "services" : "00000001", "lastsend" : 1406327679, "lastrecv" : 1406327680, "conntime" : 1406327679, "version" : 70099, "subver" : "/Pyramid:3.3.3.3/", "inbound" : false, "releasetime" : 0, "startingheight" : 9002, "banscore" : 1 } ] those two that are running 3.3.3.3 are messing with the network. if you compile yourself, edit protocol.h, change min proto version so its the same as the network protocol version. Then recompile. This will not allow older version to connect to you Thanks for suggestion, but if that would be the problem, then version 3.3.4.4 would not stuck, as there are peers with same version, my peers are not much different than yours 00:49:41 ? [ { "addr" : "4mmbxrdk5xorxq4s.onion:24112", "services" : "00000001", "lastsend" : 1406328129, "lastrecv" : 1406328433, "conntime" : 1406328129, "version" : 70101, "subver" : "/Illuminatus:3.3.4.4/", "inbound" : false, "releasetime" : 0, "startingheight" : 9984, "banscore" : 1 }, { "addr" : "lig5vcicm6hgjggx.onion:24112", "services" : "00000001", "lastsend" : 1406328133, "lastrecv" : 1406328136, "conntime" : 1406328132, "version" : 70099, "subver" : "/Pyramid:3.3.3.3/", "inbound" : false, "releasetime" : 0, "startingheight" : 9002, "banscore" : 1 }, { "addr" : "sr77eqw7cxkc34zy.onion:24112", "services" : "00000001", "lastsend" : 1406328540, "lastrecv" : 1406328173, "conntime" : 1406328137, "version" : 70099, "subver" : "/Pyramid:3.3.3.3/", "inbound" : false, "releasetime" : 0, "startingheight" : 6508, "banscore" : 1 }, { "addr" : "mcf4bxy7ksfl2jce.onion:24112", "services" : "00000001", "lastsend" : 1406328433, "lastrecv" : 1406328397, "conntime" : 1406328142, "version" : 70099, "subver" : "/Pyramid:3.3.3.3/", "inbound" : false, "releasetime" : 0, "startingheight" : 6508, "banscore" : 1 }, { "addr" : "ufoi7dt2lv575nlh.onion:24112", "services" : "00000001", "lastsend" : 1406328417, "lastrecv" : 1406328162, "conntime" : 1406328158, "version" : 70099, "subver" : "/Pyramid:3.3.3.3/", "inbound" : false, "releasetime" : 0, "startingheight" : 9002, "banscore" : 1 }, { "addr" : "qsjqt5tpcx7qsqfy.onion:24112", "services" : "00000001", "lastsend" : 1406328398, "lastrecv" : 1406328415, "conntime" : 1406328162, "version" : 70099, "subver" : "/Pyramid:3.3.3.3/", "inbound" : false, "releasetime" : 0, "startingheight" : 9002, "banscore" : 1 }, { "addr" : "66pgszhqlte4u5n3.onion:24112", "services" : "00000001", "lastsend" : 1406328454, "lastrecv" : 1406328537, "conntime" : 1406328452, "version" : 70101, "subver" : "/Illuminatus:3.3.4.4/", "inbound" : false, "releasetime" : 0, "startingheight" : 9027, "banscore" : 1 }, { "addr" : "ywedag3i2e3ocvel.onion:24112", "services" : "00000001", "lastsend" : 1406328477, "lastrecv" : 1406328479, "conntime" : 1406328477, "version" : 70101, "subver" : "/Illuminatus:3.3.4.4/", "inbound" : false, "releasetime" : 0, "startingheight" : 9027, "banscore" : 1 } ]
hmm. I am syncing fine, but I see that you're having problems. We'll work through this ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) You know why.
|
|
|
|
boki15
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 25, 2014, 11:12:22 PM |
|
Yes I did, many times. Version 3.3.3.3 syncs to block 9165, 3.3.4.3 to 1025, 3.3.4.4 to 9020.
When version 3.3.4.3 came out, I wanted to try it and wanted to see if sync is working properly. I deleted all data, started wallet and since then it did not work. I left the wallet for more than 24 hours version 3.3.4.3 open and nothing. Today I compiled new version 3.3.4.4, still does not work. Running peerinfo I can see than all peers do have version 3.3.3.3.
If new versions are broken, why are broken version posted untested? Is there anyone who can resync completly with 3.3.4.4?
I'm fully synced with 3.3.4.4 Could you try to delete all data except your wallet and resync? these are what I'm connected to now, after deleting everything.  [ { "addr" : "fzwpi2uqgauy225m.onion:24112", "services" : "00000001", "lastsend" : 1406327624, "lastrecv" : 1406327614, "conntime" : 1406327550, "version" : 70101, "subver" : "/Illuminatus:3.3.4.4/", "inbound" : false, "releasetime" : 0, "startingheight" : 9984, "banscore" : 1 }, { "addr" : "4mmbxrdk5xorxq4s.onion:24112", "services" : "00000001", "lastsend" : 1406327615, "lastrecv" : 1406327623, "conntime" : 1406327556, "version" : 70101, "subver" : "/Illuminatus:3.3.4.4/", "inbound" : false, "releasetime" : 0, "startingheight" : 9984, "banscore" : 1 }, { "addr" : "sv44mb2qcyxfwnbw.onion:24112", "services" : "00000001", "lastsend" : 1406327615, "lastrecv" : 1406327616, "conntime" : 1406327570, "version" : 70099, "subver" : "/Pyramid:3.3.3.3/", "inbound" : false, "releasetime" : 0, "startingheight" : 9002, "banscore" : 1 }, { "addr" : "6kickq6scfajdhot.onion:24112", "services" : "00000001", "lastsend" : 1406327679, "lastrecv" : 1406327680, "conntime" : 1406327679, "version" : 70099, "subver" : "/Pyramid:3.3.3.3/", "inbound" : false, "releasetime" : 0, "startingheight" : 9002, "banscore" : 1 } ] those two that are running 3.3.3.3 are messing with the network. if you compile yourself, edit protocol.h, change min proto version so its the same as the network protocol version. Then recompile. This will not allow older version to connect to you Thanks for suggestion, but if that would be the problem, then version 3.3.4.4 would not stuck, as there are peers with same version, my peers are not much different than yours 00:49:41 ? [ { "addr" : "4mmbxrdk5xorxq4s.onion:24112", "services" : "00000001", "lastsend" : 1406328129, "lastrecv" : 1406328433, "conntime" : 1406328129, "version" : 70101, "subver" : "/Illuminatus:3.3.4.4/", "inbound" : false, "releasetime" : 0, "startingheight" : 9984, "banscore" : 1 }, { "addr" : "lig5vcicm6hgjggx.onion:24112", "services" : "00000001", "lastsend" : 1406328133, "lastrecv" : 1406328136, "conntime" : 1406328132, "version" : 70099, "subver" : "/Pyramid:3.3.3.3/", "inbound" : false, "releasetime" : 0, "startingheight" : 9002, "banscore" : 1 }, { "addr" : "sr77eqw7cxkc34zy.onion:24112", "services" : "00000001", "lastsend" : 1406328540, "lastrecv" : 1406328173, "conntime" : 1406328137, "version" : 70099, "subver" : "/Pyramid:3.3.3.3/", "inbound" : false, "releasetime" : 0, "startingheight" : 6508, "banscore" : 1 }, { "addr" : "mcf4bxy7ksfl2jce.onion:24112", "services" : "00000001", "lastsend" : 1406328433, "lastrecv" : 1406328397, "conntime" : 1406328142, "version" : 70099, "subver" : "/Pyramid:3.3.3.3/", "inbound" : false, "releasetime" : 0, "startingheight" : 6508, "banscore" : 1 }, { "addr" : "ufoi7dt2lv575nlh.onion:24112", "services" : "00000001", "lastsend" : 1406328417, "lastrecv" : 1406328162, "conntime" : 1406328158, "version" : 70099, "subver" : "/Pyramid:3.3.3.3/", "inbound" : false, "releasetime" : 0, "startingheight" : 9002, "banscore" : 1 }, { "addr" : "qsjqt5tpcx7qsqfy.onion:24112", "services" : "00000001", "lastsend" : 1406328398, "lastrecv" : 1406328415, "conntime" : 1406328162, "version" : 70099, "subver" : "/Pyramid:3.3.3.3/", "inbound" : false, "releasetime" : 0, "startingheight" : 9002, "banscore" : 1 }, { "addr" : "66pgszhqlte4u5n3.onion:24112", "services" : "00000001", "lastsend" : 1406328454, "lastrecv" : 1406328537, "conntime" : 1406328452, "version" : 70101, "subver" : "/Illuminatus:3.3.4.4/", "inbound" : false, "releasetime" : 0, "startingheight" : 9027, "banscore" : 1 }, { "addr" : "ywedag3i2e3ocvel.onion:24112", "services" : "00000001", "lastsend" : 1406328477, "lastrecv" : 1406328479, "conntime" : 1406328477, "version" : 70101, "subver" : "/Illuminatus:3.3.4.4/", "inbound" : false, "releasetime" : 0, "startingheight" : 9027, "banscore" : 1 } ]
hmm. I am syncing fine, but I see that you're having problems. We'll work through this ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) You know why. I am resyncing with new compiled (70101), it took pretty long to pass from 9000 to 9003, but now it's pretty long not passing 9003. 01:08:22 ? getpeerinfo
01:08:22 ? [ { "addr" : "4mmbxrdk5xorxq4s.onion:24112", "services" : "00000001", "lastsend" : 1406329637, "lastrecv" : 1406329637, "conntime" : 1406329408, "version" : 70101, "subver" : "/Illuminatus:3.3.4.4/", "inbound" : false, "releasetime" : 0, "startingheight" : 9991, "banscore" : 1 }, { "addr" : "snp2rymorhfxibkn.onion:24112", "services" : "00000001", "lastsend" : 1406329520, "lastrecv" : 1406329519, "conntime" : 1406329418, "version" : 70101, "subver" : "/Illuminatus:3.3.4.4/", "inbound" : false, "releasetime" : 0, "startingheight" : 9991, "banscore" : 1 } ]
01:09:02 ? getmininginfo
01:09:02 ? { "blocks" : 9003, "currentblocksize" : 1000, "currentblocktx" : 0, "difficulty" : 125.80864323, "errors" : "", "generate" : false, "genproclimit" : -1, "hashespersec" : 0, "networkhashps" : 233937097, "pooledtx" : 0, "testnet" : false }
|
|
|
|
boki15
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 25, 2014, 11:20:15 PM |
|
Still no change, stucked at 9003: 01:18:49 ? { "blocks" : 9003, "currentblocksize" : 1000, "currentblocktx" : 0, "difficulty" : 125.80864323, "errors" : "", "generate" : false, "genproclimit" : -1, "hashespersec" : 0, "networkhashps" : 233937097, "pooledtx" : 0, "testnet" : false }
|
|
|
|
kernels10
Sr. Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 408
Merit: 250
ded
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 25, 2014, 11:21:25 PM |
|
try deleting just your peers.dat and restarting the wallet now
|
|
|
|
boki15
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 25, 2014, 11:24:21 PM |
|
try deleting just your peers.dat and restarting the wallet now
deleted, no change: 01:23:07 ? getmininginfo
01:23:07 ? { "blocks" : 9003, "currentblocksize" : 0, "currentblocktx" : 0, "difficulty" : 125.80864323, "errors" : "", "generate" : false, "genproclimit" : -1, "hashespersec" : 0, "networkhashps" : 233937097, "pooledtx" : 0, "testnet" : false }
01:23:30 ? getpeerinfo
01:23:30 ? [ { "addr" : "4mmbxrdk5xorxq4s.onion:24112", "services" : "00000001", "lastsend" : 1406330600, "lastrecv" : 1406330600, "conntime" : 1406330572, "version" : 70101, "subver" : "/Illuminatus:3.3.4.4/", "inbound" : false, "releasetime" : 0, "startingheight" : 10008, "banscore" : 1 }, { "addr" : "fzwpi2uqgauy225m.onion:24112", "services" : "00000001", "lastsend" : 1406330592, "lastrecv" : 1406330592, "conntime" : 1406330576, "version" : 70101, "subver" : "/Illuminatus:3.3.4.4/", "inbound" : false, "releasetime" : 0, "startingheight" : 10009, "banscore" : 1 } ]
|
|
|
|
kernels10
Sr. Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 408
Merit: 250
ded
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 25, 2014, 11:28:30 PM |
|
try deleting just your peers.dat and restarting the wallet now
deleted, no change: 01:23:07 ? getmininginfo
01:23:07 ? { "blocks" : 9003, "currentblocksize" : 0, "currentblocktx" : 0, "difficulty" : 125.80864323, "errors" : "", "generate" : false, "genproclimit" : -1, "hashespersec" : 0, "networkhashps" : 233937097, "pooledtx" : 0, "testnet" : false }
01:23:30 ? getpeerinfo
01:23:30 ? [ { "addr" : "4mmbxrdk5xorxq4s.onion:24112", "services" : "00000001", "lastsend" : 1406330600, "lastrecv" : 1406330600, "conntime" : 1406330572, "version" : 70101, "subver" : "/Illuminatus:3.3.4.4/", "inbound" : false, "releasetime" : 0, "startingheight" : 10008, "banscore" : 1 }, { "addr" : "fzwpi2uqgauy225m.onion:24112", "services" : "00000001", "lastsend" : 1406330592, "lastrecv" : 1406330592, "conntime" : 1406330576, "version" : 70101, "subver" : "/Illuminatus:3.3.4.4/", "inbound" : false, "releasetime" : 0, "startingheight" : 10009, "banscore" : 1 } ] hmm well both of your peers are at 10009 so maybe try resyncing again?
|
|
|
|
boki15
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 25, 2014, 11:46:27 PM |
|
try deleting just your peers.dat and restarting the wallet now
deleted, no change: .... hmm well both of your peers are at 10009 so maybe try resyncing again? I will give it now a last try but wallet or network is just broken. I am resyncing since couple of days, curious that dev is not answering. Is there anyone who can delete all data and resync again? No answers to that question until now. So whats broken, wallet net or chain? 01:23:07 ? getmininginfo
01:23:07 ? { "blocks" : 9003, "currentblocksize" : 0, "currentblocktx" : 0, "difficulty" : 125.80864323, "errors" : "", "generate" : false, "genproclimit" : -1, "hashespersec" : 0, "networkhashps" : 233937097, "pooledtx" : 0, "testnet" : false }
01:23:30 ? getpeerinfo
01:23:30 ? [ { "addr" : "4mmbxrdk5xorxq4s.onion:24112", "services" : "00000001", "lastsend" : 1406330600, "lastrecv" : 1406330600, "conntime" : 1406330572, "version" : 70101, "subver" : "/Illuminatus:3.3.4.4/", "inbound" : false, "releasetime" : 0, "startingheight" : 10008, "banscore" : 1 }, { "addr" : "fzwpi2uqgauy225m.onion:24112", "services" : "00000001", "lastsend" : 1406330592, "lastrecv" : 1406330592, "conntime" : 1406330576, "version" : 70101, "subver" : "/Illuminatus:3.3.4.4/", "inbound" : false, "releasetime" : 0, "startingheight" : 10009, "banscore" : 1 } ]
|
|
|
|
boki15
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 25, 2014, 11:59:46 PM |
|
Same ![Angry](https://bitcointalk.org/Smileys/default/angry.gif) ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FtkDxJeE.png&t=665&c=n5sF-HCd18E9Qg)
|
|
|
|
|