Wallet staking - 2 payments since yesterday
MNs- All paid once (except 1) - ether 28 or 30 payments
gonna start mixing back up next
(that is coin mixing - mochitos are ready already
) ) 
Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN - page 316. (Read 782375 times)
September 24, 2016, 07:35:45 PM
Seems all good
Wallet staking - 2 payments since yesterday
MNs- All paid once (except 1) - ether 28 or 30 payments
gonna start mixing back up next
(that is coin mixing - mochitos are ready already) )
Wallet staking - 2 payments since yesterday
MNs- All paid once (except 1) - ether 28 or 30 payments
gonna start mixing back up next
(that is coin mixing - mochitos are ready already
) ) 
September 24, 2016, 05:54:36 PM
Thanks. I've just created a swap file, changed to a lower swappiness then restarted the lagging ones. So far so good.
September 24, 2016, 05:41:39 PM
For those running multiple masternodes on a single Vultr server, have you noticed if they lag in block number quite often?
e.g. Out of 5 instances, few often lag behind and show EXPIRED on my controller but catches up later on. Resource issue?
"blocks" : 312126,
"blocks" : 312113,
"blocks" : 312113,
"blocks" : 312113,
"blocks" : 312113,
e.g. Out of 5 instances, few often lag behind and show EXPIRED on my controller but catches up later on. Resource issue?
"blocks" : 312126,
"blocks" : 312113,
"blocks" : 312113,
"blocks" : 312113,
"blocks" : 312113,
Yep
September 24, 2016, 05:04:03 PM
For those running multiple masternodes on a single Vultr server, have you noticed if they lag in block number quite often?
e.g. Out of 5 instances, few often lag behind and show EXPIRED on my controller but catches up later on. Resource issue?
"blocks" : 312126,
"blocks" : 312113,
"blocks" : 312113,
"blocks" : 312113,
"blocks" : 312113,
e.g. Out of 5 instances, few often lag behind and show EXPIRED on my controller but catches up later on. Resource issue?
"blocks" : 312126,
"blocks" : 312113,
"blocks" : 312113,
"blocks" : 312113,
"blocks" : 312113,
September 24, 2016, 06:20:10 AM
After yesterday affaire I have been trying to recover one of the MN in Paul's servers and I'm not capable of getting any connection. I have used a valid blockchain, one of the shared here, and I have added the addnode and bantime lines you comment here. Node started, stopped and started again an all the rest of usual tricks done. I'm stucked with no connections in block 272484. Any new ideas??
Salute
Salute
Hi whats the ip ?
September 24, 2016, 05:36:10 AM
After yesterday affaire I have been trying to recover one of the MN in Paul's servers and I'm not capable of getting any connection. I have used a valid blockchain, one of the shared here, and I have added the addnode and bantime lines you comment here. Node started, stopped and started again an all the rest of usual tricks done. I'm stucked with no connections in block 272484. Any new ideas??
Salute
Salute
September 24, 2016, 05:13:05 AM
why in maintenance?
Not sure if you are asking after you read my update or not so here it is again.
Dev Update Snippet
New wallet is currently in the works that will implement some changes to prevent such exploit that caused much havoc yesterday.
Bittrex wallet is currently in maintenance mode. It will be back online in a day or so after the new wallet has been tested by devs.
In the meantime, make sure your wallet is at or just ahead of the MN info page's shown block and that the block hash matches.
If not, you need to resync with a backed up chain or from scratch with following lines in the darknet.conf. (no other addnodes)
MN Info Page = http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html
New wallet is currently in the works that will implement some changes to prevent such exploit that caused much havoc yesterday.
Bittrex wallet is currently in maintenance mode. It will be back online in a day or so after the new wallet has been tested by devs.
In the meantime, make sure your wallet is at or just ahead of the MN info page's shown block and that the block hash matches.
If not, you need to resync with a backed up chain or from scratch with following lines in the darknet.conf. (no other addnodes)
Code:
addnode=173.245.158.8
addnode=68.108.10.35
bantime=50
MN Info Page = http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html
September 24, 2016, 03:04:32 AM
why in maintenance?
September 24, 2016, 02:21:31 AM
getting a lot of conflicts again with masternode and staking rewards 
....
was all fine until ~2.5 hrs ago
edit: wallets in sync with masternode payments page
....was all fine until ~2.5 hrs ago
edit: wallets in sync with masternode payments page
I got a couple of MN payment conflicts about 2 hours ago but none since then so looks okay on mine.
September 24, 2016, 01:55:51 AM
getting a lot of conflicts again with masternode and staking rewards ....
was all fine until ~2.5 hrs ago
edit: wallets in sync with masternode payments page
....was all fine until ~2.5 hrs ago
edit: wallets in sync with masternode payments page
September 24, 2016, 01:43:36 AM
Wallet forked, all my mastrnodes ok I think..
Staking on.
Wallet:
$ darknet-cli getblockhash 311223
9a44e1e3573a0fc33b6340b5b6be28d05abbf738f407a69eba3e9d6bd71f3636
Masternodes:
darknet-cli getblockhash 311223
9a44e1e3573a0fc33b6340b5b6be28d05abbf738f407a69eba3e9d6bd71f3636
darknet-cli getblockhash 311244
15e3842967038da2336fa829bafe19e8dbece41d3f4b298b30469d4ca13eeed6
Staking on.
Wallet:
$ darknet-cli getblockhash 311223
9a44e1e3573a0fc33b6340b5b6be28d05abbf738f407a69eba3e9d6bd71f3636
Masternodes:
darknet-cli getblockhash 311223
9a44e1e3573a0fc33b6340b5b6be28d05abbf738f407a69eba3e9d6bd71f3636
darknet-cli getblockhash 311244
15e3842967038da2336fa829bafe19e8dbece41d3f4b298b30469d4ca13eeed6
September 24, 2016, 01:10:27 AM
Dev Update Snippet
New wallet is currently in the works that will implement some changes to prevent such exploit that caused much havoc yesterday.
Bittrex wallet is currently in maintenance mode. It will be back online in a day or so after the new wallet has been tested by devs.
In the meantime, make sure your wallet is at or just ahead of the MN info page's shown block and that the block hash matches.
If not, you need to resync with a backed up chain or from scratch with following lines in the darknet.conf. (no other addnodes)
MN Info Page = http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html
New wallet is currently in the works that will implement some changes to prevent such exploit that caused much havoc yesterday.
Bittrex wallet is currently in maintenance mode. It will be back online in a day or so after the new wallet has been tested by devs.
In the meantime, make sure your wallet is at or just ahead of the MN info page's shown block and that the block hash matches.
If not, you need to resync with a backed up chain or from scratch with following lines in the darknet.conf. (no other addnodes)
Code:
addnode=173.245.158.8
addnode=68.108.10.35
bantime=50
MN Info Page = http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html
tx
all on track here
MN's (no payments yet) + Wallet (1 staked - 1 stacked but refused)
September 23, 2016, 11:44:47 PM
Dev Update Snippet
New wallet is currently in the works that will implement some changes to prevent such exploit that caused much havoc yesterday.
Bittrex wallet is currently in maintenance mode. It will be back online in a day or so after the new wallet has been tested by devs.
In the meantime, make sure your wallet is at or just ahead of the MN info page's shown block and that the block hash matches.
If not, you need to resync with a backed up chain or from scratch with following lines in the darknet.conf. (no other addnodes)
MN Info Page = http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html
New wallet is currently in the works that will implement some changes to prevent such exploit that caused much havoc yesterday.
Bittrex wallet is currently in maintenance mode. It will be back online in a day or so after the new wallet has been tested by devs.
In the meantime, make sure your wallet is at or just ahead of the MN info page's shown block and that the block hash matches.
If not, you need to resync with a backed up chain or from scratch with following lines in the darknet.conf. (no other addnodes)
Code:
addnode=173.245.158.8
addnode=68.108.10.35
bantime=50
MN Info Page = http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html
September 23, 2016, 05:49:35 PM
Okay, all my masternodes and controller wallet seems to be running on right chain now.
All have matching blocks to each other and block hash match the MN info page.
For now, setting the bantime to something low (e.g. 50) should keep us all on the right chain and may prevent a similar attack causing all this havoc.
Through this event, I learnt even more things about linux at least. lol
All have matching blocks to each other and block hash match the MN info page.
For now, setting the bantime to something low (e.g. 50) should keep us all on the right chain and may prevent a similar attack causing all this havoc.
Through this event, I learnt even more things about linux at least. lol
September 23, 2016, 05:16:11 PM
As the Dropbox-Link isn't reachable due to heavy load look for the Darknet Blockchain at http://cryptochainer.com/dir/
It is 2 weeks behind.
It is 2 weeks behind.
September 23, 2016, 02:57:14 PM
if you need a new chain, use this one. until it gets locked.
https://dl.dropboxusercontent.com/s/4iijhudq5oonswr/chain.zip?dl=0
please turn off staking for now, either add staking=0 in .conf file, or leave your wallet locked until we get back to you.
https://dl.dropboxusercontent.com/s/4iijhudq5oonswr/chain.zip?dl=0
please turn off staking for now, either add staking=0 in .conf file, or leave your wallet locked until we get back to you.
Thanks, the chain from Dropbox brought me back on track.
getblockhash 309280
5c1c1b8d830bc28a15552c767c03511d7b3724912a76e586ca19c565f10e4c44
Was now about 18hours on the right chain - checked the blockhash with http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html but around block 310579 - i was some blocks behind. Turned wallet off and restarted and now back again on the right chain - maybe just a lag in the network... idk
I'll still keep an eye on it.
Do we already know what caused the split to main and fork chain? As you wrote that some are still on the older versions...
As of Sept 15th, 1:00 pm EST The Masternode Enforcement will be re-enabled, anyone still on Source v2.1.2.1 or older will stall, and no longer receive any rewards. Please make sure you are updated before then.
Still seeing a lot of wallets/masternodes on the wrong chains out there, please verify your chain against the BE or Stats page and update if necessary.
September 23, 2016, 10:23:34 AM
Still seeing a lot of wallets/masternodes on the wrong chains out there, please verify your chain against the BE or Stats page and update if necessary.
September 23, 2016, 09:44:36 AM
Seems all works well.
Staked 2 blocks.
getblockhash 310265
07f7d2bc6063d9630e9bf15cecd789dfd1b5bc964ec57a9a525733fb658f4cca
Staked 2 blocks.
getblockhash 310265
07f7d2bc6063d9630e9bf15cecd789dfd1b5bc964ec57a9a525733fb658f4cca
same
have all my MNs back on !
September 23, 2016, 09:13:50 AM
Seems all works well.
Staked 2 blocks.
getblockhash 310265
07f7d2bc6063d9630e9bf15cecd789dfd1b5bc964ec57a9a525733fb658f4cca
Staked 2 blocks.
getblockhash 310265
07f7d2bc6063d9630e9bf15cecd789dfd1b5bc964ec57a9a525733fb658f4cca
September 23, 2016, 08:02:23 AM
.....
As for MN payments, it's normal that it varies when number of masternode count fluctuates. It's due to the seesaw algorithm.
As for MN payments, it's normal that it varies when number of masternode count fluctuates. It's due to the seesaw algorithm.
yeah but some where definitely wrong after yesterdays desaster at least in my wallet
Jump to: