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

Nightz

hero member

Activity: 1302

Merit: 504

Quote from: jc12345 on May 01, 2016, 06:07:12 AM

Quote from: novaexchange on May 01, 2016, 06:00:21 AM

Hi,

I am putting the Loco wallet into maintenance mode until the new source is available for download.

@ax66
I did a full resync, salvagewallet and reindex when the fork took place, any transactions received or sent during that time has been invalidated. The fork was unintended by the dev, but I cannot magically make coins that does not exist. If this would been an issue with the Exchange I would have paid up from my own pocket to replace those coins. Now when an issue with a fork of the blockchain the Exchange cannot be held responsible since it is out of my control.

@Nightz
How do you suggest we help those people that have lost coins due to the unintended fork?

Have you tried restoring a backup wallet.dat from when you created it initially or from an earlier backup and let the db be populated from the clean chain? perhaps the coins will "show up" since the correct chain has no knowledge of any transactions during the fork time. Alternatively a dump of the private key and import to a new wallet will achieve the same result if you do not have an early backup.

@NovaExchange what JC12345 said could work potentially Can you please give it a try ?

Thanks

jc12345

legendary

Activity: 1638

Merit: 1013

Quote from: novaexchange on May 01, 2016, 06:00:21 AM

Hi,

I am putting the Loco wallet into maintenance mode until the new source is available for download.

@ax66
I did a full resync, salvagewallet and reindex when the fork took place, any transactions received or sent during that time has been invalidated. The fork was unintended by the dev, but I cannot magically make coins that does not exist. If this would been an issue with the Exchange I would have paid up from my own pocket to replace those coins. Now when an issue with a fork of the blockchain the Exchange cannot be held responsible since it is out of my control.

@Nightz
How do you suggest we help those people that have lost coins due to the unintended fork?

Have you tried restoring a backup wallet.dat from when you created it initially or from an earlier backup and let the db be populated from the clean chain? perhaps the coins will "show up" since the correct chain has no knowledge of any transactions during the fork time. Alternatively a dump of the private key and import to a new wallet will achieve the same result if you do not have an early backup.

You can test this first on a QA machine.

Nightz

hero member

Activity: 1302

Merit: 504

Quote from: novaexchange on May 01, 2016, 06:00:21 AM

@Nightz
How do you suggest we help those people that have lost coins due to the unintended fork?

If we cannot get the said coins back As Long as they are not huge amounts I will reimburse people provided they provide all proof they have not got the coins back ( Maybe lengthy task tho)

Nightz

hero member

Activity: 1302

Merit: 504

Quote from: jc12345 on May 01, 2016, 05:53:35 AM

Quote from: Nightz on May 01, 2016, 04:59:41 AM

Go2 V1.3 Will be released @ 6PM GMT 1st May 2016 with the Following Changes:

The default maximum orphans to be kept in memory is now 200 instead of 750.

More Checkpoints added.

The networks protocol version has been changed, this will ensure all on Loco's Network are on the same client with the same chain.

I'm going to be working on a change for masternodes to lower the amount by half so instead of 30k it will be 15k once complete too.

Client timeout interval for pinging has been lowerd from 20 minutes to 10 minutes.

Maximum Stake Age has been added and is set to 31 days now.

Great stuff. When will masternodes be active and also when will the amount be lowered to 15k?

Masternodes should be active now mate for a rate of 30k at the moment, I do not presume changing the masternodes structure to 15k rather than 30k will be too hard/time consuming Wink

but more will come of this once I have released this update.

novaexchange

member

Activity: 119

Merit: 11

Hi,

I am putting the Loco wallet into maintenance mode until the new source is available for download.

@ax66
I did a full resync, salvagewallet and reindex when the fork took place, any transactions received or sent during that time has been invalidated. The fork was unintended by the dev, but I cannot magically make coins that does not exist. If this would been an issue with the Exchange I would have paid up from my own pocket to replace those coins. Now when an issue with a fork of the blockchain the Exchange cannot be held responsible since it is out of my control.

@Nightz
How do you suggest we help those people that have lost coins due to the unintended fork?

jc12345

legendary

Activity: 1638

Merit: 1013

Quote from: Nightz on May 01, 2016, 04:59:41 AM

Go2 V1.3 Will be released @ 6PM GMT 1st May 2016 with the Following Changes:

The default maximum orphans to be kept in memory is now 200 instead of 750.

More Checkpoints added.

The networks protocol version has been changed, this will ensure all on Loco's Network are on the same client with the same chain.

I'm going to be working on a change for masternodes to lower the amount by half so instead of 30k it will be 15k once complete too.

Client timeout interval for pinging has been lowerd from 20 minutes to 10 minutes.

Maximum Stake Age has been added and is set to 31 days now.

Great stuff. When will masternodes be active and also when will the amount be lowered to 15k?

jc12345

legendary

Activity: 1638

Merit: 1013

Quote from: ?? on ??

Quote from: jc12345 on April 30, 2016, 11:29:53 PM

Quote from: Selsonblue on April 30, 2016, 04:58:38 PM

Sooo thanks to everyone that helped out with this. All my coins recovered... yes 16k loco back home..

First, resync wallet. and import the wallet.dat

Second, did the resendtx command in console which pushed through the transaction fee and another lost tx.

Third, issue repairwallet in console and got this output ---
{
"mismatched spent coins" : 85,
"amount affected by repair" : 14337.85425458
}

Then coins showed up about a minute later. --

Thanks again everyone! And good luck to the other fellow in here with the recovery

It is great to know that this worked for you. Will it work if the source was Novaexchange, or will they have to do this excercise on their side? My tx with the ! was a withdraw from Nova and they say there is nothing they can do about it and the coins are lost and that I must contact the dev.

I will try your procedure although the tx id is not on the new chain.

your issue is symmetrical to this:
https://bitcointalksearch.org/topic/m.14700400

their wallet invalidated incoming tx's - your wallet invalidated their transfer to you,
they ask to resend deposits - you ask them to resend you withdrawal.
i don't quite understand why they refuse,
but exchanges kitchen is a bit more delicate than personal

I always make a backup of my wallets immediately after creating them before sending any coins there. I wiped my .loco folder except the .conf file and resynced from scratch. I then put in the wallet.dat from my backup and now my wallet is clean from all orphans and conflicts. The issue now is that I did a withdrawal from Novaexchange durign the fork time that is not in my wallet. The issue is therefore on the Nova side.

@Novaexchange, can you please do a wallet recovery/rescan procedure on your side so that you will have a clean wallet? I am sure that if you do this, the coins withdrawn from your wallet during the fork time will show up on your side again and then you can resend the tx. Then in future, lock your deposits and withdrawals before a major update and only re-open after everything is ok on the new wallet.

Nightz

hero member

Activity: 1302

Merit: 504

Go2 V1.3 Will be released @ 6PM GMT 1st May 2016 with the Following Changes:

The default maximum orphans to be kept in memory is now 200 instead of 750.

More Checkpoints added.

The networks protocol version has been changed, this will ensure all on Loco's Network are on the same client with the same chain.

I'm going to be working on a change for masternodes to lower the amount by half so instead of 30k it will be 15k once complete too.

Client timeout interval for pinging has been lowerd from 20 minutes to 10 minutes.

Maximum Stake Age has been added and is set to 31 days now.

Nightz

hero member

Activity: 1302

Merit: 504

Quote from: USScrypto on May 01, 2016, 04:37:25 AM

6 pm on what timezone?

That would be "GMT"

USScrypto

hero member

Activity: 602

Merit: 500

6 pm on what timezone?

Nightz

hero member

Activity: 1302

Merit: 504

Update Go2 v1.3 is ready, I will release the new wallets and github at 6pm today so can all pools, block explorers and exchanges please stop your services by 6pm tonight ready to update.

Enticed87

sr. member

Activity: 413

Merit: 250

So where is this coin at right now ? Is there a Hardfork or Mandatory update before a certain block required ?

I remember I only mined a little bit of these since it was the Quark Algorithm but haven't opened my wallet ever since.

3worlduser

sr. member

Activity: 306

Merit: 250

Quote from: jc12345 on April 30, 2016, 11:29:53 PM

Quote from: Selsonblue on April 30, 2016, 04:58:38 PM

Sooo thanks to everyone that helped out with this. All my coins recovered... yes 16k loco back home..

First, resync wallet. and import the wallet.dat

Second, did the resendtx command in console which pushed through the transaction fee and another lost tx.

Third, issue repairwallet in console and got this output ---
{
"mismatched spent coins" : 85,
"amount affected by repair" : 14337.85425458
}

Then coins showed up about a minute later. --

Thanks again everyone! And good luck to the other fellow in here with the recovery

It is great to know that this worked for you. Will it work if the source was Novaexchange, or will they have to do this excercise on their side? My tx with the ! was a withdraw from Nova and they say there is nothing they can do about it and the coins are lost and that I must contact the dev.

I will try your procedure although the tx id is not on the new chain.

I have a copy of the old block chain before I updated teh daemon on the block.explorer, I don't if it can help you in something but if you need it just PM me

jc12345

legendary

Activity: 1638

Merit: 1013

Quote from: Selsonblue on April 30, 2016, 04:58:38 PM

Sooo thanks to everyone that helped out with this. All my coins recovered... yes 16k loco back home..

First, resync wallet. and import the wallet.dat

Second, did the resendtx command in console which pushed through the transaction fee and another lost tx.

Third, issue repairwallet in console and got this output ---
{
"mismatched spent coins" : 85,
"amount affected by repair" : 14337.85425458
}

Then coins showed up about a minute later. --

Thanks again everyone! And good luck to the other fellow in here with the recovery

It is great to know that this worked for you. Will it work if the source was Novaexchange, or will they have to do this excercise on their side? My tx with the ! was a withdraw from Nova and they say there is nothing they can do about it and the coins are lost and that I must contact the dev.

I will try your procedure although the tx id is not on the new chain.

Selsonblue

hero member

Activity: 661

Merit: 500

In addition, conflicted coins will continue to stake. Good to know

GREEDYJOHN

legendary

Activity: 1778

Merit: 1000

23:03:59

getblockhash 35839

23:03:59

6ee3936e9c572f147599015b64292f9eb0fb3597d6fd64292e23a2ddea2a5aef

Please make the update, so that the changes take place at a BLOCK that is at least 24 hours away. Many of us work weekends, but keep our computers on to stake these coins

Selsonblue

hero member

Activity: 661

Merit: 500

Sooo thanks to everyone that helped out with this. All my coins recovered... yes 16k loco back home..

First, resync wallet. and import the wallet.dat

Second, did the resendtx command in console which pushed through the transaction fee and another lost tx.

Third, issue repairwallet in console and got this output ---
{
"mismatched spent coins" : 85,
"amount affected by repair" : 14337.85425458
}

Then coins showed up about a minute later. --

Thanks again everyone! And good luck to the other fellow in here with the recovery

Selsonblue

hero member

Activity: 661

Merit: 500

After resync, resendtx command in console immediately prompted 2 transactions to resend and they went through fine.. but the one that has the ! next to it and is conflicted is still MIA

Selsonblue

hero member

Activity: 661

Merit: 500

Quote from: jc12345 on April 30, 2016, 03:43:28 PM

I got a deposit tx in my wallet with an exclamation mark next to it and it says "conflict". the deposit was done on the forked chain. The tx id does not appear in the block explorer and the new chain after the fork and the new chain does not contain any trace of the tx. How do I recover those coins as they were sent to my wallet but now they are gone.

I would also like to request that any mandatory updates get co-ordinated with the exchange/s so the the exchange can freeze their withdrawls and deposits until the exchange is also on the new wallet. this is standard practice.

I resynced my entire wallet. Imported the old wallet.dat. and the transaction in question which was previously confirmed is not showing up as conflicted....

On another note, some random coins showed up in my wallet.... How can I recover the conflicted coins now?

Nightz

hero member

Activity: 1302

Merit: 504

Quote from: chivaki on April 30, 2016, 03:44:03 PM

What is the correct fork ?

If Block 35839 reports this Then you are on the correct chain

21:52:12

getblockhash 35839

21:52:12

6ee3936e9c572f147599015b64292f9eb0fb3597d6fd64292e23a2ddea2a5aef

21:52:19

getblock 6ee3936e9c572f147599015b64292f9eb0fb3597d6fd64292e23a2ddea2a5aef

21:52:19

{
"hash" : "6ee3936e9c572f147599015b64292f9eb0fb3597d6fd64292e23a2ddea2a5aef",
"confirmations" : 1,
"size" : 213,
"height" : 35839,
"version" : 7,
"merkleroot" : "8985bf4f623ff0dfce69815edd0e64eec0b910a1c57aec23e84d98c14a0859e7",
"mint" : 5.00000000,
"time" : 1462049473,
"nonce" : 3429161778,
"bits" : "1c76eef4",
"difficulty" : 2.15243212,
"blocktrust" : "22707f1b5",
"chaintrust" : "31fa5a548b153131",
"previousblockhash" : "a4758218a7224e2590b4112173b46742029cdad9135096a0c1f9ed8c849301c1",
"flags" : "proof-of-work",
"proofhash" : "0000000027eb75807d1566d39d9b3ddfe27a7f46e208c729d67a36c67a063077",
"entropybit" : 1,
"modifier" : "297de4d42ad32778",
"modifierv2" : "96399b0afb29042578c8e353997f89579edaa3359ab5daf7a118d7bacf156140",
"tx" : [
"8985bf4f623ff0dfce69815edd0e64eec0b910a1c57aec23e84d98c14a0859e7"
]
}

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