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

[werwortmann]

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

[1713552761]

1713552761

[1713552761]

1713552761

[werwortmann]

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

Mine also has that hash,
so looks good

[boy2k]

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]

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

[mikegi]

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...

[jakiman]

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.

[shimlbit]

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]

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.

[pjcltd]

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

[BitcoinFX]

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:

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]

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:

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]

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

[jakiman]

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

[pjcltd]

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

[berron]

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

Mine also has that hash,
so looks good

Thank you! great news

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

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

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.

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:

getblockhash 259880
f6bf9eae07bbba776309c374ef73b83bf633853b7026ceeff17e20ccd0774098

like them
but

getblockhash 260209
f47f44ca42bf37918cce19e638ba3d7bbf10f6da24510b2eebf17c34c3700a27

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

[BitcoinFX]

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:

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]

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.

[tylerderden]

Allgood here, right on guys!

[jakiman]

getblockhash 260209

c1a37179151fd5f44d08d06805e4d4087341eacdf5aaaef2553c69fca29c21d4

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

I get the same as what you get on my controller wallet and some of my MNs.

But some of my other MNs show something else (below) even though hash for 259880 is same as what s3v3n put up
f47f44ca42bf37918cce19e638ba3d7bbf10f6da24510b2eebf17c34c3700a27

This is still a mess.

Edit: seems i forgot to run a full re-synd on the problematic MNs.

[BitcoinFX]

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.

~/Darknet/src# ./darknet-cli getblockhash 260209
c1a37179151fd5f44d08d06805e4d4087341eacdf5aaaef2553c69fca29c21d4

~ from onlynet=tor