Pages:
Author

Topic: [ANN] [QRK] Quark | POW/POS | 0.10.6.3 - New Self Moderated Thread - page 11. (Read 64318 times)

newbie
Activity: 59
Merit: 0
What's up with the template?

08:12:04

getblockcount
08:12:04

7243026
08:12:14

getblocktemplate
08:12:14

CreateNewBlock() : TestBlockValidity failed (code -1)


I guess it's best to turn this thing off and use the 3GB of memory for something else while we're being ignored.
newbie
Activity: 36
Merit: 0
What's up with the template?

08:12:04

getblockcount
08:12:04

7243026
08:12:14

getblocktemplate
08:12:14

CreateNewBlock() : TestBlockValidity failed (code -1)
newbie
Activity: 56
Merit: 0
The Blockchain worked for 2 hours and stucks now again at 7243026
jr. member
Activity: 180
Merit: 4
No new blocks since block 7242799 (more than 6 hours ago), the problems don't get smaller.


This is not a regular caton

It's all the mine pools down

Because the mine pool owner and is not near the computer, therefore could not restart the mine pool in time

But the arrival of the superblock caused the pool to go offline

We're still trying to figure out why
jr. member
Activity: 180
Merit: 4
The mine pool is offline for unknown reasons ( Related to the Treasury super block, the next one may be in a month, we will try to find the cause and fix it before then )
Subsequently caused the entire net wallet to get stuck at a height of 7242799
After the restart of the mine pool has been normal output block
Be sure to add the following node and restart the wallet to fix the card height problem
47.52.19.237
49.66.116.86
47.92.129.82
newbie
Activity: 56
Merit: 0
No new blocks since block 7242799 (more than 6 hours ago), the problems don't get smaller.
full member
Activity: 229
Merit: 100
Freiexchange contacted me earlier and i have passed on the details to the dev.
newbie
Activity: 36
Merit: 0
After running for 48 hours 3 masternodes now stuck on block 7242799 needing a restart to continue.

When restarting masternode:

23:53:04

Sync in progress. Must wait until sync is complete to start Masternode
newbie
Activity: 56
Merit: 0


Thanks for the answers.

The MN now seem to be running stable. Thanks for that!

But now unfortunately another annoyance comes, which was announced, where I already pointed out the problem and now do it again: 980 or 1000 confirmations for a transfer to the Exchanges is too long. I.e. a transfer takes 8-9 hours.

We actually wanted to set up a lot more QRK MN because we believe in the concept and history of QRK. But if we have to wait for 8-9 hours to sell the rewards , then unfortunately this is not interesting.  In this time the price can change so much, or Exchanges can suspend the transfer and the trade, that this becomes more and more incalculable beside the past problems.

FreiEXchange wrote that they do this only because of the recommendation of the QRK developers. Why don't you give advice to wait 5,000 or 10,000 confirmations? That would be much safer and nobody would trade or sell QRK again.

You can't pass your problem with hackers on to the community and pass it on to stakeholders.

Every problem will be solved
It takes time
Quark have lost a lot in it's long sleep

If there is something you feel you need to improve

You can leave a message.

We will enhance them in sequence
[/quote]

Unfortunately there are now problems with the transfers. First our transfer was not booked at FreiExchange. After the correction the coins cannot be transferred.

FreiExchange has set our wallet to "maintenance" and now wants to talk to your devs. You will understand that this does not increase our trust.
jr. member
Activity: 180
Merit: 4


Thanks for the answers.

The MN now seem to be running stable. Thanks for that!

But now unfortunately another annoyance comes, which was announced, where I already pointed out the problem and now do it again: 980 or 1000 confirmations for a transfer to the Exchanges is too long. I.e. a transfer takes 8-9 hours.

We actually wanted to set up a lot more QRK MN because we believe in the concept and history of QRK. But if we have to wait for 8-9 hours to sell the rewards , then unfortunately this is not interesting.  In this time the price can change so much, or Exchanges can suspend the transfer and the trade, that this becomes more and more incalculable beside the past problems.

FreiEXchange wrote that they do this only because of the recommendation of the QRK developers. Why don't you give advice to wait 5,000 or 10,000 confirmations? That would be much safer and nobody would trade or sell QRK again.

You can't pass your problem with hackers on to the community and pass it on to stakeholders.
[/quote]

Every problem will be solved
It takes time
Quark have lost a lot in it's long sleep

If there is something you feel you need to improve

You can leave a message.

We will enhance them in sequence
newbie
Activity: 36
Merit: 0
Wallets and Masternodes now stable for +36 Hours.
Can we have a response from AEX as to when Deposits and Withdrawals will resume? (with Sub 100 confirmations!)
full member
Activity: 229
Merit: 100
We have adviced our exchanges to reduce confirmations to between 50-100 for now.
The previous high number was just a precaution for a temporary period.
newbie
Activity: 56
Merit: 0
We have 15 QRK MN running, the behaviour is different. Some are running without problems, at some it helps to restart at other it comes to "Missing" and we have to wait for 2 hours until we get rewards again.

We also have many other MN of other coins running, where all these problems do not exist.

Please come to a solution and a version that runs without big problems. We accept that updates and changes can cause problems, but with QRK the problem will soon be normal. We thought that version 10.7.3 would solve the problem, but now there are problems again with the new version. So it might be understandable that people are slowly switching from 7.3 to 7.4.

I don't know how the developers designed it

But at present, I can't see the node 7.0/7.2/7.3 in my 7.4 wallet

I think it may need to be upgraded to 7.4 to stay on the main chain

Are you kidding me?

I changed all MN and my wallet to 7.4 less than one hour after the message came that there is a new version 7.4. I already wrote this several times. All MNs are configured the same and have the same peers, they are only in different countries (Europe, Asia and America). With version 7.3 there were hardly any problems, with version 7.4 there are again many problems.
Also from the beginning I only saw a part of my MN in the blockchain (https://chainz.cryptoid.info/qrk/#!network) under 7.4, although all MN are absolutely identical (except the private key of course).

I explained this all already before in other posts. So maybe you should ask your developers what the problem is and not declare us for idiots.


I believe this is a temporary problem caused by version switching

I mentioned the need for more than 51% of the new version consensus



Before POS is produced, 7.4 will have the problem of caton

However, after POS output, 7.4 is stable, while caton's is 7.3

I don't have any problems with the catons anymore

---
And 7.4 is our target (POW/POS+MN)



Thanks for the answers.

The MN now seem to be running stable. Thanks for that!

But now unfortunately another annoyance comes, which was announced, where I already pointed out the problem and now do it again: 980 or 1000 confirmations for a transfer to the Exchanges is too long. I.e. a transfer takes 8-9 hours.

We actually wanted to set up a lot more QRK MN because we believe in the concept and history of QRK. But if we have to wait for 8-9 hours to sell the rewards , then unfortunately this is not interesting.  In this time the price can change so much, or Exchanges can suspend the transfer and the trade, that this becomes more and more incalculable beside the past problems.

FreiEXchange wrote that they do this only because of the recommendation of the QRK developers. Why don't you give advice to wait 5,000 or 10,000 confirmations? That would be much safer and nobody would trade or sell QRK again.

You can't pass your problem with hackers on to the community and pass it on to stakeholders.
jr. member
Activity: 180
Merit: 4
We have 15 QRK MN running, the behaviour is different. Some are running without problems, at some it helps to restart at other it comes to "Missing" and we have to wait for 2 hours until we get rewards again.

We also have many other MN of other coins running, where all these problems do not exist.

Please come to a solution and a version that runs without big problems. We accept that updates and changes can cause problems, but with QRK the problem will soon be normal. We thought that version 10.7.3 would solve the problem, but now there are problems again with the new version. So it might be understandable that people are slowly switching from 7.3 to 7.4.

I don't know how the developers designed it

But at present, I can't see the node 7.0/7.2/7.3 in my 7.4 wallet

I think it may need to be upgraded to 7.4 to stay on the main chain

Are you kidding me?

I changed all MN and my wallet to 7.4 less than one hour after the message came that there is a new version 7.4. I already wrote this several times. All MNs are configured the same and have the same peers, they are only in different countries (Europe, Asia and America). With version 7.3 there were hardly any problems, with version 7.4 there are again many problems.
Also from the beginning I only saw a part of my MN in the blockchain (https://chainz.cryptoid.info/qrk/#!network) under 7.4, although all MN are absolutely identical (except the private key of course).

I explained this all already before in other posts. So maybe you should ask your developers what the problem is and not declare us for idiots.


I believe this is a temporary problem caused by version switching

I mentioned the need for more than 51% of the new version consensus



Before POS is produced, 7.4 will have the problem of caton

However, after POS output, 7.4 is stable, while caton's is 7.3

I don't have any problems with the catons anymore

---
And 7.4 is our target (POW/POS+MN)

newbie
Activity: 56
Merit: 0
Three 0.10.7.4 masternodes synchronized and stable for 12 hours. 79 Masternodes Visible.
The reducing connection count on Quark explorer could be an indication of the load being distributed more evenly through the network.

Yeah, now also our masternodes ran all night without any problems.

Only the rewards are decreased, because of the increase of the number of masternodes. But here are too often too many problems and the developers don't really seem to know why.  And for these problems, the ROI is getting to low now. There are more exciting masternodes.
newbie
Activity: 36
Merit: 0
Three 0.10.7.4 masternodes synchronized and stable for 12 hours. 79 Masternodes Visible.
The reducing connection count on Quark explorer could be an indication of the load being distributed more evenly through the network.
newbie
Activity: 12
Merit: 0
FYI, left the wallet open 24hrs and the wallet did not synchronize!
thats with 0.10.7.4!

had to reboot to sync it... pls fix this...
newbie
Activity: 56
Merit: 0
We have 15 QRK MN running, the behaviour is different. Some are running without problems, at some it helps to restart at other it comes to "Missing" and we have to wait for 2 hours until we get rewards again.

We also have many other MN of other coins running, where all these problems do not exist.

Please come to a solution and a version that runs without big problems. We accept that updates and changes can cause problems, but with QRK the problem will soon be normal. We thought that version 10.7.3 would solve the problem, but now there are problems again with the new version. So it might be understandable that people are slowly switching from 7.3 to 7.4.

I don't know how the developers designed it

But at present, I can't see the node 7.0/7.2/7.3 in my 7.4 wallet

I think it may need to be upgraded to 7.4 to stay on the main chain

Are you kidding me?

I changed all MN and my wallet to 7.4 less than one hour after the message came that there is a new version 7.4. I already wrote this several times. All MNs are configured the same and have the same peers, they are only in different countries (Europe, Asia and America). With version 7.3 there were hardly any problems, with version 7.4 there are again many problems.
Also from the beginning I only saw a part of my MN in the blockchain (https://chainz.cryptoid.info/qrk/#!network) under 7.4, although all MN are absolutely identical (except the private key of course).

I explained this all already before in other posts. So maybe you should ask your developers what the problem is and not declare us for idiots.
jr. member
Activity: 180
Merit: 4
We have 15 QRK MN running, the behaviour is different. Some are running without problems, at some it helps to restart at other it comes to "Missing" and we have to wait for 2 hours until we get rewards again.

We also have many other MN of other coins running, where all these problems do not exist.

Please come to a solution and a version that runs without big problems. We accept that updates and changes can cause problems, but with QRK the problem will soon be normal. We thought that version 10.7.3 would solve the problem, but now there are problems again with the new version. So it might be understandable that people are slowly switching from 7.3 to 7.4.

I don't know how the developers designed it

But at present, I can't see the node 7.0/7.2/7.3 in my 7.4 wallet

I think it may need to be upgraded to 7.4 to stay on the main chain
newbie
Activity: 56
Merit: 0
We have 15 QRK MN running, the behaviour is different. Some are running without problems, at some it helps to restart at other it comes to "Missing" and we have to wait for 2 hours until we get rewards again.

We also have many other MN of other coins running, where all these problems do not exist.

Please come to a solution and a version that runs without big problems. We accept that updates and changes can cause problems, but with QRK the problem will soon be normal. We thought that version 10.7.3 would solve the problem, but now there are problems again with the new version. So it might be understandable that people are slowly switching from 7.3 to 7.4.
Pages:
Jump to: