Thx. With the new wallet (after manually choosing the external node because it's not set by default as described) the balance immediately shows up correctly. The daemon itself  still does not seem to sync correctly, so for now I will just stick to the external one.

So I tested 1.1.2.6 on my two Windows machines (old Thinkpad Win7, newer Xeon Win10). Here's what I see so far:

1. The startup is indeed much faster without the "memorizing prayers" step. Nice work there.
2. After the wallet opened there is a longer period of time with huge CPU utilization. This is the "memorizing prayers" step I suppose?
3. I immediately got the CPID errors mentioned by thesnat.
4. The self-payment Rob suggested helped this error for approx. 1 minute, then it returned.
5. The errors are independent of OS and occur on both pools (main pool and purepool) alike.

Hope this helps a bit.



Edit: Well, that's strange. On my Win10-Xeon it seems to have sorted itself out after maybe 10 minutes and is now submitting solutions as usual. On the Win7-Thinkpad getmininginfo is still full of CPID errors.

Ah well, I found the error. Apparently the single task is obligatory, that means you HAVE TO USE "-t 1". Everything else results in multiple solutions and errors.
So for the new solo cluster we have to (in the optimum case) run 1 instance for every CPU core? Does every instance need a different ROI address?

Furthermore I'm a bit confused about the hash rate. I know it's a test cluster, but the miner says "0.05 h/s" for every task. Is that normal? Under Windows it's a bit higher, but still ridiculously low.



Edit: Server seems to be down now, cannot establish connection.

I just tried it and the miners do connect, but I have no idea how to configure them. On windows I get approx. 10% accepted shares, on Linux it's below 5%, so completely useless. Are there updates for the hodlminer? What is the recommended way to mine with multiple instances?

(hodlminer and scripts are the exact same versions that worked perfectly on the old solo-cluster).

It seems like since the fork the daemon has some hickups. It often switches between "synced" and "xxx blocks behind" and I think the reason is, that there are still "old" nodes in the network.
Is there any way to either auto-ban nodes that are on a wrong version OR have the daemon start with a reliable up-to-date node in exclusive mode (maybe through something like --add-exclusive-node [IP])?

Thank you very much for the clarification. That's all I wanted to hear.

Well, seems like I spoke too soon. After closing the wallet, the GUI cannot open it again, only giving the following error:.
I also realized, that the GUI wallet asked for a folder to place the wallet file in, but it didn't write anything to that folder. Restoring from seed works of course, but it would be tedious to always do that again...


Edit: found the solution myself, although it's really weird. Apparently you musn't change the default folder for the wallet storage when asked. So after letting the GUI create the wallet file in "my documents", I closed it, moved the created file to another folder, opened the GUI again and then opened the created wallet file from the other folder. Now it works.

Also: is there a setting to lower the "countdown" to the daemon start? Dunno what those 10 seconds are for...

I just updated the GUI Windows wallet to 0.2.4. I had to restore the wallet from the seed and after that it was smooth sailing. Syncing and rescanning took only a couple of minutes, all my balance is back, and the GUI looks and "feels" very nice.

Awesome work!

Ah I see, thanks for clearing that up. I was just wondering, because I could have sworn I had these 4024 for days now^^.

Awesome! I was always wondering if that process could be sped up somehow. Especially on the Rapsberry Pi this took ages.

So you received a PODC payment just now on block 50635? That's good news. This means that now your magnitude is >0 and the system should start accepting your shares in POW (heat mining) again. Just wait for a couple of blocks (or maybe hours) and see if your shares start rising on the pool. Errors on purepool are accumulated over 24 hours, so those will diminish slowly until tomorrow.
If the heat mining still doesn't work, check if your wallets are unlocked. You can easily see this with "getmininginfo", there should be "submitting solution" in the poolinfo and nothing like "invalid CPID" etc.

Well, it's not that simple actually (that's why I wrote "on windows"). Windows takes up several hundered MB of GPU RAM (at least on the GPU where the screens are connected to). So my question was, how "hard" the limit of 2.5 GB is and how it is reflected in GPU RAM consumption.

Or in other words: The ETH DAG is at approx. 2.4 GB right now, but ETH is definitely not minable on 3GB cards on Windows anymore (in contrast to Linux and of course headless systems).

I hope I expressed this clearer now.

@ Rob: Again, I don't think the WCG mags are diminished the way they should. I cannot see any changes for the last 3 superblocks now.

That's the most hillarious calculation I have ever seen.

On a serious note: I just took a look at the vieo with the explanations. One thing that caught my eye was the 2.5 GB mem requirement. Does that mean that I cannot mine BTCZ on windows with my 1060 3GB card anymore?

What? Why? That makes no sense. With this you are telling this client that you want to specifically stake 1 BBP! utxooverride is not a Boolean but an actual absolute value. That means for your "controller wallet" you have to either leave out this line completely OR set it to the amount of BBP you want to stake for PODC (e.g. 20000).

Has anyone ever heard of this exchange? "BitexLIVE". It seems to be a new guy in town, located in Turkey, and there seem to be a lot of small coins already registered.
I couldn't find anything about the coin registration fees they might or might not have, but it looks like someone "official" of BBP can easily apply here:
https://bitexlive.com/addcoin

Lol, this was a perfectly understandable, simple answer (although I don't know if the telegram is really the up-to-date channel for BBP...). Perhaps you should improve your reading comprehension skills instead of criticizing other's posts.


@Rob: Could you please check the MAG adjustment for WCG? I don't think it had any effect the last two days (or maybe my memory has tricked me).

Edit: Ah maybe it's just because the superblock view still shows 50225, so nevermind^^.

Thank you for your reply. However this is not what the problem is here. My wallet.dat is perfectly allright, it works and syncs just fine on other PCs (running Win7). The problem is, that my main PC (Windows 10) won't start the QT application at all. As soon as I start lux-qt.exe it very briefly shows a blank window in the size of the start-splash and then closes itself again. This happens with a clean LUX folder in Roaming as well as with a fully synced one, in compatibility mode, in "run-as-administrator"-mode etc. I have no chance of opening the GUI on this PC; all that happens is that it puts the above mentioned lines into debug.log

P.S.: I'm really excited about all the things down the road. Keep up the good work!

Nice work, thanks. Didn't know about the SPARC connection (or about SPARC for that matter^^) and just completed the connection. Let's see how this works out. :-D

The repository (i.e. the Ubuntu binaries) are not out yet for Ubuntu 18.04. Lichtsucher (the guy making them) ran into compilation troubles for 18.04 and is working on fixing them. I'm not sure if in the meantime it's possible to compile it from source, but I'm pretty sure you would have to have some Linux skills to circumvent any incompatibilities. Here's the old bash script for the compilation:
https://gist.github.com/anonymous/d1c1d35e3c8f67f5fb2e204479fa5c6b

Also this might help:
https://www.reddit.com/r/BiblePay/comments/6ummuj/how_to_mine_biblepay_on_linux/


@Rob: So IBM lawyers have been working "for months" on those 2 sheets of paper? Haha, sure! It's not that this agreement and the date hasn't been known for more than 2 years...

Hello all. I have the exact same problem on Windows 10. The GUI wallet worked perfectly until yesterday, but today it won't start and just leaves the above mentioned errors in the log. Was there ever a solution to this?