Search content
Sort by
Showing 12 of 12 results by AggroHead
Re: [ANN] [QRK] Quark | POW/POS+MN | 0.10.7.4 - New Self Moderated Thread
This coin daemon for masternode is terribly unreliable.
I host a 32 GB vps with 10 masternodes on it. (yes, swap-file on ssd)
Since there is no solution to get the masternodes running stable, I want to share my script.
I created a crontab (running every 10 minutes). It checks blockcount from explorer and compare to masternode's-blockcount.
If blockcount of any (node or explorer) is newer than (-gap of 5 blocks) OR block is the same as last cron-run (because explorer also hangs sometimes) --> it stop mn-daemon (and systemctl restart it automatically).
Feel free to use this kind of shit-script to keep rewards running. (And yes rewards are still incomming but if your mn hangs on block for several hours, you need to restart mn from wallet again, to get rewards again.
Some of my mn's hangs every ~30-120 minutes, so rewards never began to run.
script.sh
to monitor all my nodes I use this little oneliner:
I host a 32 GB vps with 10 masternodes on it. (yes, swap-file on ssd)
Since there is no solution to get the masternodes running stable, I want to share my script.
I created a crontab (running every 10 minutes). It checks blockcount from explorer and compare to masternode's-blockcount.
If blockcount of any (node or explorer) is newer than (-gap of 5 blocks) OR block is the same as last cron-run (because explorer also hangs sometimes) --> it stop mn-daemon (and systemctl restart it automatically).
Feel free to use this kind of shit-script to keep rewards running. (And yes rewards are still incomming but if your mn hangs on block for several hours, you need to restart mn from wallet again, to get rewards again.
Some of my mn's hangs every ~30-120 minutes, so rewards never began to run.
script.sh
Code:
#!/bin/bash
#Console Colour
BLUE="\033[0;34m"
YELLOW="\033[0;33m"
CYAN="\033[0;36m"
PURPLE="\033[0;35m"
RED='\033[0;31m'
GREEN="\033[0;32m"
MAG='\e[1;35m'
NC='\033[0m'
coin_cli=/usr/local/bin/quark-cli
blockcount_gap=5
logfile=/root/mnh-status.log
# /root/*subfolder* = masternode-instance
# mn-01 mn-02 mn-03 mn-04 mn-05 mn-06 mn-07 mn-08 mn-09 mn-10
mns=$(ls /root/ | grep mn-)
function log() {
logtime=$(date '+%H:%M:%S')
C=$1
LS="$2"
echo -e "$logtime: ${C}$LS${NC}"
}
function logtf() {
log $1 "$2"
LS="$2"
logtime=$(date '+%Y-%m-%d %H:%M:%S')
echo "$logtime: $LS" >> $logfile
}
blockcount=$(curl -s https://chainz.cryptoid.info/qrk/api.dws?q=getblockcount --max-time 5)
if [ $? -ne 0 ]; then
blockcount=0
fi
lastblockcount=$(cat /root/mnh-lastblock.txt)
if [ $? -ne 0 ]; then
lastblockcount=0
fi
for mn in $mns ; do
mbc=$($coin_cli -datadir=/root/$mn getblockcount 2>/dev/null)
mst=$?
if [ $mst -eq 0 ]; then
if [ $mbc -gt $blockcount ]; then
blockcount=$mbc
fi
fi
done
echo $blockcount > /root/mnh-lastblock.txt
logtf $YELLOW "Highest Block: $blockcount"
logtf $YELLOW " Last Block: $lastblockcount"
if [ $blockcount -le $lastblockcount ]; then
logtf $RED "Same blockcount as last run!"
for mn in $mns ; do
mbc=$($coin_cli -datadir=/root/$mn getblockcount 2>/dev/null)
mst=$?
mbcg=$(($mbc-$blockcount))
logtf $NC "$mn Status: $mst Block: $mbc ($mbcg)"
if [ $mst -eq 0 ]; then
logtf $RED "$mn stopping"
$coin_cli -datadir=/root/$mn stop >/dev/null
fi
done
else
for mn in $mns ; do
mbc=$($coin_cli -datadir=/root/$mn getblockcount 2>/dev/null)
mst=$?
mbcg=$(($mbc-$blockcount))
logtf $NC "$mn Status: $mst Block: $mbc ($mbcg)"
if [ $mst -eq 0 ]; then
if [ $mbc -le $(($blockcount-$blockcount_gap)) ]; then
logtf $RED "$mn stopping"
$coin_cli -datadir=/root/$mn stop >/dev/null
fi
fi
done
fi
#Console Colour
BLUE="\033[0;34m"
YELLOW="\033[0;33m"
CYAN="\033[0;36m"
PURPLE="\033[0;35m"
RED='\033[0;31m'
GREEN="\033[0;32m"
MAG='\e[1;35m'
NC='\033[0m'
coin_cli=/usr/local/bin/quark-cli
blockcount_gap=5
logfile=/root/mnh-status.log
# /root/*subfolder* = masternode-instance
# mn-01 mn-02 mn-03 mn-04 mn-05 mn-06 mn-07 mn-08 mn-09 mn-10
mns=$(ls /root/ | grep mn-)
function log() {
logtime=$(date '+%H:%M:%S')
C=$1
LS="$2"
echo -e "$logtime: ${C}$LS${NC}"
}
function logtf() {
log $1 "$2"
LS="$2"
logtime=$(date '+%Y-%m-%d %H:%M:%S')
echo "$logtime: $LS" >> $logfile
}
blockcount=$(curl -s https://chainz.cryptoid.info/qrk/api.dws?q=getblockcount --max-time 5)
if [ $? -ne 0 ]; then
blockcount=0
fi
lastblockcount=$(cat /root/mnh-lastblock.txt)
if [ $? -ne 0 ]; then
lastblockcount=0
fi
for mn in $mns ; do
mbc=$($coin_cli -datadir=/root/$mn getblockcount 2>/dev/null)
mst=$?
if [ $mst -eq 0 ]; then
if [ $mbc -gt $blockcount ]; then
blockcount=$mbc
fi
fi
done
echo $blockcount > /root/mnh-lastblock.txt
logtf $YELLOW "Highest Block: $blockcount"
logtf $YELLOW " Last Block: $lastblockcount"
if [ $blockcount -le $lastblockcount ]; then
logtf $RED "Same blockcount as last run!"
for mn in $mns ; do
mbc=$($coin_cli -datadir=/root/$mn getblockcount 2>/dev/null)
mst=$?
mbcg=$(($mbc-$blockcount))
logtf $NC "$mn Status: $mst Block: $mbc ($mbcg)"
if [ $mst -eq 0 ]; then
logtf $RED "$mn stopping"
$coin_cli -datadir=/root/$mn stop >/dev/null
fi
done
else
for mn in $mns ; do
mbc=$($coin_cli -datadir=/root/$mn getblockcount 2>/dev/null)
mst=$?
mbcg=$(($mbc-$blockcount))
logtf $NC "$mn Status: $mst Block: $mbc ($mbcg)"
if [ $mst -eq 0 ]; then
if [ $mbc -le $(($blockcount-$blockcount_gap)) ]; then
logtf $RED "$mn stopping"
$coin_cli -datadir=/root/$mn stop >/dev/null
fi
fi
done
fi
to monitor all my nodes I use this little oneliner:
Code:
watch -n 1 'echo -n "mn01: " && quark-cli -datadir=/root/mn-01 getblockcount && quark-cli -datadir=/root/mn-01 masternode status | grep status && echo && echo -n "mn02: " && quark-cli -datadir=/root/mn-02 getblockcount && quark-cli -datadir=/root/mn-02 masternode status | grep status && echo && echo -n "mn03: " && quark-cli -datadir=/root/mn-03 getblockcount && quark-cli -datadir=/root/mn-03 masternode status | grep status && echo && echo -n "mn04: " && quark-cli -datadir=/root/mn-04 getblockcount && quark-cli -datadir=/root/mn-04 masternode status | grep status && echo && echo -n "mn05: " && quark-cli -datadir=/root/mn-05 getblockcount && quark-cli -datadir=/root/mn-05 masternode status | grep status && echo && echo -n "mn06: " && quark-cli -datadir=/root/mn-06 getblockcount && quark-cli -datadir=/root/mn-06 masternode status | grep status && echo && echo -n "mn07: " && quark-cli -datadir=/root/mn-07 getblockcount && quark-cli -datadir=/root/mn-07 masternode status | grep status && echo && echo -n "mn08: " && quark-cli -datadir=/root/mn-08 getblockcount && quark-cli -datadir=/root/mn-08 masternode status | grep status && echo && echo -n "mn09: " && quark-cli -datadir=/root/mn-09 getblockcount && quark-cli -datadir=/root/mn-09 masternode status | grep status && echo && echo -n "mn10: " && quark-cli -datadir=/root/mn-10 getblockcount && quark-cli -datadir=/root/mn-10 masternode status | grep status'
Re: [ANN] [QRK] Quark | POW/POS+MN | 0.10.7.4 - New Self Moderated Thread
8 of my 10 masternodes stock on
block
7289807
each one uses a conf-file with different addnodes
also my desktop-wallet stuck at same block.
after restart wallet, it works again. But not for long time...
block
7289807
each one uses a conf-file with different addnodes
also my desktop-wallet stuck at same block.
after restart wallet, it works again. But not for long time...
Re: [ANN] [QRK] Quark | POW+POS | 0.10.6.3 - New Self Moderated Thread
@Dev, do you know when AEX opens their wallet?
I'm waiting more than one month. Opend several tickets to get more information.
They always told me "wallet upgrade is in progress". Do you have more details?
I'm waiting more than one month. Opend several tickets to get more information.
They always told me "wallet upgrade is in progress". Do you have more details?
Re: [ANN] [QRK] Quark | POW+POS | 0.10.6.3 - New Self Moderated Thread
Code:
cp .quarkcoin/quark-cli /usr/local/bin/quark-cli
sudo chmod +x /usr/local/bin/quark-cli
sudo chmod 777 .quarkcoin/debug.log
and then run watch command againsudo chmod +x /usr/local/bin/quark-cli
sudo chmod 777 .quarkcoin/debug.log
Re: [ANN] [QRK] Quark | POW+POS | 0.10.6.3 - New Self Moderated Thread
You can use this command to follow-up sync-status:
Code:
watch -n 5 'tail -n 20 .quarkcoin/debug.log && quark-cli mnsync status && quark-cli getblockcount && quark-cli masternode status'
Re: [ANN] [QRK] Quark | POW+POS | 0.10.6.3 - New Self Moderated Thread
Hi,
from FreiExchange.com i cannot withdraw my Quarks, page say "Withdraw address not valid".
I wrote to support, and they say:
"There is a issue after the last upgrade of wallet from the quark team so we are investigating it as we speak"
Can you send the latest wallet to them?
Thanks,
from FreiExchange.com i cannot withdraw my Quarks, page say "Withdraw address not valid".
I wrote to support, and they say:
"There is a issue after the last upgrade of wallet from the quark team so we are investigating it as we speak"
Can you send the latest wallet to them?
Thanks,
I just opend a support-call too, they are working on issue.
They use newest wallet 0.10.7.3
Re: [ANN] [QRK] Quark | POW+POS | 0.10.6.3 - New Self Moderated Thread
We have 5 MN running, but only 2 get always (less) rewards, the other 3 get no rewards since the change to 0.17.7.2. When will come a solution that real works?
All my MN's earning rewards in even distribution.
I've setup two of them yesterday and it works with 0.17.7.2.
Re: [ANN] [QRK] Quark | POW+POS | 0.10.6.3 - New Self Moderated Thread
...The masternode distribution is mainly the interest adjustment among miners...
Can you please explain this?Does it mean a pool/miner can define the generation amout?
3.69416 for miner and 0 for mn
or
1.23139 for miner and 2.46277 for mn
per block
I just setup a yiimp test-pool and tested mining. At default yiimp mine 3.69416 per block, without mn reward.
Can you please expain how to modify yiimp (or stratum) to generate the correct mn amount?
Good work so far, wallet is really stable now.
Re: [ANN] [QRK] Quark | POW+POS | 0.10.6.3 - New Self Moderated Thread
I dont understand why blockreward sometime contains mn-reward and sometime contains not.
Could someone please explain this behaviour?
2.46277 qrk for masternode (block 7186675):
no reward for masternode (block 7186673):
Could someone please explain this behaviour?
2.46277 qrk for masternode (block 7186675):
Code:
{
"txid": "9ed78d38cf4ca48af99484855fe1b48d0e5619b0ff2ae551da69853fa070e4aa",
"version": 1,
"locktime": 0,
"vin": [
{
"coinbase": "03f3a86d0447b56b5d088100002c750000007969696d7000",
"sequence": 0
}
],
"vout": [
{
"value": 2.46277,
"n": 0,
"scriptPubKey": {
"asm": "OP_DUP OP_HASH160 be2b394514fb004d27d168a893ba19fc1fc5b97a OP_EQUALVERIFY OP_CHECKSIG",
"hex": "76a914be2b394514fb004d27d168a893ba19fc1fc5b97a88ac",
"reqSigs": 1,
"type": "pubkeyhash",
"addresses": [
"QdwWGyx6m7SsAnvqAaVwji9sXmeEmPzLEv"
]
}
},
{
"value": 1.23139,
"n": 1,
"scriptPubKey": {
"asm": "OP_DUP OP_HASH160 df297fb547331c691d876ceefe21cec085606813 OP_EQUALVERIFY OP_CHECKSIG",
"hex": "76a914df297fb547331c691d876ceefe21cec08560681388ac",
"reqSigs": 1,
"type": "pubkeyhash",
"addresses": [
"QgwxWU7xRWEVXnHyBqdgsEFDwjVVB75LyC"
]
}
}
],
"blockhash": "00000000000c31d961f797a2a8a212b2c74a043ca61310d4b5a6233c50fa5e9e",
"confirmations": 4,
"time": 1567339845,
"blocktime": 1567339845
}
"txid": "9ed78d38cf4ca48af99484855fe1b48d0e5619b0ff2ae551da69853fa070e4aa",
"version": 1,
"locktime": 0,
"vin": [
{
"coinbase": "03f3a86d0447b56b5d088100002c750000007969696d7000",
"sequence": 0
}
],
"vout": [
{
"value": 2.46277,
"n": 0,
"scriptPubKey": {
"asm": "OP_DUP OP_HASH160 be2b394514fb004d27d168a893ba19fc1fc5b97a OP_EQUALVERIFY OP_CHECKSIG",
"hex": "76a914be2b394514fb004d27d168a893ba19fc1fc5b97a88ac",
"reqSigs": 1,
"type": "pubkeyhash",
"addresses": [
"QdwWGyx6m7SsAnvqAaVwji9sXmeEmPzLEv"
]
}
},
{
"value": 1.23139,
"n": 1,
"scriptPubKey": {
"asm": "OP_DUP OP_HASH160 df297fb547331c691d876ceefe21cec085606813 OP_EQUALVERIFY OP_CHECKSIG",
"hex": "76a914df297fb547331c691d876ceefe21cec08560681388ac",
"reqSigs": 1,
"type": "pubkeyhash",
"addresses": [
"QgwxWU7xRWEVXnHyBqdgsEFDwjVVB75LyC"
]
}
}
],
"blockhash": "00000000000c31d961f797a2a8a212b2c74a043ca61310d4b5a6233c50fa5e9e",
"confirmations": 4,
"time": 1567339845,
"blocktime": 1567339845
}
no reward for masternode (block 7186673):
Code:
{
"txid": "ef02c3e9cda9b5011eac41074f0c0705391d7a3a5ce3058bfb994f2bc7d78b42",
"version": 1,
"locktime": 0,
"vin": [
{
"coinbase": "03f1a86d0416b56b5d0881000005792500007969696d7000",
"sequence": 0
}
],
"vout": [
{
"value": 3.69416,
"n": 0,
"scriptPubKey": {
"asm": "OP_DUP OP_HASH160 1993d4d26ea50fb09c1bce734f82ea581dc9d43e OP_EQUALVERIFY OP_CHECKSIG",
"hex": "76a9141993d4d26ea50fb09c1bce734f82ea581dc9d43e88ac",
"reqSigs": 1,
"type": "pubkeyhash",
"addresses": [
"QNwE6bWzpNMMwdRLdw1Mr4wbBQFjN97aqb"
]
}
}
],
"blockhash": "0000000000074c441bf0a3d203b068a0611fa3b76768eac92c8498e3c6c8e15b",
"confirmations": 7,
"time": 1567339798,
"blocktime": 1567339798
}
"txid": "ef02c3e9cda9b5011eac41074f0c0705391d7a3a5ce3058bfb994f2bc7d78b42",
"version": 1,
"locktime": 0,
"vin": [
{
"coinbase": "03f1a86d0416b56b5d0881000005792500007969696d7000",
"sequence": 0
}
],
"vout": [
{
"value": 3.69416,
"n": 0,
"scriptPubKey": {
"asm": "OP_DUP OP_HASH160 1993d4d26ea50fb09c1bce734f82ea581dc9d43e OP_EQUALVERIFY OP_CHECKSIG",
"hex": "76a9141993d4d26ea50fb09c1bce734f82ea581dc9d43e88ac",
"reqSigs": 1,
"type": "pubkeyhash",
"addresses": [
"QNwE6bWzpNMMwdRLdw1Mr4wbBQFjN97aqb"
]
}
}
],
"blockhash": "0000000000074c441bf0a3d203b068a0611fa3b76768eac92c8498e3c6c8e15b",
"confirmations": 7,
"time": 1567339798,
"blocktime": 1567339798
}
Re: [ANN] [QRK] Quark | POW+POS | 0.10.6.3 - New Self Moderated Thread
no more wallet crashes because no new block syncs
in debug.log you find
same issue as last time...
is it possible to manually correct blocktemplate to mine new correct block?
Two possibilities
Some people are using the new code to generate a lot of rewards for the foundation
(to create panic)
Unknown bugs have emerged as a result of mining along with the old chain during the upgrade
it's a bug - happened during adaption of yiimp-base pool to new coinbase-layout.
getblocktemplate reports wrong scaled values and wallet doesn't check max value for treasury
Yeah! can we get a max value check? Better an error than a 27million coin overrun.
Any Idea where it's getting that magical number? (106,394.92616)
8 hours in seconds is 28800 times the MN reward 3.69416 is very close to the magical number 106391.808 Perhaps some rounding is involved.
QVvYypXoiRXcJpJpRVkftKEjMkXbd6UKJv
106,391.232 QRK
QirdV1H3Tikg12QefVkoFKrwkfHxT8EXia
3.69416 QRK
in debug.log you find
Code:
Treasury payment of 106391.232 to QVvYypXoiRXcJpJpRVkftKEjMkXbd6UKJv
same issue as last time...
is it possible to manually correct blocktemplate to mine new correct block?
rpc-getblocktemplate calls CreateNewBlock()
(https://github.com/quark-project/quark/blob/f813e83ee229d9dce9f798051f96ca73f36d91f5/src/rpcmining.cpp#L517)
in CreateNewBlock() after MN-startblock it calls FillBlockPayee()
(https://github.com/quark-project/quark/blob/f813e83ee229d9dce9f798051f96ca73f36d91f5/src/miner.cpp#L360)
where FillTreasuryPayee() is called
(https://github.com/quark-project/quark/blob/f813e83ee229d9dce9f798051f96ca73f36d91f5/src/masternode-payments.cpp#L304)
(https://github.com/quark-project/quark/blob/f813e83ee229d9dce9f798051f96ca73f36d91f5/src/rpcmining.cpp#L517)
in CreateNewBlock() after MN-startblock it calls FillBlockPayee()
(https://github.com/quark-project/quark/blob/f813e83ee229d9dce9f798051f96ca73f36d91f5/src/miner.cpp#L360)
where FillTreasuryPayee() is called
(https://github.com/quark-project/quark/blob/f813e83ee229d9dce9f798051f96ca73f36d91f5/src/masternode-payments.cpp#L304)
Two possibilities
Some people are using the new code to generate a lot of rewards for the foundation
(to create panic)
Unknown bugs have emerged as a result of mining along with the old chain during the upgrade
getblocktemplate reports wrong scaled values and wallet doesn't check max value for treasury
Any Idea where it's getting that magical number? (106,394.92616)
8 hours in seconds is 28800 times the MN reward 3.69416 is very close to the magical number 106391.808 Perhaps some rounding is involved.
QVvYypXoiRXcJpJpRVkftKEjMkXbd6UKJv
106,391.232 QRK
QirdV1H3Tikg12QefVkoFKrwkfHxT8EXia
3.69416 QRK
Re: [ANN] [QRK] Quark | POW+POS | 0.10.6.3 - New Self Moderated Thread
yes all hashes for block 7156400 are rejected:
last block was found:
kind of bad miner attack?
Code:
ERROR: ConnectBlock() : reward pays too much (actual=10639492616 vs Expected=371282)
InvalidChainFound: invalid block=00000000002a2e9dd5e1a56d4acf875ab8f501ae1d8113b588390dcbc062a475 height=7156400
InvalidChainFound: current best=0000000000329b2d94b233b0b473fbf506b51d2d250950059265cb80749feda1 height=7156399
InvalidChainFound: invalid block=00000000002a2e9dd5e1a56d4acf875ab8f501ae1d8113b588390dcbc062a475 height=7156400
InvalidChainFound: current best=0000000000329b2d94b233b0b473fbf506b51d2d250950059265cb80749feda1 height=7156399
last block was found:
Code:
2019-08-25 01:03:14 UpdateTip: new best=0000000000329b2d94b233b0b473fbf506b51d2d250950059265cb80749feda1 height=7156399
kind of bad miner attack?