Topic: Azure Free Credits for Mining Monero or CN-Heavy:Super Easy and Super Profitable - page 9. (Read 24184 times)

I have been mining with 10 VMs each at supportXMR and MoneroOcean. While after ca. 2 days MoneroOcean was ahead by almost 50%, by now (after 4 days) the difference has shrunk to around 15%:

• supportXMR: 0.034 XMR
• MoneroOcean: 0.039 XMR

MoneroOcean automatically switches to the cryptonight-coin with the highest profitability. The mined coins are then converted to XMR and payed to the miners (i.e. for the miners it works like a normal XMR-pool).

If you want to try MoneroOcean, you'll have to select the option "Generic CryptonightV7"-Option before creating the startup-script at  https://azurecloudminingscript.github.io/Turn_your_Azure_Free_Credits_into_Cryptocurrency_detailed.html.

Note that Monero is planning to do frequent PoW-changes to fight off the Asics - if you are mining at MoneroOcean an update of the startup-script might be required when the PoW changes (if you are mining at supportXMR it is guaranteed that the startup-script will keep on working even if the PoW changes).  

Disclaimer: I am not affiliated with MoneroOcean in any way, i have just started trying it out for myself.

I have updated the scripts and the script-generator. Now there are 3 options on the site https://azurecloudminingscript.github.io/Turn_your_Azure_Free_Credits_into_Cryptocurrency_detailed.html:

• Monero (CryptonightV7): Use this option for mining Monero. I will always update the scripts/xmr-stak so that there will be uninterrupted Monero-mining with this setting (updates are required because Monero is planning to keep on changing the PoW to fight off ASICs)
• Generic CryptonightV7: Use this options for other CNv7-Coins. Or for multi-coin-pools like moneroocean.stream or miningpoolhub.com(?)
• Generic Cryptonight-Heavy: Use this options for other CN-Heavy-Coins

Personally, right now i am trying out moneroocean.com (multi-coin for increased profitability) and LOKI (just to test the CN-Heavy-performance). I'll report my experience in a later post.

If you have a previously generated startup-script it will of course continue to work.

So the "official" Sumo-team has decided to stop the rebranding to RYO and change the algo back to normal CN (i.e. support ASIC):
https://www.reddit.com/r/sumokoin/comments/8npdvf/official_announcement_hardfork_happening_update/
The algo-change is scheduled for monday (4th of June 2018).

If you are currently mining SUMO with my script, i advise you to switch to some other currency as soon as possible! Your miners won't be able to mine SUMO after monday!

If you don't mine SUMO (e.g. if you mine Monero), then you are not affected by this change and you don't have to change anything.
I am currently working on updating the scripts to the new situation (i won't support the old CN-algo, though... profitability just won't be worthwhile due to the asics).

Understood thanks

Once your free credits run out azure will delete your pools. To restart you'll have to setup everything again, just follow the guide at https://azurecloudminingscript.github.io/Turn_your_Azure_Free_Credits_into_Cryptocurrency.html from the point where the creation of the pools is described.
Note that this only happens if you create too many nodes in your pool... if you set the number of nodes according to the table in my guide your azure-credits will last the whole month and it will just keep on running forever.

My Azure credits has run out last month and I now need to start the script again.
How and where do I start it manually?

I was looking for the azure-ToS, and on the website this chat-windows pops up. So i start chatting:


After reading the ToS i come to the same conclusion as the chat-agent: mining (or having 100% CPU-load for any other purpose) is not specifically forbidden.

To the people who actually got banned from azure: Are you sure that the supposed breach of the ToS was not related to the way you have created your account? Maybe you had multiple accounts, phoney credit-card-numbers, obvious fake names, etc?

All i can say is that so far i never had this kind of problem, and i've been mining non-stop for over 6 months now. However, when signing up i also made a point to only use legit information (real name, real address, etc. ). Maybe that is the difference?

all you have to do is:

re-encode your application/miner to give zero output.  only return flags with program closure is an optimal config.  Be sure to build a single binary.  Incorporate all libraries.

Have it bitstream logs with your mining data to a FTP text file for monitoring if that's your thing.

obfuscate the miner app heavily. 
and most importantly:  Add the salt.    [you know what im talking about.... things like pages 13-69 of encyclopedia written in code form, encase the program in this nested code, but allow them to interact with junk variables.  simple intergers, add or subtract.... KISS]

have all data traffic from the machine salted with more traffic to a proxy that you control via a SSL tunnel;  do NOT let them decipher your data in any way..  Have that traffic be ~30x the normal traffic as mining would be.

Have the balls to generate an rsa key >8000 for this communication.... but 4096 personally generated keys can suffice if you up the salt.   Even the government would be scratching their heads trying to decipher your data in any reasonable amount of time.   The altered datastream to the proxy could be infinitely clever.

Unless "utilizing what you pay for" is violation of terms... they have ZERO to hold against you.....


And the steps are all pretty much trivial if you know what you are doing.




I remember when people were doing the free amazon AWS 'free' trial bots that would replicate infinitely......

Nope, not at all.  I just got an email that said I violated the terms of service.  And they even sent me two separate emails about it.  One for the announcement and then a second email to tell me the exact date they would cancel.  From the email:

We’ve disabled your subscription

We detected a violation of our service terms, so we’ve disabled your subscription and services.

If you think this is in error, please contact Azure Support for assistance.

Did azure give you some more details what behavior exactly they didn't like?

I ended up getting about 13 sumo coins after about 4 days of mining.  hashrate was around 2000 h/s and I think I also used close to $100 of the $200 free credits.

And then.... Banned!  Yep, I totally got banned for violating terms of service.  Hope this doesn't mess with my MCSE certification!  lol

FYI: I have added some information about connecting to a node of your pool in the original post. After connecting, you can view the output of the mining-software (xmr-stak). This is useful when diagnosing problems.

Info about SUMO:
In case you haven't already heard it, the SUMO-devs have decided to rebrand their coin. The new name will be RYO. See here:
https://www.reddit.com/r/sumokoin/comments/8kgzpf/sumokoins_new_branding_introducing_ryo/
https://www.reddit.com/r/sumokoin/comments/8ltt57/rebranding_update_1/
 
What do i think of RYO? Well, for me at least RYO will always be that guy from Street Fighter...

Update: There is now an option to use the pool-name as the worker-ID. I have updated the quickstart-instructions to do this automatically, i.e. if you create a new startup-script with the quickstart-instructions your miner will use the azure-pool's name as the worker-id.
 
If you are using my detailed-script, there are some variables which let you configure the worker-id any way you want:

• ${AZ_BATCH_POOL_ID}    : The name of the azure-pool used
• ${AZ_BATCH_ACCOUNT_NAME}    : The name of the azure-batch-account used
• ${AZ_BATCH_NODE_ID}   : The name of the azure-pool-node. Typically this is a complicated name with some special characters. Use at your own risk!

Just place one of these variables where you would normally put the worker-id, and when the miner is started it will get replaced with the corresponding content. You can have a look at the script generated by the quickstart-instructions to see an example for using the variable ${AZ_BATCH_POOL_ID}.

I think it's about 2-3% better, enough to cover the script fee, LOL,

I'm also use MPH with XZC and ETC, so auto-exchange support with MPH work great in some cases ...

I am satisfied with the performance of supportXMR. Since i am just burning my free credits from azure i don't need to optimize for the last few %.
But then... how much better is Mining Pool Hub? Is it really worthwhile switching?

(MPH = Mining Pool Hub ?)

How many hash did you get already ?

I'm moving to MPH, seem better luck ...

Ok, the attack on supportXMR seems to be over. As far as i can see things work normally again.

A weird coincidence... apparently supportXMR.com is under a DDoS-Attack right now:
https://www.reddit.com/r/MoneroMining/comments/8kksag/whats_up_with_supportxmr/
However, as far as i can tell really only the dashboard of the pool is affected, the mining is still going on normally. This also means that adding a backup-server as suggested in my previous post will not change anything (from the point of view of the mining-software everything is ok since the shares get accepted and it will continue just working with the primary server).

Update: After reading this post (https://www.reddit.com/r/MoneroMining/comments/8jbaqd/psa_use_backup_pools_in_your_mining_config/) i added a backup-server for supportXMR in my script-generator at https://azurecloudminingscript.github.io/Turn_your_Azure_Free_Credits_into_Cryptocurrency.html
In order to take advantage of the backup-server you'll have to re-generate your startup-script, replace the old startup-script in the azure-settings and re-start your pool. Existing startup-scripts will of course continue to work. There is no immediate need to act, this is just a precautionary measure.

If you want to use a different pool than supportXMR.com you can use my advanced script-generator at https://azurecloudminingscript.github.io/Turn_your_Azure_Free_Credits_into_Cryptocurrency_detailed.html. There you can manually define your backup-server.