|
There are still things like jamming the network and causing a lag
Any wallet can happen
Currently, the repair can only be done by restarting the wallet
For those with technical skills, try writing an extra daemon to help detect the height and restart the wallet
Once development is back to work, we will try to find and fix the problem as soon as possible
It could take two weeks or more
|
|
|
|
I have three masternodes stuck at 7282818, Restart Required.
Stuck again at 7283336 and again 7283563 This may be due to the presence of some version or older version in the network First make sure you are 0.10.7.4 Then You can then search the Explorer for some nodes to add to the quarkcoin.conf file |
|
|
|
I uploaded a block file of renidex When you're asked to type txindex=1 It will be available This saves time in setting up the masternode https://mega.nz/#!P7IETAQL!y687XXNYaPE8hbgkhXYJWAN05ajoE6xJjeM_Qa-fX-o （renidex） ------------- In addition to paste again regular block data https://mega.nz/#!Xy4VCKJR!3VbR-HzV2VDnmNG0tgQTYfa72Gs3EtOsAvugx_e-y5Y （normal） |
|
|
|
Answer from FreiExchange when I asked for the whereabouts of our 9950 QRK, which we wanted to transfer almost 3 days ago: Hi
Currently we have to wait, if the conflicts resolves, the transactions will be picked up in the memopool.
There was a few transactions comming in after we put the hot wallet in service mode and those transactions came in with conflicts.
Biggest issue is that when you check on the connecting peers
"synced_headers" : 7247885,
"synced_blocks" : 7242632,
They are all stuck on block ~632 but headers are much higher. I also tested with the connection ip nuttynoah on bitcointalk with no luck either, we are still stuck on the ~2632 block.
If the transactions goes away from the mempool, we will re-issue it so that none of your coins are lost, but atm i think the devs are not quite sure what to do. I have not heard back from them after i raised the question the other day when you where first in touch.
The support of FreiExchange at least does a good job. Now the whole network is back up There is no need to connect to the three provided nodes Just connect to any higher node and restart the wallet to fix the caton If it still cannot be updated, I think they need to download block data again or download part of block using the connection provided by us https://mega.nz/#!Xy4VCKJR!3VbR-HzV2VDnmNG0tgQTYfa72Gs3EtOsAvugx_e-y5Y Can you tell them this |
|
|
|
|
In the case of network problems
Only two things are needed to keep moving forward
1. Connect to the node at the latest height
2. Restart the wallet
This problem will eventually be solved, but for the time being we still need to be in such an environment
|
|
|
|
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 |
|
|
|
|
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
|
|
|
|
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 |
|
|
|
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) |
|
|
|
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 |
|
|
|
0.17.0.3 worked stable, with 0.17.0.4 there are again problems. The wallets loose over the day 3-4 times their blockchain. There are already more than 51% nodes 0.17.0.4 in the chain, but not all are correct recognized. And there are again crashing wallets, not so often like with 0.17.0.1, but it happens again.
And MN is always online, but only sometime got rewards. in 7.3 MN rewards was good, continous. In 7.4 not continous... Yes, we have the same problem. When my wallet gets stuck though I need to reboot But my MN didn't go down My rewards were still allocated to me on time |
|
|
|
0.17.0.3 worked stable, with 0.17.0.4 there are again problems. The wallets loose over the day 3-4 times their blockchain. There are already more than 51% nodes 0.17.0.4 in the chain, but not all are correct recognized. And there are again crashing wallets, not so often like with 0.17.0.1, but it happens again.
So far we haven't seen any crashes on our side But it will get stuck at a certain height and need to restart the wallet to fix it The reason for this phenomenon may be that the output POS is stuck I generated 1 POS block But it got stuck on one confirmation It has not been accepted on the net Using 7.4 is still not enough Many people are still using 7.3 Need to see more time |
|
|
|
They erased the link I listed. I'm talking about the Quark Website listed on Coinmarket Cap. If you listed it there you would get much more traffic. If I down load it and install will I be able to synch the wallet? We are continually trying to notify these listing sites, they are proving difficult to get in contact with and update their records. If you download the latest version you will be able to synch the wallet. You can always add the latest nodes list from cryptoid blockchain explorer which is up to date. Here: https://chainz.cryptoid.info/qrk/#!network I downloaded v0.10.7.4 (3 weeks behind No Block Source Available)........... WTF? Some unknown reason may cause the card to be stuck at this height You can remove blocks and reload them Some of these blocks can be downloaded here https://mega.nz/#!Xy4VCKJR!3VbR-HzV2VDnmNG0tgQTYfa72Gs3EtOsAvugx_e-y5Y In addition, if you cannot connect to the node, you can view it in Explorer and add some |
|
|
|
Quark 0.10.7.4 released Fix POS bug Need to be replaced network more than 51% of the wallets to 0.10.7.4 to start agreement Please change to 0.10.7.4 as soon as possible Because the code needs to be updated in a few days I temporarily used the connection of 0.10.7.3 The compiled version is 0.10.7.4 https://github.com/quark-project-evolution/quark/releases/tag/v0.10.7.3Thanks, I like QRK more and more. If now AEX also reactivates trading, everything is perfect. We have changed our MN to 0.10.7.4, everything works perfectly and from the feeling the wallets start faster. When enough supporters use 0.10.7.4 POS can produce correctly AEX will then be open for deposits and withdrawals |
|
|
|
downloaded the zip file but again "no blocks source available".. do i need to enter all the "add nodes" again?
Usually I add it to Quarkcoin.conf |
|
|
|
Quark 0.10.7.4 released Fix POS bug Need to be replaced network more than 51% of the wallets to 0.10.7.4 to start agreement Please change to 0.10.7.4 as soon as possible Because the code needs to be updated in a few days I temporarily used the connection of 0.10.7.3 The compiled version is 0.10.7.4 https://github.com/quark-project-evolution/quark/releases/tag/v0.10.7.3Great !! How this latest release effect on MN's owners ? Do we need to upgrade MN's wallet 0.10.7.3 to 0.10.7.4 too... Thanks yes upgrade to 0.10.7.4 We need enough proportion to start POS |
|
|
|
Quark 0.10.7.4 released Fix POS bug Need to be replaced network more than 51% of the wallets to 0.10.7.4 to start agreement Please change to 0.10.7.4 as soon as possible Because the code needs to be updated in a few days I temporarily used the connection of 0.10.7.3 The compiled version is 0.10.7.4 https://github.com/quark-project-evolution/quark/releases/tag/v0.10.7.3 |
|
|
|
|
Show Posts
