Problem with getblocktemplate on testnet #245
Comments
|
Hello wiiiteek. Testnet is absolutely working. I have been mining about 99% of the testnet blocks for most of this year. What DigiByte version are you running? |
|
Hi, I am running latest Here are node logs |
|
If you are running 7.17.3 you will need to manually add another node to connect to, since the old seed servers are all offline. I would recommend running 8.22.0-rc4 which has solved this issue. |
|
Ok, with |
|
@wiiiteek Am I correct that you have gotten mining working? I appear to be getting only 60% of the blocks now. |
Other new blocks are skein blocks we are having loads of issues with. We have been working to set up testnet nodes and test mine on DigiHash. It appears testnet was never set up properly this last time and is throwing unknown version bit errors. There are lots of issues mining odo/ skein/ qubit which is why it appears only sha and script were getting mined. The soft forks/ hard forks were not executed in the correct steps. Also with 3 million + blocks, sync times are way too long for testing now. So for many reasons, it's time to reset the testnet and start over. We need to tweak several testnet settings. I was told others had test-mined all 5 algos on previous 8.22 versions, but that does not appear to be the case. It's all good, we will just need a group effort to get tesnet reset and these bugs sorted. It's important to have all 5 mining algos continuously mined on testnet if we are going to keep testnet going. I should also mention to anyone looking to use testnet, outside of mining testing and p2p issues testing all of your test needs can be done with reg test. Reg test will fulfill 99% of any issues trying to build on top of DGB. Bitcoin devs had tons of issues with testnet like we are which is why regtest was created.
https://developer.bitcoin.org/examples/testing.html
|
Also I did not realize you were the one keeping testnet alive. Thank you for that and thanks for helping keep it going for people to test. We will try and get a couple more CPU miners and a testnet mining pool for all 5 algos on digihash moving forward to support community testing. |
|
What is absolutely mind boggling is we are mining skein blocks that get added to the testnet chain yet the 8.22 RC4 digibyted rejects the skein blocks as invalid, no funds are sent to reward wallet, or held in pool wallet and 8.22 RC4 client rejects the mined blocks. Yet the blocks are still added to the chain and it keeps incrementing. So 100% this is a testnet consensus rules issue as we testmined Skien, qubit on main net with 8.22 RC4 just fine.
Just restarted skein miner again to debug, running my stats site on testnet locally is kinda handy:
|
|
@JaredTate Yes, I had been mining sha256, scrypt, and skein for quite a while. Skein stopped a little while back when I had a power outage. I previously had mined all 5 algos by manually switching my miner periodically. Right now I just mined a few skein blocks and a couple odo blocks. And now a handful of Qubit blocks. |
Thanks for doing that, I know that's a big hassle to keep that many miners going on testnet. I was under the impression a few people were doing that to help, not just 1 person. We can start from now on to help out. We can get 2-3 more of us to run a CPU miner. Here is where we are setting the 5 testmining algos up on digihash. https://digihash.digibyte.io/ What wallet version are you mining with @beggsdl? I assume you are mining straight to your wallet? Trying to debug this version bit 6 issue on testnet. See if we can't do an easier reset of it than a full blown testnet reset. Thanks for helping us debug this. We also want to double-check check we don't have any 8.22 issues with odo as we can't seem to mine an 8.22 RC4 odo block on main net. This will also help us debug digihash pool too. Cheers |
I see the other blocks now, are you mining on 8.22 RC4? Or 7.17.3? We may have an issue with digihash pool... very strange behavior, but that still would not explain the error in the 8.22 rc4 testnet client itself. |
|
I have to check the version on my Linux box where I mined the odo, qubit, and skein blocks. I know it is 8.22.x, just not positive if it’s rc4 or not. My Windows machine mining scrypt and sha256 is rc4. |
Ok good to know, our issue could be DigiHash... very strange though. Are you getting the version bits warning? I am getting it on 3 separate 8.22 RC4 test wallets now. We are going to try to test mine sha, scrypt and qubit through pool here in a bit when they finish syncing. Try and get a block on all 5 algos. Something in testnet consensus rules appears off vs main net. Looking through the previous soft forks testnet code they may not have been ran through in correct order when testnet was reset the last time. |
Yes, I do see the version bits warning. I have I think at least since we fixed that split chain issue around Christmas/New Year’s. |
That could be another reason to reset the testnet chain. It may go away if we get 8.22 RC4 mining all 5 algos for a bit. Will have to try it. Just curious if we have an older client mining a bunch of blocks still. More importantly, it is good to double-check check there is still not another issue in 8.22 to flush out. So I will keep debuggingg. |
That response is part of our DigiHash test mining issue, could be related to the version bits warning clients are showing. |
|
I am confident older versions are not mining a bunch of blocks. I’ve been getting >99% of blocks for quite a while. Every once in a while, I will notice one block that I did not get. Then today someone else started getting a good portion of the blocks. May you? |
Yes, it was us with Skein, but then as mentioned above... serious errors with them. Very perplexing. Nothing was showing up in the wallet but blocks still getting added to the chain. |
|
I think we got some of the DigiHash pool issues sorted... getting some Tesnet sha256 blocks now with 8.22 RC4.
|
Nice! Glad to see things are starting to get sorted out. |
|
Ok we just test mined qubit, scrypt, sha256, skein on tesnet with 8.22 RC4 through digihash pool... it is mostly pool issues causing problems, but still have some consensus issues on testnet to debug. Will keep debugging and report back. Can't get odo to fire yet.
|
Hi,
When I am running node on test chain (
./digibyted -testnet) I cant generate block template for mining. I am receiving errorBut node seems to run OK, because other method
getmininginfofor example returns this dataalso test chain seems to be empty because on node logs there is only one block with heigh=0
Is there something wrong with my setup or maybe DigiByte does not have a working testnet chain?
The text was updated successfully, but these errors were encountered: