[ANN][LOC]UPDATE V1.4.5 OUT!! LOCO|Quark|PoW/PoS|HiPos|Masternodes|Tor[LOC][ANN] - page 42.

Amph

legendary

Activity: 3248

Merit: 1070

Quote from: zdeni82 on May 02, 2016, 06:34:23 AM

Quote from: Nightz on May 02, 2016, 06:28:16 AM

Going to look into forking DashPay source code and swapping algo's then adding PoS into it, I'm not saying I will do it but it is looking more than likely,

If I do I will try my hardest to keep the original chain so nobody has to start again or so we don't need any swaps to be done.

My wallet staking orphan blocks every block is not accepted by network. Should I shutdown my wallet until you fix the problem or what?

https://mega.nz/#!HphwSbJR!iOJbOmN5F3HrX-zQGlr3r-6C6mP9CxLgZPf9buwP5PY

3worlduser

sr. member

Activity: 306

Merit: 250

Quote from: Nightz on May 02, 2016, 06:31:25 AM

Quote from: 3worlduser on May 02, 2016, 05:53:23 AM

Quote from: Nightz on May 02, 2016, 04:58:13 AM

Quote from: 3worlduser on May 02, 2016, 04:42:02 AM

mmm and now my wallet travels trough time stake a block get confirmed even in de blockexplorer and then my wallet say I'm 2 hours behind
resync in 3 second and everything is back to my wallet before the stake with a nice stake block with 200 confirmation that the next minute becomes "in conflict" i wait five minutes and the stake begins again. now it goes for the 9 cycle doing this Undecided

Try this, It's my chain the correct one too Wink

https://mega.nz/#!HphwSbJR!iOJbOmN5F3HrX-zQGlr3r-6C6mP9CxLgZPf9buwP5PY

Contains
peers.dat
blk0001.dat
txleveldb folder

LoL why don't we did this in the update

Code:

connect=Nightz_wallet
listen=0

would have save a lot of problems, in fact I'm gona need to do that because the chain in the explorer is a little "weird"
I'll be playing with these thing now

I will add myself as a node on the next update to cut out half of this also mate Wink

connect=198.50.229.39 //is the explorer
listen=0
I'm gonna try a couple of days so far no problems, in the meanwhile what else we can do to support the coin?

zdeni82

hero member

Activity: 912

Merit: 505

Quote from: Nightz on May 02, 2016, 06:28:16 AM

Going to look into forking DashPay source code and swapping algo's then adding PoS into it, I'm not saying I will do it but it is looking more than likely,

If I do I will try my hardest to keep the original chain so nobody has to start again or so we don't need any swaps to be done.

My wallet staking orphan blocks every block is not accepted by network. Should I shutdown my wallet until you fix the problem or what?

Nightz

hero member

Activity: 1316

Merit: 504

I also think half the orphans are from those who have chose to be stubborn and stuck with v1.2 not a hard fix tho i will roll out a small update soon to adjust the noblks version upwards so those on v1.2 can no longer submit or mess with the v1.3 chain

Nightz

hero member

Activity: 1316

Merit: 504

Quote from: 3worlduser on May 02, 2016, 05:53:23 AM

Quote from: Nightz on May 02, 2016, 04:58:13 AM

Quote from: 3worlduser on May 02, 2016, 04:42:02 AM

mmm and now my wallet travels trough time stake a block get confirmed even in de blockexplorer and then my wallet say I'm 2 hours behind
resync in 3 second and everything is back to my wallet before the stake with a nice stake block with 200 confirmation that the next minute becomes "in conflict" i wait five minutes and the stake begins again. now it goes for the 9 cycle doing this Undecided

Try this, It's my chain the correct one too Wink

https://mega.nz/#!HphwSbJR!iOJbOmN5F3HrX-zQGlr3r-6C6mP9CxLgZPf9buwP5PY

Contains
peers.dat
blk0001.dat
txleveldb folder

LoL why don't we did this in the update

Code:

connect=Nightz_wallet
listen=0

would have save a lot of problems, in fact I'm gona need to do that because the chain in the explorer is a little "weird"
I'll be playing with these thing now

I will add myself as a node on the next update to cut out half of this also mate Wink

Nightz

hero member

Activity: 1316

Merit: 504

Going to look into forking DashPay source code and swapping algo's then adding PoS into it, I'm not saying I will do it but it is looking more than likely,

If I do I will try my hardest to keep the original chain so nobody has to start again or so we don't need any swaps to be done.

Nightz

hero member

Activity: 1316

Merit: 504

Quote from: bbr on May 02, 2016, 05:42:57 AM

I'm confused...which is now the correct chain?

When I look at block 39327 I get b4b5eb074c20b1b483d7620ad22519497027c32ca34c7639f4329f4ecf771f08 (which matches the explorer).

This is after downloading Nightz chain but when I look at previous posts they are stating that the correct hash for this block is f1b18e6d3369b17009295d73c3c64edd2c4f9c0b76c404993e8e8ba8561fc560

If you downloaded my chain mate it also reports back

b4b5eb074c20b1b483d7620ad22519497027c32ca34c7639f4329f4ecf771f08

12:24:17

getblockhash 39327

12:24:17

b4b5eb074c20b1b483d7620ad22519497027c32ca34c7639f4329f4ecf771f08

GREEDYJOHN

legendary

Activity: 1778

Merit: 1000

12:04:24

getinfo

12:04:24

{
"version" : "v1.3.0.0-Alpha",
"protocolversion" : 70002,
"walletversion" : 60000,
"balance" : xxxxxxxx,
"newmint" : 0.00000000,
"stake" : xxxxxxxx,
"blocks" : 39569,
"timeoffset" : 2,
"moneysupply" : 1850311.73066100,
"connections" : 22,
"proxy" : "",
"ip" : "0.0.0.0",
"difficulty" : {
"proof-of-work" : xxxxxxx
"proof-of-stake" : xxxxxxx
},
"testnet" : false,
"keypoololdest" : 1460750870,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00000000,
"unlocked_until" : 0,
"errors" : ""
}

3worlduser

sr. member

Activity: 306

Merit: 250

Quote from: Nightz on May 02, 2016, 04:58:13 AM

Quote from: 3worlduser on May 02, 2016, 04:42:02 AM

mmm and now my wallet travels trough time stake a block get confirmed even in de blockexplorer and then my wallet say I'm 2 hours behind
resync in 3 second and everything is back to my wallet before the stake with a nice stake block with 200 confirmation that the next minute becomes "in conflict" i wait five minutes and the stake begins again. now it goes for the 9 cycle doing this Undecided

Try this, It's my chain the correct one too Wink

https://mega.nz/#!HphwSbJR!iOJbOmN5F3HrX-zQGlr3r-6C6mP9CxLgZPf9buwP5PY

Contains
peers.dat
blk0001.dat
txleveldb folder

LoL why don't we did this in the update

Code:

connect=Nightz_wallet
listen=0

would have save a lot of problems, in fact I'm gona need to do that because the chain in the explorer is a little "weird"
I'll be playing with these thing now

bbr

sr. member

Activity: 290

Merit: 250

I'm confused...which is now the correct chain?

When I look at block 39327 I get b4b5eb074c20b1b483d7620ad22519497027c32ca34c7639f4329f4ecf771f08 (which matches the explorer).

This is after downloading Nightz chain but when I look at previous posts they are stating that the correct hash for this block is f1b18e6d3369b17009295d73c3c64edd2c4f9c0b76c404993e8e8ba8561fc560

novaexchange

member

Activity: 119

Merit: 11

I have temporarely increased confirmations needed to 800 on Novaexchange (just to be sure), this will be lowered down again to 10 once this has been sorted out.

However, I have not received even one orphan just yet. It seems like my client is very stable together with the explorers, i am keeping a sharp eye to events around loco at this point.

Nightz

hero member

Activity: 1316

Merit: 504

Quote from: ?? on ??

Quote from: Nightz on May 02, 2016, 04:59:31 AM

Mate if you wish to leave that is your choice but I can say with Certainty all will be sorted and bettered. Take that how you will

Thanks

already done, will delete completely in 30 min, sorry i'm certain you won't

LMAO do not under estimate me Wink

Will be a not very wise move mate Wink

Nightz

hero member

Activity: 1316

Merit: 504

Quote from: ?? on ??

Quote from: 3worlduser on May 02, 2016, 04:42:02 AM

mmm and now my wallet travels trough time stake a block get confirmed even in de blockexplorer and then my wallet say I'm 2 hours behind
resync in 3 second and everything is back to my wallet before the stake with a nice stake block with 200 confirmation that the next minute becomes "in conflict" i wait five minutes and the stake begins again. now it goes for the 9 cycle doing this Undecided

yeah, that's how it makes orphans, and other wallets the same way,
and it will make tons of them until chain gets completely overloaded.
it's all over again, nothing new.
perhaps side effect of limiting orphans mempool to 200 speeds up the process,
otherwise you would notice it much later

Mate if you wish to leave that is your choice but I can say with Certainty all will be sorted and bettered. Take that how you will

Thanks

Nightz

hero member

Activity: 1316

Merit: 504

Quote from: 3worlduser on May 02, 2016, 04:42:02 AM

mmm and now my wallet travels trough time stake a block get confirmed even in de blockexplorer and then my wallet say I'm 2 hours behind
resync in 3 second and everything is back to my wallet before the stake with a nice stake block with 200 confirmation that the next minute becomes "in conflict" i wait five minutes and the stake begins again. now it goes for the 9 cycle doing this Undecided

Try this, It's my chain the correct one too Wink

https://mega.nz/#!HphwSbJR!iOJbOmN5F3HrX-zQGlr3r-6C6mP9CxLgZPf9buwP5PY

Contains
peers.dat
blk0001.dat
txleveldb folder

Nightz

hero member

Activity: 1316

Merit: 504

Quote from: novaexchange on May 02, 2016, 04:08:29 AM

Quote from: ?? on ??

Quote from: novaexchange on May 02, 2016, 03:57:26 AM

A lot of people is still running old wallet,.

Code:

2016-05-02 08:56:17 ProcessMessage(version, 95 bytes) FAILED
2016-05-02 08:56:21 partner 101.175.180.227:34575 using obsolete version 61401; disconnecting
2016-05-02 08:56:21 ProcessMessage(version, 96 bytes) FAILED
2016-05-02 08:56:21 connect() to 46.226.186.70:34575 failed after select(): No route to host
2016-05-02 08:56:28 partner 176.193.213.25:52496 using obsolete version 61401; disconnecting
2016-05-02 08:56:28 ProcessMessage(version, 95 bytes) FAILED
2016-05-02 08:56:28 partner 75.85.20.118:34575 using obsolete version 61401; disconnecting
2016-05-02 08:56:28 ProcessMessage(version, 96 bytes) FAILED
2016-05-02 08:56:28 connect() to 37.59.18.108:34575 failed after select(): Connection refused
2016-05-02 08:56:31 partner 79.235.235.133:52173 using obsolete version 61401; disconnecting
2016-05-02 08:56:31 ProcessMessage(version, 95 bytes) FAILED

interesting, you have suprnova faulty on default port
37.59.18.108:34575 failed after select
and i have suprnova clean and healthy on another
37.59.18.108:41160

Those lines is not what is intresting, thats probably because his connection pool is full. Though those partner messages are the intresting ones, the log is full of those.

The partner messages are telling you that people are trying to connect etc to you but they are no longer able to due to them not updating as they should of Wink

pineapples

legendary

Activity: 1204

Merit: 1000

to your stations, man the pineapples!!!

I had a bunch of stakes, they were all lost in another fork being reorganised, seems I lost about 302 blocks in that particular lot.

Novaexchange, perhaps you should set confirmations to 500 Wink

3worlduser

sr. member

Activity: 306

Merit: 250

mmm and now my wallet travels trough time stake a block get confirmed even in de blockexplorer and then my wallet say I'm 2 hours behind
resync in 3 second and everything is back to my wallet before the stake with a nice stake block with 200 confirmation that the next minute becomes "in conflict" i wait five minutes and the stake begins again. now it goes for the 9 cycle doing this Undecided

novaexchange

member

Activity: 119

Merit: 11

Quote from: ?? on ??

Quote from: novaexchange on May 02, 2016, 03:57:26 AM

A lot of people is still running old wallet,.

Code:

2016-05-02 08:56:17 ProcessMessage(version, 95 bytes) FAILED
2016-05-02 08:56:21 partner 101.175.180.227:34575 using obsolete version 61401; disconnecting
2016-05-02 08:56:21 ProcessMessage(version, 96 bytes) FAILED
2016-05-02 08:56:21 connect() to 46.226.186.70:34575 failed after select(): No route to host
2016-05-02 08:56:28 partner 176.193.213.25:52496 using obsolete version 61401; disconnecting
2016-05-02 08:56:28 ProcessMessage(version, 95 bytes) FAILED
2016-05-02 08:56:28 partner 75.85.20.118:34575 using obsolete version 61401; disconnecting
2016-05-02 08:56:28 ProcessMessage(version, 96 bytes) FAILED
2016-05-02 08:56:28 connect() to 37.59.18.108:34575 failed after select(): Connection refused
2016-05-02 08:56:31 partner 79.235.235.133:52173 using obsolete version 61401; disconnecting
2016-05-02 08:56:31 ProcessMessage(version, 95 bytes) FAILED

interesting, you have suprnova faulty on default port
37.59.18.108:34575 failed after select
and i have suprnova clean and healthy on another
37.59.18.108:41160

Those lines is not what is intresting, thats probably because his connection pool is full. Though those partner messages are the intresting ones, the log is full of those.

novaexchange

member

Activity: 119

Merit: 11

A lot of people is still running old wallet,.

Code:

2016-05-02 08:56:17 ProcessMessage(version, 95 bytes) FAILED
2016-05-02 08:56:21 partner 101.175.180.227:34575 using obsolete version 61401; disconnecting
2016-05-02 08:56:21 ProcessMessage(version, 96 bytes) FAILED
2016-05-02 08:56:21 connect() to 46.226.186.70:34575 failed after select(): No route to host
2016-05-02 08:56:28 partner 176.193.213.25:52496 using obsolete version 61401; disconnecting
2016-05-02 08:56:28 ProcessMessage(version, 95 bytes) FAILED
2016-05-02 08:56:28 partner 75.85.20.118:34575 using obsolete version 61401; disconnecting
2016-05-02 08:56:28 ProcessMessage(version, 96 bytes) FAILED
2016-05-02 08:56:28 connect() to 37.59.18.108:34575 failed after select(): Connection refused
2016-05-02 08:56:31 partner 79.235.235.133:52173 using obsolete version 61401; disconnecting
2016-05-02 08:56:31 ProcessMessage(version, 95 bytes) FAILED

3worlduser

sr. member

Activity: 306

Merit: 250

Quote from: novaexchange on May 02, 2016, 03:51:43 AM

Quote from: 3worlduser on May 02, 2016, 03:50:04 AM

Code:

connect=node03.novaexchange.com:8057
listen=0

didn't worked for me but

Code:

connect=198.50.229.39
listen=0

did the trick, is the ip of the block explorer as it seem we both have the same chain because when I resync I used only the nodes on you page Wink

I have 122 connections to the wallet right now. ;-)

why I couln't connect Cry

, i want to have your blockchain I'll try again later

Topic: [ANN][LOC]UPDATE V1.4.5 OUT!! LOCO|Quark|PoW/PoS|HiPos|Masternodes|Tor[LOC][ANN] - page 42. (Read 88723 times)