I've got two wallets running, both version 2.1.2.0, both running on Ubuntu 16.04, one staking, and one masternode...
Soooo, my masternode (which is NOT staking, I'm not sure if that's how it's supposed to be or not) is earning/masternoding just fine... However, although my "staking" wallet says "staking active", has not earned anything, and I've been running it for over two days at this point. Any ideas?
Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN - page 351. (Read 782375 times)
August 20, 2016, 01:48:35 PM
August 20, 2016, 07:17:11 AM
My wallet is all syncd up, but my MN's keep going in missing status, and im not receiving rewards. Why would that happen? I have 100 MN hosted by James.
log into masternode and check that its fully synced up and not stuck. may just need a restart.
August 20, 2016, 07:05:13 AM
My wallet is all syncd up, but my MN's keep going in missing status, and im not receiving rewards. Why would that happen? I have 100 MN hosted by James.
August 20, 2016, 06:17:38 AM
Is everyone else still having issues?
I haven't had any crashes since migrating to a fresh wallet.dat generated by the new wallet version. I only did this because setting up new MN addresses generated keys on existing test public addresses on the old one. I sent existing coins to Bittrex and then started fresh nodes with newly purchased coins. All nodes have recieved a payment and I am getting no crashes or hanging on close. I'd say it's working perfectly for me on Win 64.
August 20, 2016, 05:42:58 AM
Is everyone else still having issues?
Not really, but i can confirm now there is an existing issue with the current wallet and chaindata getting corrupt while staking on Windows 10 64bit. Happened to me overnight, OSX wallet on same version still fine. I will keep an eye on it. August 20, 2016, 05:08:08 AM
Is everyone else still having issues?
August 20, 2016, 04:57:55 AM
definately burn and make it as public as possible (block and hash and all)
Dash is haunted until today with these early mining issues !
these things stick !
Dash is haunted until today with these early mining issues !
these things stick !
August 20, 2016, 03:33:26 AM
I'm happy for them to be burnt as originally planned.
Even if it's only 0.139% of current coin supply.
Even if it's only 0.139% of current coin supply.
August 19, 2016, 09:50:04 PM
roughly 350 votes/.35 bitcoin to get us on coinpayments.
have you burnt the 60k coins yet?
sell at market value and use that for the funds to get us on?
have you burnt the 60k coins yet?
sell at market value and use that for the funds to get us on?
Why don't we wait a bit? I want to put some votes as soon as I finish my holidays and I think that the idea of giving those to devs taking into account the big effort done to solve these problems with this wallet is still valid.
Only a idea.
Honestly, while we appreciate the different ideas, we want to burn these coins like we said from the beginning. We don't want to be the types that go back on their word, that sets a bad precedent, as well as gives some folks legitimate negatives to dwell on. 60k is not that much in the grand scheme of things, and we will eventually make some budget proposals to compensate individuals for their contributions.
With that said, it will be a bit before we burn them. Right now, you may have noticed, presstab's block explorer is not really showing much useful data in the transaction and address pages. He is doing some tweaking to the backend so that things will display right. Once he is done with that we will burn them, then be able to point to a specific transaction so that anyone who would like can go and verify it.
We will be sure to let you know when it happens.
August 19, 2016, 06:02:25 PM
Wow, just for fun I did a start-missing and BOOM! They all fired up and I'm staking nicely since.
August 19, 2016, 05:58:19 PM
roughly 350 votes/.35 bitcoin to get us on coinpayments.
have you burnt the 60k coins yet?
sell at market value and use that for the funds to get us on?
have you burnt the 60k coins yet?
sell at market value and use that for the funds to get us on?
Why don't we wait a bit? I want to put some votes as soon as I finish my holidays and I think that the idea of giving those to devs taking into account the big effort done to solve these problems with this wallet is still valid.
Only a idea.
August 19, 2016, 03:39:37 PM
roughly 350 votes/.35 bitcoin to get us on coinpayments.
have you burnt the 60k coins yet?
sell at market value and use that for the funds to get us on?
have you burnt the 60k coins yet?
sell at market value and use that for the funds to get us on?
August 19, 2016, 03:36:15 PM
Can windows wallet get fixed plz. It lags out then crashes when you start nodes one after other. Start missing instantly crashes. It is getting stuck at a block/crashing out when staking.
I have used a wallet from may. Resynced from scratch. It is the program.
It's not the program, its the new chain that your old wallet is not even aware of. I am also on Win 10 64bit. Besides that fact, it works for me and others. Sure, there are still issues. We have good workarounds for most. If you use an old wallet, your nodes are at risk of not working.I have used a wallet from may. Resynced from scratch. It is the program.
so what is the workaround? was just told to use a wallet pre 2.0.1.0 version.
will this get fixed in an update?
Here is a solid work around for the lagging issue in the console.
walletpassphrase
enter
masternode start-alias
enter
walletpassphrase
enter
masternode start-alias
enter
etc etc..
we are looking into this issue...
EDIT: Make sure you have synced all the masternodes in your list before you start this, depending on the peers you have, this may take awhile after all the data has been synced. Check you masternode totals from the information tab against the Crowning stats page. You may not see all, but should see most (All depends on the peers you are connected to)
Code:
#!/bin/bash
# date: 20160819
# author: @marsmensch
# function: this script outputs a list of all configured masternodes with their alias
# this output can be used to start even big numbers of masternodes easily one-by-one
for MASTERNODE in $(darknet-cli masternode list-conf | awk -F":" '/masternode/{getline;gsub("\"",""); gsub(",",""); print $2 }')
do
echo "darknet-cli walletpassphrase 12000"
echo "darknet-cli masternode start-alias ${MASTERNODE}"
done
# date: 20160819
# author: @marsmensch
# function: this script outputs a list of all configured masternodes with their alias
# this output can be used to start even big numbers of masternodes easily one-by-one
for MASTERNODE in $(darknet-cli masternode list-conf | awk -F":" '/masternode/{getline;gsub("\"",""); gsub(",",""); print $2 }')
do
echo "darknet-cli walletpassphrase
echo "darknet-cli masternode start-alias ${MASTERNODE}"
done
Example output:
Quote
....
darknet-cli walletpassphrase 12000
darknet-cli masternode start-alias MN6
darknet-cli walletpassphrase 12000
darknet-cli masternode start-alias MN7
darknet-cli walletpassphrase 12000
darknet-cli masternode start-alias MN8
darknet-cli walletpassphrase 12000
darknet-cli masternode start-alias MN9
darknet-cli walletpassphrase 12000
darknet-cli masternode start-alias MN10
darknet-cli walletpassphrase 12000
darknet-cli masternode start-alias MN11
darknet-cli walletpassphrase 12000
darknet-cli masternode start-alias MN12
darknet-cli walletpassphrase 12000
....
darknet-cli walletpassphrase
darknet-cli masternode start-alias MN6
darknet-cli walletpassphrase
darknet-cli masternode start-alias MN7
darknet-cli walletpassphrase
darknet-cli masternode start-alias MN8
darknet-cli walletpassphrase
darknet-cli masternode start-alias MN9
darknet-cli walletpassphrase
darknet-cli masternode start-alias MN10
darknet-cli walletpassphrase
darknet-cli masternode start-alias MN11
darknet-cli walletpassphrase
darknet-cli masternode start-alias MN12
darknet-cli walletpassphrase
....
Does this work in Windows too? Or just Linux?
@Devs
Can you create a Debug Version of the Qt-wallet? I am trying hard to replicate on Windows and OSX, but no luck so far. Even with desperately fucked up wallets in Docker Containers.
August 19, 2016, 02:51:32 PM
My problem with that script is that my wallet randomly crashes even when starting one MN at a time...
until the wallet crash has been fixed a script is going to just annoy you with the crashing. masternode start-missing just needs to be fixed.
have you tried the work around i suggested and are still having your wallet crash??
- Wait until your masternodes are close the the amount on Crownings stats page
- console command: walletpassphrase
- console command: masternode start-alias
- arrow up key to re enter passphrase
- arrow up key twice change the name
etc etc??
This has been working without issue for me, zero wallet freezes.
I not questioning it just saying for people that frustrated. I activate mine wit
Masternode start-alias mn* WALLETPASS
But it does crash every now and again doing it this way. Can usually tell when not to press enter to activate it as it will lag out. If you tet activate it when it lags it crashes.
and you just keep pressing up and changing the number. But it is an issue that I hope is fixed in next update.
August 19, 2016, 02:38:08 PM
My problem with that script is that my wallet randomly crashes even when starting one MN at a time...
until the wallet crash has been fixed a script is going to just annoy you with the crashing. masternode start-missing just needs to be fixed.
have you tried the work around i suggested and are still having your wallet crash??
- Wait until your masternodes are close the the amount on Crownings stats page
- console command: walletpassphrase
- console command: masternode start-alias
- arrow up key to re enter passphrase
- arrow up key twice change the name
etc etc??
This has been working without issue for me, zero wallet freezes.
August 19, 2016, 02:32:59 PM
still keeps crashing on windows for me from time to time
Synced from scratch before
Blockdata got corrupted over this.
Synced from scratch before
Blockdata got corrupted over this.
Quote
Problem signature:
Problem Event Name: APPCRASH
Application Name: darknet-qt.exe
Application Version: 2.1.2.0
Application Timestamp: 57b5515b
Fault Module Name: ntdll.dll
Fault Module Version: 6.3.9600.18233
Fault Module Timestamp: 56bb4ebb
Exception Code: c0000005
Exception Offset: 00000000000773e6
OS Version: 6.3.9600.2.0.0.272.7
Locale ID: 1033
Additional Information 1: abcc
Additional Information 2: abcc8f7853b48d9807d6d51eb1fa5df9
Additional Information 3: abcc
Additional Information 4: abcc8f7853b48d9807d6d51eb1fa5df9
Problem Event Name: APPCRASH
Application Name: darknet-qt.exe
Application Version: 2.1.2.0
Application Timestamp: 57b5515b
Fault Module Name: ntdll.dll
Fault Module Version: 6.3.9600.18233
Fault Module Timestamp: 56bb4ebb
Exception Code: c0000005
Exception Offset: 00000000000773e6
OS Version: 6.3.9600.2.0.0.272.7
Locale ID: 1033
Additional Information 1: abcc
Additional Information 2: abcc8f7853b48d9807d6d51eb1fa5df9
Additional Information 3: abcc
Additional Information 4: abcc8f7853b48d9807d6d51eb1fa5df9
Are you using a backup of your wallet.dat that is from before v2.1.0.0? One that was made before that version, and was not used with the v2.1.0.0 wallet or the v2.1.1.0 wallet. I don't think there was any issues with the v2.1.0.0 wallet, but the v2.1.1.0 wallet corrupted wallet.dat files. If the wallet.dat was in place while using that wallet you will need to use another backup, or export your private keys and import them into a new wallet.dat.
For those that seem to still be having the occasional crash, could you run the wallet for a bit with a completely new, clean wallet.dat and verify that it does not crash. I am unable to replicate the problem, so need some help from you guys to troubleshoot it.
If you could shoot s3v3n a PM with an email address and get yourself a slack invite that would be great, thanks.
Mine doesn't crash I'm just missing huge gaps of transactions, tried backups from Jan until beginning of June, dumped private keys, salvaged wallet, resynced with every back up I have, recover txids, recover transactions 1 scan the blockchain for missing transactions and my coins are just gone, the weird thing is the first few test transactions I sent to and from Bittrex during the first pos version are still on my transaction list only the bulk ones are gone. And I asked Bittrex for help they just like transaction confirmed on the blockchain sorry. Been at this for a long time and never had this problem occur where I couldn't fix it. My balance is now literally like 6. Something DNET. Had 3 masternodes, now I have 6 coins lol. I'm not pissed or anything just baffled, like wtf man why the universe gotta mess with my darknet?
August 19, 2016, 02:09:37 PM
My problem with that script is that my wallet randomly crashes even when starting one MN at a time...
until the wallet crash has been fixed a script is going to just annoy you with the crashing. masternode start-missing just needs to be fixed.
August 19, 2016, 01:51:34 PM
My problem with that script is that my wallet randomly crashes even when starting one MN at a time...
August 19, 2016, 01:49:49 PM
Can windows wallet get fixed plz. It lags out then crashes when you start nodes one after other. Start missing instantly crashes. It is getting stuck at a block/crashing out when staking.
I have used a wallet from may. Resynced from scratch. It is the program.
It's not the program, its the new chain that your old wallet is not even aware of. I am also on Win 10 64bit. Besides that fact, it works for me and others. Sure, there are still issues. We have good workarounds for most. If you use an old wallet, your nodes are at risk of not working.I have used a wallet from may. Resynced from scratch. It is the program.
so what is the workaround? was just told to use a wallet pre 2.0.1.0 version.
will this get fixed in an update?
Here is a solid work around for the lagging issue in the console.
walletpassphrase
enter
masternode start-alias
enter
walletpassphrase
enter
masternode start-alias
enter
etc etc..
we are looking into this issue...
EDIT: Make sure you have synced all the masternodes in your list before you start this, depending on the peers you have, this may take awhile after all the data has been synced. Check you masternode totals from the information tab against the Crowning stats page. You may not see all, but should see most (All depends on the peers you are connected to)
Code:
#!/bin/bash
# date: 20160819
# author: @marsmensch
# function: this script outputs a list of all configured masternodes with their alias
# this output can be used to start even big numbers of masternodes easily one-by-one
for MASTERNODE in $(darknet-cli masternode list-conf | awk -F":" '/masternode/{getline;gsub("\"",""); gsub(",",""); print $2 }')
do
echo "darknet-cli walletpassphrase 12000"
echo "darknet-cli masternode start-alias ${MASTERNODE}"
done
# date: 20160819
# author: @marsmensch
# function: this script outputs a list of all configured masternodes with their alias
# this output can be used to start even big numbers of masternodes easily one-by-one
for MASTERNODE in $(darknet-cli masternode list-conf | awk -F":" '/masternode/{getline;gsub("\"",""); gsub(",",""); print $2 }')
do
echo "darknet-cli walletpassphrase
echo "darknet-cli masternode start-alias ${MASTERNODE}"
done
Example output:
Quote
....
darknet-cli walletpassphrase 12000
darknet-cli masternode start-alias MN6
darknet-cli walletpassphrase 12000
darknet-cli masternode start-alias MN7
darknet-cli walletpassphrase 12000
darknet-cli masternode start-alias MN8
darknet-cli walletpassphrase 12000
darknet-cli masternode start-alias MN9
darknet-cli walletpassphrase 12000
darknet-cli masternode start-alias MN10
darknet-cli walletpassphrase 12000
darknet-cli masternode start-alias MN11
darknet-cli walletpassphrase 12000
darknet-cli masternode start-alias MN12
darknet-cli walletpassphrase 12000
....
darknet-cli walletpassphrase
darknet-cli masternode start-alias MN6
darknet-cli walletpassphrase
darknet-cli masternode start-alias MN7
darknet-cli walletpassphrase
darknet-cli masternode start-alias MN8
darknet-cli walletpassphrase
darknet-cli masternode start-alias MN9
darknet-cli walletpassphrase
darknet-cli masternode start-alias MN10
darknet-cli walletpassphrase
darknet-cli masternode start-alias MN11
darknet-cli walletpassphrase
darknet-cli masternode start-alias MN12
darknet-cli walletpassphrase
....
Does this work in Windows too? Or just Linux?
August 19, 2016, 01:46:22 PM
still keeps crashing on windows for me from time to time
Synced from scratch before
Blockdata got corrupted over this.
Synced from scratch before
Blockdata got corrupted over this.
Quote
Problem signature:
Problem Event Name: APPCRASH
Application Name: darknet-qt.exe
Application Version: 2.1.2.0
Application Timestamp: 57b5515b
Fault Module Name: ntdll.dll
Fault Module Version: 6.3.9600.18233
Fault Module Timestamp: 56bb4ebb
Exception Code: c0000005
Exception Offset: 00000000000773e6
OS Version: 6.3.9600.2.0.0.272.7
Locale ID: 1033
Additional Information 1: abcc
Additional Information 2: abcc8f7853b48d9807d6d51eb1fa5df9
Additional Information 3: abcc
Additional Information 4: abcc8f7853b48d9807d6d51eb1fa5df9
Problem Event Name: APPCRASH
Application Name: darknet-qt.exe
Application Version: 2.1.2.0
Application Timestamp: 57b5515b
Fault Module Name: ntdll.dll
Fault Module Version: 6.3.9600.18233
Fault Module Timestamp: 56bb4ebb
Exception Code: c0000005
Exception Offset: 00000000000773e6
OS Version: 6.3.9600.2.0.0.272.7
Locale ID: 1033
Additional Information 1: abcc
Additional Information 2: abcc8f7853b48d9807d6d51eb1fa5df9
Additional Information 3: abcc
Additional Information 4: abcc8f7853b48d9807d6d51eb1fa5df9
Are you using a backup of your wallet.dat that is from before v2.1.0.0? One that was made before that version, and was not used with the v2.1.0.0 wallet or the v2.1.1.0 wallet. I don't think there was any issues with the v2.1.0.0 wallet, but the v2.1.1.0 wallet corrupted wallet.dat files. If the wallet.dat was in place while using that wallet you will need to use another backup, or export your private keys and import them into a new wallet.dat.
For those that seem to still be having the occasional crash, could you run the wallet for a bit with a completely new, clean wallet.dat and verify that it does not crash. I am unable to replicate the problem, so need some help from you guys to troubleshoot it.
If you could shoot s3v3n a PM with an email address and get yourself a slack invite that would be great, thanks.
Jump to: