@zapbuzz Glad to hear, for me the lastest release is not 100% stable yet .. but i'm monitoring and working on it.

@cryptonick You should maybe report your issue here https://github.com/JohnnyFFM/miner-burst/issues ... for now you maybe need to run 2 computers independent of each other, witch is no problem for solo mining. 2x miner 2x wallet no proxy.

@juasker POC2 is active since block 502000 ... Still mining POC1 plotfiles means double the data needs to be read, also the convert POC1->POC2 requires more CPU and memory (thats why your old chunkPartNonces setting does not work anymore) ... you will need to convert your plotfiles, to change behaviour back to pre-fork. Please check https://burstforum.net/topic/9185/hard-fork-resources-everything-a-happy-burster-needs!

From jminer 0.5.x release Notice:
Supports both, POC1 and POC2 plotfiles. This will also be the case after the fork.
However, to handle POC2 pre-fork and POC1 post-fork, twice the amount of data needs to be read and also more CPU and memory resources will be used. The best case for a miner would be, to have converted up to 50% of plotfiles once the fork happens. That would cause the mining setup to behave exactly the same pre and post fork.

@burnme I understand very well what you talk about. And i agree that a application doing the math you need would be helpful in your case ... but thats nothing to build in wallet. The walllet provides a interface for such kind of 3rd party apps, delivering all information needed. (http://localhost:8125/test)
In your case you should maybe define exactly what you need and find a developer programming it for you, if you just have to handle one country tax law and you have access to burst price in your tax currency by transaction timestamp ... it is not that big deal to plot out a excel sheet for a specific burst account. Writing a general app that fits the need of all and all special cases is much harder.

The whole aspect you describe will be a big issue in the future ... tax and crypto just don't work together very well, as crypto is not bound to identity like fiat ... a lot of current laws just don't work with crypto. It is quite amusing, if i pass a border, i may only take a given amount of cash with me. But considering that crypto is cash, and i have my 'private keys' with me, i break the law, every time i cross a border. I have accepted that i'm a money launderer and terrorist for the authorities ... hope you find a way to not get criminalized by reporting every single crypto transaction with all related data, like timestamp, exchange price in fiat, source/recipient ID etc. ;-)

@haitch said in Wow!:

@gpedro I believe the jMiner dynamicDeadline performs the PoCC calculation for you and uses it as the target DL.

exactly (but i still have no clue why this is needed by the pool, maybe just because everything above gets ignored anyway?)

@energy good question, i have no idea :-) somehow the pool calculates your 'effective capacity' by the deadlines you commit ... why a special calculated target deadline should hellp with that ... i do not know.

Edit: from a miner perspective ... i just deliver what they want ... and do not ask why :-)

@energy sure the capacity of the pool influences the network, but the capacity the pool calculates from your submitted deadlines just affect your shares. for now maybe just wait another 24h, maybe it re-adjusts ... else check 'Quick Info' tab/section on your pool page. Not sure about other mining software, in jminer you can just set 'dynamicTargetDeadline=true' to auto apply the pool formula.

@ranger64 you have noticed the poc1->poc2 change yesterday? you need to at least update your miner and consider converting your plot files to poc2 ... https://burstforum.net/topic/9185/hard-fork-resources-everything-a-happy-burster-needs

@energy not sure, are you talking about what your pool tells you? that has nothing to do with network size, maybe you just need to adjust your targetDeadline ?

@bluebook Always remember that the value of a coin is related to the difficulty mining it. So i wouldn't be too happy, if it turns out that the real capacity was lower than expected. But surely it is even worse for the value of a coin if it has flaws. Very interesting times ...