Patrike,
Feature Request
Is it OK to ask for a secondary Profit Profile to be added to the program ?
If so, can I post the info / details here and get feedback from others in this thread ?
Or should I contact you direct with this ?
What is the expected behavior of a secondary profit profile here? You can add your own profiles in Options dialog, Profit profile section. A single miner can only reference a single profit profile.
You can share any ideas in the thread here, because it's always good to get opinion from more people on these kind of ideas. Thanks!
OK, here goes, I take it that the Profit Profile works on fiat profit -- ie USD ($) of the coins, correct me if I am wrong.
So here is the secondary Profit Profile idea.
1/ The Profit Profile scans the BTC exchange value of the algorithms that you have selected to mine on said pool and switches to the algorithm that pays the most in uBTC regardless of the $ profit, the mBTC profit should override here in this case even if the dollar amount is $0.04 or $10.00 as the mBTC amount is what we are looking for, not the $ amount.
For example -- Bitcore @ ZPOOL >> Under the POOL tab for this algo, the profit* in mBTC is 0.01732
* 24h estimation from net difficulty in mBTC/MH/day (in PH for sha256 & GH for blake, decred, x11, quark, qubit, kS for equihash)
Below is another example, I mined the blake2s algo and earned this below
BlakeStar (blake2s)
0.518452 BLAS << This is the amount earned / mined in this coin
0.216%
0.00019704 <<< This is the uBTC amount earned, this will be paid to my BTC wallet address thats been given with the c=BTC command, you can add this to a custom pool in Awesome Miner.
c=BTC << this is added to the password field in the custom pool in Awesome Miner.
-a m7m -o stratum+tcp://m7m.mine.zpool.ca:6033 -u
-p c=BTC
So say this is the most profitable algo to mine in terms of mBTC profit regardless of the $ profit, Awesome Miner should switch to that algo and mine it.
Awesome Miner then rescans the Algorithms to find the next most profitable one in terms of uBTC when exchanged and not the $ amount.
ZPOOL allows you to set the symbol that you want to be paid in ...eg c=BTC, this is the only pool that I have found that lets you pick the payment option with the correct wallet address for that payment.
2/ If someone wants to be paid in say DASH or any other coin (c= eg c=BTX or c=DASH etc) and input the correct wallet address for that symbol, the Profit Profile looks to see what algorithm pays the most in the payout coin (c=DASH) for example to a DASH wallet.
Say someone wants to boost their DASH wallet with some earnings, which algo would be best to do this when exchanged out ?
ie... Awesome Miner checks for this and mines the algo that's worth more in DASH vs other coins when exchanged by the pool (ZPOOL).
Thoughts ?
I think I'm following here, you want AM to be able to set the C=XXX code for Zpool based on what is currently the coin that has the best conversion rate to BTC? This would be a complex setup, as AM would have to constantly be scanning an exchange and doing comparisons in order to change the c=XXX code. And in order to change the c=XXX code, it would have to stop the miner and restart it. Now, you know with the huge number of coins on Zpool, that this will fluctuate constantly, even if you used a 24 hour average... and more importantly, the exchange does not happen instantly at Zpool. By the time Zpool sends your mined coins to the exchange, the exchange rate could be vastly different than what AM was calculating at the time of mining.
I'm still trying to understand the reasoning behind a second profit profile though. The profit profile just establishes how much hashrate you have and how much power you use for those algos. I guess you could have a second profile to ignore certain algos, but I don't know how AM would know to pick one over the other? What conditions would be necessary to switch profit profiles? The scenarios you mentioned in your examples would be an alternate logic stream option in the Managed Profit Miner, not in the Profit Profile.
I like where your thinking was going, but the exchange timing issues I mention above will probably defeat your expectations.
I think I'm following here, you want AM to be able to set the C=XXX code for Zpool based on what is currently the coin that has the best conversion rate to BTC?
Your close, more details below.
The c=symbol is set by the user with the correct wallet address for that symbol. This will be how you are paid, ie, c=BTX + your bitcore wallet address.
Custom pools and pool groups need to be made for this to work. The pre-defined pools do not allow the user to define the c=symbol and add the correct wallet for that symbol.
Forgot to add -- This is for a 'My Profit Miner' and not a 'Managed Miner'.
Week 1
Say I wanted to be paid in Dash for this week -- Custom pools need to be made for all the algo's
Awesome Miner - My Profit Miner -- Mines the algo's that gives me the best conversion to the c=symbol and not the fiat ($) profit of the algo that's mined.
(c=DASH + Dash wallet address)
Week 2
Say I wanted to be paid in Hush this week -- Custom pools need to be made for all the algo's
Awesome Miner - My Profit Miner -- Mines the algo's that gives me the best conversion to the c=symbol and not the fiat ($) profit of the algo that's mined.
(c=HUSH + Hush wallet address)
Week 3
A new payout coin --- any coin of your choice + the wallet for that coin. Custom pools need to be made for all the algo's
(Please see below for more details from ZPOOL for the c=
)
Awesome Miner - My Profit Miner -- Mines the algo's that gives me the best conversion to the c=symbol and not the fiat ($) profit of the algo that's mined.
(c= + the wallet address for that symbol)
Awesome Miner scans for whatever algo pays the best in each coin for each day (or week) based on the algo / coins exchange rate for the c=symbol for that day (or week) and not for the fiat ($) profit of that algo / coin.
A 'My Profit Miner' is setup so that it auto switches to the best algo so that when it's exchanged to the c= is worth more in that coin (the payout symbol).
I've been testing this manually with a 'Managed Miner' I've had to take the time to see what algo's pay the best in the coin that I want to be paid in (BTC) and not fiat ($), the fiat ($) profit (gain / loss) is ignored, the mBTC profit is what I am looking for here.
This has taken me two weeks to get it right, I've had to watch the mBTC profit of all the algo's on ZPOOL and manually switch to them, it's a lot of work.
Now if Awesome Miner can be set to do the same thing with a 'My Profit Miner' that would take out the human factor.
Custom pools have been made to allow me to set the payment symbol and any other commands like difficulty etc.
These are my stats mining with 2 small rigs with the c=symbol set to BTC. (1x 1060 rig) (2 x 1070 rig) All the earnings in BTC have been done manually here for the last two weeks based on the above example(s) of mBTC profit over fiat ($) profit.
http://zpool.ca/?address=1BmzTnQkX3wAD8bWmao4NzT7k4nQyEyC3n
ZPOOL --- c=
STRATUM SERVERS
-o stratum+tcp://.mine.zpool.ca: -u [-p c=,]
must be a valid BTC address. Incorrect addresses will result in forfit of earning.
You can also use any valid wallet address from any of the coins we mine. This feature has had minimal testing so use at your own risk
YOU MUST ALWAYS set your currency in your password field: c=. The pool has mined hundreds of different coins and many have the same address version. We CAN NOT read your mind and possible know what currency you want. If no c= is set, your currency will be randomly chosen from any matching coins we have used. This HAS TO BE A REAL EXCHANGE SYMBOL. Do not use a symbol that has an added. Such as XVG-blake2s or AUR-sha or DGB-skein, these are ALL WRONG. These are used only for the pool to support multi-algo coins.
c= doesn't always work. However, if you fail to correct this and/or continue mining with the wrong currency detected you will NOT be able to change to the proper currency once an actual balance has been posted to the address.
(More info may be added, please feel free to revisit this post to check).