[ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN - page 382.

berron

hero member

Activity: 727

Merit: 501

Quote from: ?? on ??

getblockhash 260209

c1a37179151fd5f44d08d06805e4d4087341eacdf5aaaef2553c69fca29c21d4

this is what I get... anyone could confirm please?

I'm updating again, I would tell you as soon as synced again with the new list of nodes of the config file.

BitcoinFX

legendary

Activity: 2646

Merit: 1722

https://youtu.be/DsAVx0u9Cw4 ... Dr. WHO < KLF

Quote from: pjcltd on August 10, 2016, 06:03:07 AM

Quote from: BitcoinFX on August 10, 2016, 05:57:53 AM

Quote from: pjcltd on August 10, 2016, 05:36:37 AM

ok now im getting this in the wallet

11:35:20

getinfo

11:35:20

CDB : Error -30974, can't open database (code -1)

and then it crashed again

I will resyinc it all again

thanks
Paul

Confirming that I've also seen this on a couple of masternode (linux) instances, for the devs. reference.

It is proceeded by:

Quote

error: {"code":-1,"message":"ReserveKeyFromKeyPool() : read failed"}

error: {"code":-1,"message":"CWallet::GenerateNewKey() : AddKey failed"}

error: {"code":-1,"message":"CDB : Error -30974, can't open database "}

@pjcltd Did you run the Darknet-Qt-Linux64-Wallet-v2.0.1.0.zip or compile from source ?

i did yes

also it looks like the blockchain is stuck

./darknet-cli getinfo
{
   "version" : 2000100,
   "protocolversion" : 70300,
   "walletversion" : 61000,
   "balance" : 0.00000000,
   "obfuscation_balance" : 0.00000000,
   "blocks" : 259200,
   "timeoffset" : -1,
   "connections" : 7,
   "proxy" : "",
   "difficulty" : 48.59999131,
   "testnet" : false,
   "keypoololdest" : 1457354235,
   "keypoolsize" : 1001,
   "paytxfee" : 0.00000000,
   "relayfee" : 0.00010000,
   "staking status" : "Staking Not Active",
   "errors" : ""
}

In my experience of this issue, I had to clear all of ~/.darknet , including darknet.conf and masternode.conf - effectively ran a fresh wallet - synced with the correct blockchain height and then imported the private key from the 'old' (original) wallet .dat / backup.

Of course, the devs. may review this and provide you with an alternative solution. I have not located the exact probable cause yet, although I have a good idea that it was to do with running v2.0.0.0 with the wallet for that instance being on a fork, which has effectively 'borked' it.

berron

hero member

Activity: 727

Merit: 501

Quote from: ?? on ??

Quote from: werwortmann on August 10, 2016, 05:10:22 AM

Quote from: ?? on ??

Hi all,

Could you please check this block to be sure we are all on the same chain?

getblockhash 260200

c6e2324f5baf1b8dfcc5feee9d2eb6db3481136da78b287b1b2c44ff68932e12

I hope it's the one Cool

Mine also has that hash,
so looks good

Thank you! great news Cool

Quote from: jakiman on August 10, 2016, 04:29:29 AM

My controller wallet is on the right chain and now starting up my MNs also. Grin

I remember you had a transaction issue, did you get it?

Quote from: mikegi on August 10, 2016, 05:23:19 AM

Quote from: mxnsch on August 10, 2016, 04:03:11 AM

Nice catch! Looking at the changes, i will leave my masternodes running with the one additional commit:
https://github.com/Darknet-Crypto/Darknet/commit/db34f50e5fb1f8eb8dc31349d08809457220102c

I have the older one, looks like the changes are necessary as there are a lot of warnings and errors in the logs after the PoW blocks end.

Compiling.... Done ...

Let's see...

Code:

$ darknet-cli getblockhash 259880
f6bf9eae07bbba776309c374ef73b83bf633853b7026ceeff17e20ccd0774098

Yay!!!

I am up to this block now... does anyone want to confirm I am on the right chain?

darknet-cli getblockhash 260209
c1a37179151fd5f44d08d06805e4d4087341eacdf5aaaef2553c69fca29c21d4

Thought scripting everything would be overkill for the small amount of masternodes I have ( < 10 ) , but now considering it...
At least I have clusterssh set up now...

Time to set up masternodes...

I have the same.

Quote from: werwortmann on August 10, 2016, 05:22:53 AM

How can we get rid of orphan transactions in the gui?
They are always ontop, so I can't see my recent transactions

interested too... I got a stacking block and it replaced an old orphaned one...

Anyone more can take a look at this:

Quote

getblockhash 259880
f6bf9eae07bbba776309c374ef73b83bf633853b7026ceeff17e20ccd0774098

like them
but

Quote

getblockhash 260209
f47f44ca42bf37918cce19e638ba3d7bbf10f6da24510b2eebf17c34c3700a27

Instead of their value.
I'm forked???

pjcltd

legendary

Activity: 1778

Merit: 1003

NodeMasters

Quote from: jakiman on August 10, 2016, 06:05:23 AM

I resynced every single one of my MN's from scratch. So far, haven't had any stuck block issues.

All my masternodes have been resynced from scratch

thanks
Paul

jakiman

legendary

Activity: 1638

Merit: 1011

jakiman is back!

I resynced every single one of my MN's from scratch. So far, haven't had any stuck block issues.

BitcoinFX

legendary

Activity: 2646

Merit: 1722

https://youtu.be/DsAVx0u9Cw4 ... Dr. WHO < KLF

The majority of Tor addnode=.onion's appear to have gone onto a stale fork, after updating to v2.0.1.0.

However, the following Tor addnode=.onion's would appear to be on the correct chain now:

addnode=dnetxef3rmouy5qo.onion:989
addnode=dnetxcvx4iqeunnk.onion:989
addnode=dnetxn4m5kfh4xhr.onion:989
addnode=dnetxu5edp35e4rm.onion:989
addnode=gtlqzb5zbws5di7g.onion:989
addnode=f7j2m26rptm5f7af.onion:989
addnode=dnetzj6l4cvo2fxy.onion:989
addnode=s3v3n7xhqafg6sb7.onion:989

pjcltd

legendary

Activity: 1778

Merit: 1003

NodeMasters

Quote from: BitcoinFX on August 10, 2016, 05:57:53 AM

Quote from: pjcltd on August 10, 2016, 05:36:37 AM

ok now im getting this in the wallet

11:35:20

getinfo

11:35:20

CDB : Error -30974, can't open database (code -1)

and then it crashed again

I will resyinc it all again

thanks
Paul

Confirming that I've also seen this on a couple of masternode (linux) instances, for the devs. reference.

It is proceeded by:

Quote

error: {"code":-1,"message":"ReserveKeyFromKeyPool() : read failed"}

error: {"code":-1,"message":"CWallet::GenerateNewKey() : AddKey failed"}

error: {"code":-1,"message":"CDB : Error -30974, can't open database "}

@pjcltd Did you run the Darknet-Qt-Linux64-Wallet-v2.0.1.0.zip or compile from source ?

i did yes

also it looks like the blockchain is stuck

./darknet-cli getinfo
{
"version" : 2000100,
"protocolversion" : 70300,
"walletversion" : 61000,
"balance" : 0.00000000,
"obfuscation_balance" : 0.00000000,
"blocks" : 259200,
"timeoffset" : -1,
"connections" : 7,
"proxy" : "",
"difficulty" : 48.59999131,
"testnet" : false,
"keypoololdest" : 1457354235,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"relayfee" : 0.00010000,
"staking status" : "Staking Not Active",
"errors" : ""
}

BitcoinFX

legendary

Activity: 2646

Merit: 1722

https://youtu.be/DsAVx0u9Cw4 ... Dr. WHO < KLF

Quote from: pjcltd on August 10, 2016, 05:36:37 AM

ok now im getting this in the wallet

11:35:20

getinfo

11:35:20

CDB : Error -30974, can't open database (code -1)

and then it crashed again

I will resyinc it all again

thanks
Paul

Confirming that I've also seen this on a couple of masternode (linux) instances, for the devs. reference.

It is proceeded by:

Quote

error: {"code":-1,"message":"ReserveKeyFromKeyPool() : read failed"}

error: {"code":-1,"message":"CWallet::GenerateNewKey() : AddKey failed"}

error: {"code":-1,"message":"CDB : Error -30974, can't open database "}

@pjcltd Did you run the Darknet-Qt-Linux64-Wallet-v2.0.1.0.zip or compile from source ?

pjcltd

legendary

Activity: 1778

Merit: 1003

NodeMasters

ok now im getting this in the wallet

11:35:20

getinfo

11:35:20

CDB : Error -30974, can't open database (code -1)

and then it crashed again

I will resyinc it all again

thanks
Paul

jakiman

legendary

Activity: 1638

Merit: 1011

jakiman is back!

Quote from: ?? on ??

I remember you had a transaction issue, did you get it?

Yes, the withdrawal from Bittrex after the fork is showing up and confirmed. I assume devs did some magic. Cool

shimlbit

legendary

Activity: 1302

Merit: 1001

i updated to the latest version but i still stuck at 259200!

i did everything...
just the posted addnodes...deleted everything...compiled it new..the blockchain file also tested nothing is working...

im on ubuntu 14.4

everything worked fine until 259200 now nothing working anymore...

jakiman

legendary

Activity: 1638

Merit: 1011

jakiman is back!

Quote from: werwortmann on August 10, 2016, 05:22:53 AM

How can we get rid of orphan transactions in the gui?
They are always ontop, so I can't see my recent transactions

Not sure if there is a better way but I just used the wallet.dat that was backed up prior to the fork to get rid of them. Wink

mikegi

full member

Activity: 165

Merit: 100

Quote from: mxnsch on August 10, 2016, 04:03:11 AM

Nice catch! Looking at the changes, i will leave my masternodes running with the one additional commit:
https://github.com/Darknet-Crypto/Darknet/commit/db34f50e5fb1f8eb8dc31349d08809457220102c

I have the older one, looks like the changes are necessary as there are a lot of warnings and errors in the logs after the PoW blocks end.

Compiling.... Done ...

Let's see...

Code:

$ darknet-cli getblockhash 259880
f6bf9eae07bbba776309c374ef73b83bf633853b7026ceeff17e20ccd0774098

Yay!!!

I am up to this block now... does anyone want to confirm I am on the right chain?

darknet-cli getblockhash 260209
c1a37179151fd5f44d08d06805e4d4087341eacdf5aaaef2553c69fca29c21d4

Thought scripting everything would be overkill for the small amount of masternodes I have ( < 10 ) , but now considering it...
At least I have clusterssh set up now...

Time to set up masternodes...

werwortmann

member

Activity: 80

Merit: 10

How can we get rid of orphan transactions in the gui?
They are always ontop, so I can't see my recent transactions

boy2k

full member

Activity: 168

Merit: 100

Masternodes updated but still stuck...
{
   "version" : 2000100,
   "protocolversion" : 70300,
   "walletversion" : 61000,
   "balance" : 0.00000000,
   "obfuscation_balance" : 0.00000000,
   "blocks" : 259200,
   "timeoffset" : 0,
   "connections" : 11,
   "proxy" : "",
   "difficulty" : 48.59999131,
   "testnet" : false,
   "keypoololdest" : 1464207294,
   "keypoolsize" : 1001,
   "paytxfee" : 0.00000000,
   "relayfee" : 0.00010000,
   "staking status" : "Staking Not Active",
   "errors" : ""
}

werwortmann

member

Activity: 80

Merit: 10

Quote from: ?? on ??

Hi all,

Could you please check this block to be sure we are all on the same chain?

getblockhash 260200

c6e2324f5baf1b8dfcc5feee9d2eb6db3481136da78b287b1b2c44ff68932e12

I hope it's the one Cool

Mine also has that hash,
so looks good

werwortmann

member

Activity: 80

Merit: 10

I did check, my hash for that block is correct
It is also unlocked.
But getting 'staking not active'in the gui and also not receiving any mints.
On v2 I did stake succesfully before the chain died

EDIT: Locked and then unlocked my wallet, staking working now

jakiman

legendary

Activity: 1638

Merit: 1011

jakiman is back!

Quote from: werwortmann on August 10, 2016, 04:04:39 AM

I re-synced with the specific addnodes.
Everything seems to be staying synced now,
but I am not staking.
Been synced for a few hours now.
What is the staking maturity time?

Is your wallet unlocked?

Also, are you on the right chain?
"getblockhash 259880" should return "f6bf9eae07bbba776309c374ef73b83bf633853b7026ceeff17e20ccd0774098".

jakiman

legendary

Activity: 1638

Merit: 1011

jakiman is back!

My controller wallet is on the right chain and now starting up my MNs also. Grin

werwortmann

member

Activity: 80

Merit: 10

I re-synced with the specific addnodes.
Everything seems to be staying synced now,
but I am not staking.
Been synced for a few hours now.
What is the staking maturity time?

Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN - page 382. (Read 782375 times)