Opened issue https://github.com/PoC-Consortium/burstcoin/issues/252
Maybe you can add your findings /log - I lost mine when the wallet restarted.

I don't think it is actually forking... maybe it is resyncing or something. The warnings are not very descriptive to me and it is unclear what is happening. Don't have this with the 1.3.6cg version.
I'm running on windows, and the OS does not change the blockchain as there is only one.

I want to add, I also get the fork warning in the 2.0.4 wallet.
Every now and then. I don't know the reason, I googled a bit, but this is the first time I have seen someone mentioning this.

I was solo mining before and switched to pool after upgrading to 2.0.4 so I can't say If it causes problems for me. It is also a reason why I did not switch to solo again (was afarid it could be a problem). Is the POCC aware of this behaviour or should we open an issue on github?

Like BurnMe I want to support dymaxion, but I'd also like to mine with the local wallet again...

With 100GB you won't get any useable deadlines. Check the deadline setting in the config, maybe set it to maximum. It will not help you with mining, but you will see if it works (submits a DL) from time to time.

Wow, the new 1.8.0 Web Gui is looking awesome!
I have one issue where I scroll in the cmd window and it stops displaying stuff, but I like the new features. I will definitely give the new one a try.

Question:
In the Wiki it states the following:
The miner will parse the paths and will create for every partitions (C:, D:, ...) a separate thread for reading. This is done for performance reasons.

Now, if I use Mountpoints in Windows, the path will be simmilar like C:\mount\drive1,C:\mount\drive2,...
Will creepminer still create seperate threads for these paths?

@brandonprasnick
calm down...
first step, get your wallet running. It needs to be in sync to be of any use.
I use the standalone wallet; otherwise use qbundle. I would recommend to use mariadb as it is much faster and more stable.
Then get your miner to work with solo mining. when you see that is working as you want - then change to a pool.

I'm sending you a couple burst, but please make sure your setup is running ok before you configure the pool/reward assignment.

@brandonprasnick
You only do the reward assignment when you want to change it. it is your account by default.
Your deadline is what you see in the miner console, what it is submitting. It varies for each block. I guess you should make sure that most of your submitted DL's are les than the max allowed pool deadline.
The Deadline in the .conf is the maximum the miner will submit. you set this to the max pool deadline if you mine in a pool. If you mine solo it does not matter much.

@nonobrutale1090 said in The Burst Core Roadmap for 2018 - the integration of the Dymaxion proposals:

Also you advise to use qbundle instead of the AIO. Why is that ? The burst client wallet and the jar that comes with it is the AIO right?

The AIO is version is quite old if I'm not mistaken. You should use the latest wallet version; the qbundle has that version.

Guys... :D