i quit - page 49. | Bitcointalksearch.org

MinerFTW

sr. member

Activity: 462

Merit: 250

Quote from: xPooky on April 18, 2015, 10:35:00 AM

Quote from: MinerFTW on April 18, 2015, 10:33:15 AM

Quote from: xPooky on April 18, 2015, 10:01:33 AM

Quote from: MinerFTW on April 18, 2015, 09:53:00 AM

aquitasIJ:

When you get online. Please check your pm's
Now crawler gets forked doing nothing also.

My advise unless you have a lot of time to keep resyncing. Stop staking and buy up all cheap lodge until permanent fix is around.

P.s. i just resynced crawler node it was forked but back to checkpoint server.

i am on same chain also now

all 3 hardcoded seednodes are on different chain
can anyone post on which one is the checkpointing node

91.121.6.19 = checkpoint server

explorer is not same chain as node

gonna resync crawler node yet again then

xPooky

sr. member

Activity: 378

Merit: 250

Quote from: MinerFTW on April 18, 2015, 10:33:15 AM

Quote from: xPooky on April 18, 2015, 10:01:33 AM

Quote from: MinerFTW on April 18, 2015, 09:53:00 AM

aquitasIJ:

When you get online. Please check your pm's
Now crawler gets forked doing nothing also.

My advise unless you have a lot of time to keep resyncing. Stop staking and buy up all cheap lodge until permanent fix is around.

P.s. i just resynced crawler node it was forked but back to checkpoint server.

i am on same chain also now

all 3 hardcoded seednodes are on different chain
can anyone post on which one is the checkpointing node

91.121.6.19 = checkpoint server

explorer is not same chain as node

MinerFTW

sr. member

Activity: 462

Merit: 250

Quote from: xPooky on April 18, 2015, 10:01:33 AM

Quote from: MinerFTW on April 18, 2015, 09:53:00 AM

aquitasIJ:

When you get online. Please check your pm's
Now crawler gets forked doing nothing also.

My advise unless you have a lot of time to keep resyncing. Stop staking and buy up all cheap lodge until permanent fix is around.

P.s. i just resynced crawler node it was forked but back to checkpoint server.

i am on same chain also now

all 3 hardcoded seednodes are on different chain
can anyone post on which one is the checkpointing node

91.121.6.19 = checkpoint server

layer1gfx

legendary

Activity: 2128

Merit: 1109

Graphic Design & Translation - BTC accepted here!

Quote from: mellon on April 18, 2015, 10:27:31 AM

Quote from: layer1gfx on April 18, 2015, 10:20:38 AM

there is an issue for other PoS coins (also for asiacoin, peercoin and paycoin and most likely others) which now appeared for LDOGE as well:

Quote

Safe mode: WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers. (code -2)

their solution might also fix our problems:
https://bitcointalksearch.org/topic/m.11111115

Same issues have been fixed by blackcoin,Spreadcoin and FailCoin Developers Teams I'm can garantied that. That's why I'm PM MinerTFw two days ago about that and it's would be much more helpfully to look on their source. At first on FailCoin because they are used script algo too.

ok i see. i slightly edited my post to make it more clear what the issue is.

mellon

legendary

Activity: 1014

Merit: 1002

Quel marth Melloneamin

Quote from: layer1gfx on April 18, 2015, 10:20:38 AM

there is an issue for other PoS coins (also for asiacoin, peercoin and paycoin and most likely others) which now appeared for LDOGE as well:

Quote

Safe mode: WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers. (code -2)

their solution might also be fixing our problems:
https://bitcointalksearch.org/topic/m.11111115

Same issues have been fixed by blackcoin,Spreadcoin and FailCoin Developers Teams I'm can garantied that. That's why I'm PM MinerTFw two days ago about that and it's would be much more helpfully to look on their source. At first on FailCoin because they are used script algo too.

mellon

legendary

Activity: 1014

Merit: 1002

Quel marth Melloneamin

Quote from: not.you on April 18, 2015, 10:06:04 AM

Quote from: heavensopen on April 18, 2015, 09:47:22 AM

Quote from: not.you on April 18, 2015, 08:26:21 AM

Does anyone know what this is? That is not my wallet address (all of my wallets have labels like the one that says wallet3) but it appears in my history like a block I mined. I have seen a few of these, each with a different address, some of them happened when I was forked so they disappeared after I resynced but this one made it into the main chain.

txid: 4db08faabc35c2c94f8c45b5ef2afc35c71e060d83dbfcc32e2e42fe44d64679

go to console and hit listaddressgroupings
this will tell you all the addresses currently into your wallet and their balance
it may be one of your addresses that receive change

I do see it listed there along with a number of others that I do not recognize. If these are all mine where did they come from and why are they not listed under the receive tab where the addresses I generated are listed?

because your wallet.dat have a informations from right and forked chain now. But database not have that info that's why you are now synchronization successfully at start because you wallet.dat find same with fixed database lns ends in some checkpoint but to next checkpoint you are again come back to your own fork and start download a txid from your wallet.dat. Check your debug log now for more clear info about your address. And same situation would be take a place around. Fix that by the way like that want to do dev and MinerTWXnot impossible now. Because they are already twice now fixed a forked chains variant and now database have a lot of issues same type like you see. You understand what I'm say now?

layer1gfx

legendary

Activity: 2128

Merit: 1109

Graphic Design & Translation - BTC accepted here!

there is an issue with the checkpoint being too old for other PoS coins (also for asiacoin, peercoin and paycoin and most likely others)
i got now a warning message that looks similar (not exactly the same) but saying things about the checkpoint as well:

Quote

Safe mode: WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers. (code -2)

their solution might also be fixing our problems:
https://bitcointalksearch.org/topic/m.11111115

not.you

legendary

Activity: 1726

Merit: 1018

Quote from: heavensopen on April 18, 2015, 09:47:22 AM

Quote from: not.you on April 18, 2015, 08:26:21 AM

Does anyone know what this is? That is not my wallet address (all of my wallets have labels like the one that says wallet3) but it appears in my history like a block I mined. I have seen a few of these, each with a different address, some of them happened when I was forked so they disappeared after I resynced but this one made it into the main chain.

txid: 4db08faabc35c2c94f8c45b5ef2afc35c71e060d83dbfcc32e2e42fe44d64679

go to console and hit listaddressgroupings
this will tell you all the addresses currently into your wallet and their balance
it may be one of your addresses that receive change

I do see it listed there along with a number of others that I do not recognize. If these are all mine where did they come from and why are they not listed under the receive tab where the addresses I generated are listed?

xPooky

sr. member

Activity: 378

Merit: 250

Quote from: MinerFTW on April 18, 2015, 09:53:00 AM

aquitasIJ:

When you get online. Please check your pm's
Now crawler gets forked doing nothing also.

My advise unless you have a lot of time to keep resyncing. Stop staking and buy up all cheap lodge until permanent fix is around.

P.s. i just resynced crawler node it was forked but back to checkpoint server.

i am on same chain also now

all 3 hardcoded seednodes are on different chain
can anyone post on which one is the checkpointing node

MinerFTW

sr. member

Activity: 462

Merit: 250

aquitasIJ:

When you get online. Please check your pm's
Now crawler gets forked doing nothing also.

My advise unless you have a lot of time to keep resyncing. Stop staking and buy up all cheap lodge until permanent fix is around.

P.s. i just resynced crawler node it was forked but back to checkpoint server.

heavensopen

sr. member

Activity: 426

Merit: 250

Quote from: not.you on April 18, 2015, 08:26:21 AM

Does anyone know what this is? That is not my wallet address (all of my wallets have labels like the one that says wallet3) but it appears in my history like a block I mined. I have seen a few of these, each with a different address, some of them happened when I was forked so they disappeared after I resynced but this one made it into the main chain.

txid: 4db08faabc35c2c94f8c45b5ef2afc35c71e060d83dbfcc32e2e42fe44d64679

go to console and hit listaddressgroupings
this will tell you all the addresses currently into your wallet and their balance
it may be one of your addresses that receive change

mellon

legendary

Activity: 1014

Merit: 1002

Quel marth Melloneamin

Quote from: xPooky on April 18, 2015, 09:07:17 AM

[
{
"addr" : "91.121.6.19:17014",
"addrlocal" : "*",
"services" : "00000001",
"lastsend" : 1429365963,
"lastrecv" : 1429365963,
"bytessent" : 2509,
"bytesrecv" : 21999,
"conntime" : 1429365951,
"pingtime" : 0.10383900,
"version" : 60015,
"subver" : "/Satoshi:1.0.0.1/",
"inbound" : false,
"startingheight" : 45640,
"banscore" : 0,
"syncnode" : true
}
]
one of the nodes that are listed in op is way in front of explorer
block 45640
and my wallet connects to it even if i remove it from conf file

In that case that seed is a basic and written in source.

mellon

legendary

Activity: 1014

Merit: 1002

Quel marth Melloneamin

Quote from: litedoge on April 18, 2015, 02:38:02 AM

Quote

are you sure it is a good idea to put listen=1 right now?

Not sure - but its working better now - much more network weight showing ...

as long as listen is below nodes

... but I think I will wait for permanent fix now ...

It's working better because it's a right scheme how must work p2p network and stand decentralized with much more better security and stability. When your turn "listen" to value 1,your are start a new server-client adress(node-seed).

xPooky

sr. member

Activity: 378

Merit: 250

[
{
"addr" : "91.121.6.19:17014",
"addrlocal" : "*",
"services" : "00000001",
"lastsend" : 1429365963,
"lastrecv" : 1429365963,
"bytessent" : 2509,
"bytesrecv" : 21999,
"conntime" : 1429365951,
"pingtime" : 0.10383900,
"version" : 60015,
"subver" : "/Satoshi:1.0.0.1/",
"inbound" : false,
"startingheight" : 45640,
"banscore" : 0,
"syncnode" : true
}
]
one of the nodes that are listed in op is way in front of explorer
block 45640
and my wallet connects to it even if i remove it from conf file

mellon

legendary

Activity: 1014

Merit: 1002

Quel marth Melloneamin

not.you

legendary

Activity: 1726

Merit: 1018

Quote from: xPooky on April 18, 2015, 08:31:33 AM

whenever i try to stake this gets forked :\
So i turn off wallet now

I saw same thing today but worse now is that I am not staking, I am only syncing with the nodes given in this thread recently (one doesn't work though as mentioned above), and I am apparently on a different chain than the crawler. Possibly the crawler is frozen. It is on 45608 right now but the node I am connected to has gone past that.

EDIT:
C:\Users\Administrator>nslookup 91.121.6.19
Server: dc1.mydomain.com
Address: 192.168.2.5

Name: ns328125.ip-91-121-6.eu
Address: 91.121.6.19

C:\Users\Administrator>netstat

Active Connections

Proto Local Address Foreign Address State
TCP 192.168.2.236:3389 192.168.1.114:49421 ESTABLISHED
TCP 192.168.2.236:58944 ns328125:17014 ESTABLISHED
TCP 192.168.2.236:58998 sh01:http LAST_ACK

So looks like the node that works is 91.121.6.19

Also looks like this node is not on same chain as the block crawler Sad

xPooky

sr. member

Activity: 378

Merit: 250

whenever i try to stake this gets forked :\
So i turn off wallet now

not.you

legendary

Activity: 1726

Merit: 1018

Does anyone know what this is? That is not my wallet address (all of my wallets have labels like the one that says wallet3) but it appears in my history like a block I mined. I have seen a few of these, each with a different address, some of them happened when I was forked so they disappeared after I resynced but this one made it into the main chain.

txid: 4db08faabc35c2c94f8c45b5ef2afc35c71e060d83dbfcc32e2e42fe44d64679

luongdk

full member

Activity: 686

Merit: 102

Quote from: not.you on April 18, 2015, 08:05:25 AM

The new block crawler is only showing 3 connections. My wallet was frozen so I have attempted to resync to the 2 nodes. It says I have 2 connections but it is not syncing. Says I am synchronizing. Says I am 21 hours behind. But it doesn't appear to be downloading any blocks.

EDIT: I had the wrong conf file in the folder. Using the correct one I too am only connecting to a single node as xPooky mentioned. But at least I was able to resync now and the block height agrees with the crawler. Not sure why the crawler reports so few connections though.

Block Crawler is using CheckPoint Server node, itself node and my node.

My node

Quote

addnode=183.91.4.3

not.you

legendary

Activity: 1726

Merit: 1018

The new block crawler is only showing 3 connections. My wallet was frozen so I have attempted to resync to the 2 nodes. It says I have 2 connections but it is not syncing. Says I am synchronizing. Says I am 21 hours behind. But it doesn't appear to be downloading any blocks.

EDIT: I had the wrong conf file in the folder. Using the correct one I too am only connecting to a single node as xPooky mentioned. But at least I was able to resync now and the block height agrees with the crawler. Not sure why the crawler reports so few connections though.

Topic: i quit - page 49. (Read 142570 times)