AwesomeMiner Coin Updater *Version 1.0.0* (Plugin)

[soothaa]

Yep, I took a closer look. The plugin is using average nethash to calculate profit and send BTC per MH value to Awesome miner.

This is correct.

Then the profit calc wont match WTM calculation and if you are using Awesom miner with mixed calculated coins (WTM and plugin) it wont be effective. To make it correct you need to calc the profitability based on the average diff for the last 24h.

I'll look at changing it. In the middle of cleaning up my Masternode Plugin for release at the moment.

[1715052522]

1715052522

[1715052522]

1715052522

[1715052522]

1715052522

[ruplikminer]

Yep, I took a closer look. The plugin is using average nethash to calculate profit and send BTC per MH value to Awesome miner.

This is correct.

Then the profit calc wont match WTM calculation and if you are using Awesom miner with mixed calculated coins (WTM and plugin) it wont be effective. To make it correct you need to calc the profitability based on the average diff for the last 24h.

I'll look at changing it. In the middle of cleaning up my Masternode Plugin for release at the moment.

Hi buddy thanks for this amazing plugin. I have a question

when you set the profitability of hte coin, where do I find the MH/day BTC profit of that coin?

[ruplikminer]

Also I receive this error when I launch the plugin: http://prntscr.com/ihk2sg

transalted means "ERROR: INTPU STRING FORMAT NOT CORRECT". how can I fix it?

[ruplikminer]

Any news on this?

[soothaa]

AwesomeMiner Coin Updater 0.2 (Requires AwesomeMiner 4.4.7 Dev or 4.5 Release)

• Changed away from nethash to difficulty measurements (delete your LocalCoinData.json file)
• Now updates all coin properties thanks to new AwesomeMiner HTTP APIs
• You no longer have to add custom coins, they are created for you thanks to new AwesomeMiner HTTP APIs
• Updated config.json to support these new changes. You MUST update your custom coins to the new format.
• Made the error messages more obvious about what is going on

You can find the latest update in the Mega link.

[ruplikminer]

AwesomeMiner Coin Updater 0.2 (Requires AwesomeMiner 4.4.7 Dev or 4.5 Release)

• Changed away from nethash to difficulty measurements (delete your LocalCoinData.json file)
• Now updates all coin properties thanks to new AwesomeMiner HTTP APIs
• You no longer have to add custom coins, they are created for you thanks to new AwesomeMiner HTTP APIs
• Updated config.json to support these new changes. You MUST update your custom coins to the new format.
• Made the error messages more obvious about what is going on

You can find the latest update in the Mega link.

thanks for the update!

[Seanklei10]

This plugin has been working great so far. I'm adding more coins, however does the plugin only work with Iquidus or CryptoNote explorer types? Is there any way to add additional? I have an explorer that provides an output that looks like:

{"version":2000000,"protocolversion":70210,"walletversion":61000,"balance":0,"privatesend_balance":0,"blocks":27908,"timeoffset":0,"connections":8,"proxy":"","difficulty":15543.04838902299,"testnet":false,"keypoololdest":1518367199,"keypoolsize":999,"paytxfee":0,"relayfee":1.0e-8,"errors":""}

https://curve.uexplorer.me/api/rpc/getinfo


Also, anything from https://chainz.cryptoid.info would be very helpful as well.

Thanks!

[soothaa]

This plugin has been working great so far. I'm adding more coins, however does the plugin only work with Iquidus or CryptoNote explorer types? Is there any way to add additional? I have an explorer that provides an output that looks like:

https://curve.uexplorer.me/api/rpc/getinfo


Also, anything from https://chainz.cryptoid.info would be very helpful as well.

Thanks!

Currently yes, just those two. But thank you for the detailed information, I will look into adding support for that as well as CrypoID - it's already supported by an unreleased plugin of mine, I'll just have to add it in.

[soothaa]

AwesomeMiner Coin Updater 0.3 (Requires AwesomeMiner 4.5 Release)

• Added support for UExplorer
• Added support for any coin on CryptoChainz
• Added support for CryptoBridge Exchange

You can find the latest update in the Mega link.

[Seanklei10]

AwesomeMiner Coin Updater 0.3 (Requires AwesomeMiner 4.5 Release)

• Added support for UExplorer
• Added support for any coin on CryptoChainz
• Added support for CryptoBridge Exchange

You can find the latest update in the Mega link.

Awesome, thank you! So far, appears to be working perfect.

Could you shed some light on how your smoothing algorithm for difficulty works? I notice it seems to start difficulty very low (resulting in a very high estimated profit) and then starts approaching the actual difficulty value. I also noticed this behavior seems to "reset" if I close and reopen the plugin.

FYI, the block difficulty you have in for CURV is about double what it should be. Need to cut it in half since half the block goes to MN's. Also CROP coin is fully PoS now, no more mining.

[soothaa]

AwesomeMiner Coin Updater 0.3 (Requires AwesomeMiner 4.5 Release)

• Added support for UExplorer
• Added support for any coin on CryptoChainz
• Added support for CryptoBridge Exchange

You can find the latest update in the Mega link.

Awesome, thank you! So far, appears to be working perfect.

Could you shed some light on how your smoothing algorithm for difficulty works? I notice it seems to start difficulty very low (resulting in a very high estimated profit) and then starts approaching the actual difficulty value. I also noticed this behavior seems to "reset" if I close and reopen the plugin.

FYI, the block difficulty you have in for CURV is about double what it should be. Need to cut it in half since half the block goes to MN's. Also CROP coin is fully PoS now, no more mining.

Good to hear.

It just starts collecting the difficulty every 60 seconds, adds it to an array, then calcuates the average. So it will eventually reach a max of 24 hours average difficulty. It should not reset.. that data is supposed to be saved out to the LocalCoinData.json file and be read in at run.. I'll try and look and see if there's a bug in there somewhere..

Block difficulty or block reward?  Looks like you mean reward.. found some data here: https://hashfaster.com/site/mining - will update my source file. I have not yet figured a way to easily fix changing block rewards because the data is very hard to come by.

[ruplikminer]

AwesomeMiner Coin Updater 0.3 (Requires AwesomeMiner 4.5 Release)

• Added support for UExplorer
• Added support for any coin on CryptoChainz
• Added support for CryptoBridge Exchange

You can find the latest update in the Mega link.

Awesome, thank you! So far, appears to be working perfect.

Could you shed some light on how your smoothing algorithm for difficulty works? I notice it seems to start difficulty very low (resulting in a very high estimated profit) and then starts approaching the actual difficulty value. I also noticed this behavior seems to "reset" if I close and reopen the plugin.

FYI, the block difficulty you have in for CURV is about double what it should be. Need to cut it in half since half the block goes to MN's. Also CROP coin is fully PoS now, no more mining.

Good to hear.

One of the best plugins ever. A detailed guide on how to use it would be very helpful tho...

It just starts collecting the difficulty every 60 seconds, adds it to an array, then calcuates the average. So it will eventually reach a max of 24 hours average difficulty. It should not reset.. that data is supposed to be saved out to the LocalCoinData.json file and be read in at run.. I'll try and look and see if there's a bug in there somewhere..

Block difficulty or block reward?  Looks like you mean reward.. found some data here: https://hashfaster.com/site/mining - will update my source file. I have not yet figured a way to easily fix changing block rewards because the data is very hard to come by.

[Seanklei10]

AwesomeMiner Coin Updater 0.3 (Requires AwesomeMiner 4.5 Release)

• Added support for UExplorer
• Added support for any coin on CryptoChainz
• Added support for CryptoBridge Exchange

You can find the latest update in the Mega link.

Awesome, thank you! So far, appears to be working perfect.

Could you shed some light on how your smoothing algorithm for difficulty works? I notice it seems to start difficulty very low (resulting in a very high estimated profit) and then starts approaching the actual difficulty value. I also noticed this behavior seems to "reset" if I close and reopen the plugin.

FYI, the block difficulty you have in for CURV is about double what it should be. Need to cut it in half since half the block goes to MN's. Also CROP coin is fully PoS now, no more mining.

Good to hear.

It just starts collecting the difficulty every 60 seconds, adds it to an array, then calcuates the average. So it will eventually reach a max of 24 hours average difficulty. It should not reset.. that data is supposed to be saved out to the LocalCoinData.json file and be read in at run.. I'll try and look and see if there's a bug in there somewhere..

Block difficulty or block reward?  Looks like you mean reward.. found some data here: https://hashfaster.com/site/mining - will update my source file. I have not yet figured a way to easily fix changing block rewards because the data is very hard to come by.

Yeah block reward is what I was referring to. Updating the block reward would be beneficial in certain situations, especially with something like CURV where there are two variables: keeps decreasing over time and the masternode vs mining rewards change periodically. However, I've seen similar issues where its even hard for me to manually determine what the block reward is at times.

[Seanklei10]

New Bug:

I went to add the following line to the config
{CoinFullName: "Argo", CoinShortName: "ARGO", Algo: "Skein", BlockReward: 40, BlockTime: 90, BlockExplorer: "http://explorer.argocash.com/ext/summary", BlockExplorerType: "Iquidus"}

After I did that and restarted the plug in, I now get. The error in the image below.

I tried so far tried (with no success)

1) removing that line from the config
2) extracted a new/clean copy of version 0.3 plugin
3) fully restarted awesome miner
4) removed all custom coins from awesome miner itself

Doesnt seem like there is anything I can do to recover the plugin. Is there another place the plugin stores data or has data that interacts with awesome miner that may have caused this bug?

Thanks!

https://i.imgur.com/PgtHl0E.png

[moppidoo]

New Bug:

I went to add the following line to the config
{CoinFullName: "Argo", CoinShortName: "ARGO", Algo: "Skein", BlockReward: 40, BlockTime: 90, BlockExplorer: "http://explorer.argocash.com/ext/summary", BlockExplorerType: "Iquidus"}

After I did that and restarted the plug in, I now get. The error in the image below.

I tried so far tried (with no success)

1) removing that line from the config
2) extracted a new/clean copy of version 0.3 plugin
3) fully restarted awesome miner
4) removed all custom coins from awesome miner itself

Doesnt seem like there is anything I can do to recover the plugin. Is there another place the plugin stores data or has data that interacts with awesome miner that may have caused this bug?

Thanks!

with the 0.3 plugin, did you simply overwrite the 0.2 version with the files in package (except config.json)? cause I have Argo in my config and didn't have the problems you are experiencing, and maybe you needed some other library files in the 0.2 version.

[Seanklei10]

New Bug:

I went to add the following line to the config
{CoinFullName: "Argo", CoinShortName: "ARGO", Algo: "Skein", BlockReward: 40, BlockTime: 90, BlockExplorer: "http://explorer.argocash.com/ext/summary", BlockExplorerType: "Iquidus"}

After I did that and restarted the plug in, I now get. The error in the image below.

I tried so far tried (with no success)

1) removing that line from the config
2) extracted a new/clean copy of version 0.3 plugin
3) fully restarted awesome miner
4) removed all custom coins from awesome miner itself

Doesnt seem like there is anything I can do to recover the plugin. Is there another place the plugin stores data or has data that interacts with awesome miner that may have caused this bug?

Thanks!

https://i.imgur.com/PgtHl0E.png

with the 0.3 plugin, did you simply overwrite the 0.2 version with the files in package (except config.json)? cause I have Argo in my config and didn't have the problems you are experiencing, and maybe you needed some other library files in the 0.2 version.

This was with a fresh install copy of the 0.3, I don't believe anything from 0.2 is needed to run 0.3. To test though, I copied the "missing" files from 0.2...same result.


EDIT: I just found the actual issues. I had a blank line at the end of the JSON file I didnt realize I had put there. Once I deleted that, issue was resolved.

[soothaa]

New Bug:

I went to add the following line to the config
{CoinFullName: "Argo", CoinShortName: "ARGO", Algo: "Skein", BlockReward: 40, BlockTime: 90, BlockExplorer: "http://explorer.argocash.com/ext/summary", BlockExplorerType: "Iquidus"}

After I did that and restarted the plug in, I now get. The error in the image below.

I tried so far tried (with no success)

1) removing that line from the config
2) extracted a new/clean copy of version 0.3 plugin
3) fully restarted awesome miner
4) removed all custom coins from awesome miner itself

Doesnt seem like there is anything I can do to recover the plugin. Is there another place the plugin stores data or has data that interacts with awesome miner that may have caused this bug?

Thanks!

The missing files were me trying to trim down the release, I found that they were unneeded.

Just off the top of my head.. it looks like maybe you have a leading space in your config file? If that's not the case, please copy/paste your exact config here using the code tags.

Also: anyone who wants help in the future - use this guys post as a model on how to ask. It's nearly perfect.

[Seanklei10]

New Bug:

I went to add the following line to the config
{CoinFullName: "Argo", CoinShortName: "ARGO", Algo: "Skein", BlockReward: 40, BlockTime: 90, BlockExplorer: "http://explorer.argocash.com/ext/summary", BlockExplorerType: "Iquidus"}

After I did that and restarted the plug in, I now get. The error in the image below.

I tried so far tried (with no success)

1) removing that line from the config
2) extracted a new/clean copy of version 0.3 plugin
3) fully restarted awesome miner
4) removed all custom coins from awesome miner itself

Doesnt seem like there is anything I can do to recover the plugin. Is there another place the plugin stores data or has data that interacts with awesome miner that may have caused this bug?

Thanks!

https://i.imgur.com/PgtHl0E.png

The missing files were me trying to trim down the release, I found that they were unneeded.

Just off the top of my head.. it looks like maybe you have a leading space in your config file? If that's not the case, please copy/paste your exact config here using the code tags.

Also: anyone who wants help in the future - use this guys post as a model on how to ask. It's nearly perfect.

That was exactly the problem. I had an extra line at the end of the config. Once that was deleted it worked perfectly again. Thanks!

[soothaa]

New Bug:

I went to add the following line to the config
{CoinFullName: "Argo", CoinShortName: "ARGO", Algo: "Skein", BlockReward: 40, BlockTime: 90, BlockExplorer: "http://explorer.argocash.com/ext/summary", BlockExplorerType: "Iquidus"}

After I did that and restarted the plug in, I now get. The error in the image below.

I tried so far tried (with no success)

1) removing that line from the config
2) extracted a new/clean copy of version 0.3 plugin
3) fully restarted awesome miner
4) removed all custom coins from awesome miner itself

Doesnt seem like there is anything I can do to recover the plugin. Is there another place the plugin stores data or has data that interacts with awesome miner that may have caused this bug?

Thanks!

The missing files were me trying to trim down the release, I found that they were unneeded.

Just off the top of my head.. it looks like maybe you have a leading space in your config file? If that's not the case, please copy/paste your exact config here using the code tags.

Also: anyone who wants help in the future - use this guys post as a model on how to ask. It's nearly perfect.

That was exactly the problem. I had an extra line at the end of the config. Once that was deleted it worked perfectly again. Thanks!

Glad to hear it. I will add making "reading in the config file more robust" on my TODO list.

[acyclovir]

Hi soothaa, thaks for your wonderfull work!!

I have some questions for you, if the plug in, have to be running all time 24/7 couldn´t be a good idea, to create a rule on AM to run the plug in? or, for check every n time if plug in is running/online?

Could you please help me with this rule creation?

Thanks in advance