After the hardfork
Can anyone summarize what will and won't work after the hard fork?
old plot files optimized
old plot file unoptimized
@luxe , so that wiki says 1.29 etc, anything under 2xx will be "obsolete". Does that mean that it won't communicate with the 2xx wallets or that POCC would like everyone to be off of pre 2xx wallets, however if your're not the wallet may still work. If it won't work, why won't it work?
Gibsalot last edited by
@rds the issue will be that the old wallets will not have any of the new fetures , and even if they load up and display correctly most likley will not communicate properly
@gibsalot , so new feature or not will it still be able to submit a DL to the network and send/receive burstcoin?
Gibsalot last edited by
@rds im not sure if it will be able to or not. my advice is to just upgrade to the newest wallet to make sure you can
@gibsalot , with respect, that's the sheeple answer, I was looking for the technical answer.
crutsy last edited by
@rds the answer is no. 1.2.9 does not have poc2 support.
@crutsy , what if you don't convert your plotfiles to POC2? I read conversion to POC2 was an option but not a requirement.
Will the Blago miner still work after the HF?
@rds the fork will change the rules ... when blocks/transactions are valid ... why would you not want to update?
@luxe , I'm not saying I don't want to update. I'm trying to understand the relationships between the old and new.
I heard POC2 will have some kind of dynamic HDD space allocation. Do I want someone's data stored on my drive? Is it like STORJ/Sia?
Energy last edited by
@rds I think you mean the price of transactions that no longer 1 Burst as now, for dynamic HDD space it would not make sense to create the plots
@rds No, POC2 is the same data stored on other parts of a drive. For a legit miner, not much does change. But rearrange data is needed to get same performance than before. POC3 will mabe store data in the future, but thats optional.
You can also contain using POC1 but your round-times will double. (Double data needs* to be read by miner ... )
*in detail thats not true but reading 2 big sequentiel blocks is faster than let the read-head jump every 32bytes
@luxe , thank you for that. One more thing. Does the current Blago miner integrate into the HF for solo mining if using the correct wallet?
@rds All 'old' miners will work with POC2 plotfiles after the fork, but for still being compatible with POC1 changes need to be made. Quite sure there will be such a version e.g. https://github.com/Quibus-burst/miner-burst seams to work on it.
@luxe , will all the old pool codes work after the HF or will these codes need to be modified. Specifically the CRK fork of the Lex pool?
Will the existing CRK code work if it's using the upgraded wallet (2.xx)?
@rds pool code should work if backed by new wallet, however, pools not using new features like 'sendMoneyMulti' or dynamic fees for payouts will not serve their miners well.
In the best case, a pool only needs 0.00735 BURST to payout to 64 miners.
So i guess some improvements to all pool codes should be made ...
@luxe , I just saw the 2.2.0 wallet was released. How do you get it running in a windows environment? I double clicked burst.cmd and it started for a second then shut down.
@rds Add a "pause" command to the end of the .cmd file, or run it from a DOS prompt - see why it's erroring.
Did you just extract the .zip into a working wallet directory ?
rds last edited by haitch
@haitch , would this be the problem? The config file for the new 2.2.0 says maria.db. I believe my old wallet was h2? So I would rather not download a new db. What goes in the config file to make it like my old db?
# Database connection JDBC url
# Append ;AUTO_SERVER=TRUE to enable automatic mixed mode access.