-
Notifications
You must be signed in to change notification settings - Fork 212
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zawy LWMA difficulty algorithm issue #80
Comments
Do not use any ZAWY_LWMA_DIFFICULTY parameters on production coins until they are tested and confirmed they produce correct results. The current implementation is just for testing only. Also, since there are a lot of parameters in the "dev" state - usually there is a description in the extension file, telling the extension is still in development |
Ok then what is your suggestion right now ? |
Is the hashrate of your network real? If you think it's real, just change 100000 to 1 |
can i disable ZAWY_LWMA_DIFFICULTY ? and use const uint32_t ZAWY_LWMA2_DIFFICULTY_BLOCK_INDEX = 13350 |
Yes you can. Add this line at the block you want to disable it: |
i did this on my private blockchain and now blocks are generated on a second or less. the time correct is 120 seconds. |
Any news about LWMA ?? Please help :( |
Hi
I added Zawy LWMA difficulty algorithm on block 83001 and since that block my difficulty is show 100000 all the time....
If you take a look on block explorer
Block 83000 before fork
http://bce.deutercoin.uk/?hash=fab2cc49baef66224a04f432c51e037baf21d6f529499b39c8d4837256fa61ac#blockchain_block
Difficulty: 22198243
and next block 83001 after fork
http://bce.deutercoin.uk/?hash=b7d9bf01ee02e9f8f1576546fb42aa6445f488d66e33a08955438a198a62a61f#blockchain_block
Difficulty: 100000
in CryptoNoteConfig.h parameter
const size_t ZAWY_LWMA_DIFFICULTY_N = 60;
I know then in this algorithm if difficulty is lower then 100000 it will be 100000 but was 22 millions and now all the time is 100000 :(
// minimum limit
if (next_difficulty < 100000) {
next_difficulty = 100000;
}
What can be wrong ???
Regards
The text was updated successfully, but these errors were encountered: