BCX could bribe one of the largest pools
LOL nifty boy ... apparently u aren't aware of the fact that BCX himself owns and operates one of the largest pools of all around
~CfA~
Of XMR
uh no. fail.
Topic: Monero Distributed Mining Initiative - BCX attack denied - page 3. (Read 6152 times)
LOL nifty boy ... apparently u aren't aware of the fact that BCX himself owns and operates one of the largest pools of all around
~CfA~
Of XMR
uh no. fail.
BCX could bribe one of the largest pools
LOL nifty boy ... apparently u aren't aware of the fact that BCX himself owns and operates one of the largest pools of all around
~CfA~
ROFL
So after pissing off 90% of the forum over several months you ask for help! Hahahahahaha!
Die, shitcoin DIE!
So after pissing off 90% of the forum over several months you ask for help! Hahahahahaha!
Die, shitcoin DIE!
pussy blabla with large pic of the monero slaveholder
just let it die dude. best for the good of all to have the $hitcoin gone
~CfA~
And do NOT MINE on the three largest pools.
BCX could bribe one of the largest pools and it would make financial sense for any one of them to sell for 100 btc which would give him control of the hash (saw someone else mention this). It's fear mongering - but from an economic perspective it would probably be cheaper for him than AWS.
Or ddos.
BTW - LOVE the pic. Absolutely classic.
BCX could bribe one of the largest pools and it would make financial sense for any one of them to sell for 100 btc which would give him control of the hash (saw someone else mention this). It's fear mongering - but from an economic perspective it would probably be cheaper for him than AWS.
Or ddos.
BTW - LOVE the pic. Absolutely classic.
-------------------------------------------------------------------------------------------------------------------------------------------------------
The only way to defeat the BCX attack, is by pure hash power. I have analyzed this whole situation over the past days and only come to one conclusion. To win this war, in practical we need to put up as much hashing power possible. There is no programming error that can cause any double spend, as long as the hashing power is distributed we will all be safe. Consensus always wins.
To secure Monero and earn XMR from mining:
1. Put all your mining rigs on XMR.
2. If you do not have a mining rig, start cloud mining. We need as many people as possible to turn hash rate to Monero.
Here is a guide for cloud mining Monero written by jwinterm. It assumes you have setup an account at https://aws.amazon.com/ec2/ and linked your credit card.
Quote
1) Click on EC2, and then click on Spot Requests under Instances on left sidebar.
2) Click Request Spot Instances blue button near top, and then click Community AMIs and search for XMRminer. Select XMRminer2.
3) For Instance Type, select GPU instances g2.2xlarge, click next and set your maximum price (kind of expensive now, need to do like
$0.09 per hour, used to be more like $0.06).
4) Click Review and Launch and then click Launch. At this point you need to setup your ssh keys. I did this a while ago, so I don't remember exact details, but it should be pretty straightforward. Here is a link to Amazon's official tutorial on key pair creation:
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html
Let me know if you have issues.
5) Make yourself a cup of tea and wait 30-120 seconds while your instance is prepared.
6) You'll need to ssh into your instance. On Linux you just put your ssh keys in ~/.ssh and set permissions for 400 (I think), and if you ssh from that folder, that's all you need to do. I think on Windows, using Putty, you need to maybe convert the key to putty's format using an extra putty tool. Let me know if you need additional help with this. Here are Amazon's official links on how to connect if you're having trouble:
ssh/Linux - http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AccessingInstancesLinux.html
Putty/Windows - http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/putty.html
More Putty - http://docs.aws.amazon.com/gettingstarted/latest/wah-linux/getting-started-deploy-app-connect.html
7) Click on Instances in the left sidebar, and you should see a g2.2xlarge instance with green circle that says running. Click that and then click Connect at the top, and it should give you your IP address to connect to with some instructions.
8 ) On Linux your ssh command should look like:
Use ubuntu as user not root.
9) Maybe it's more like 180-300 seconds. Drink some tea while waiting.
10) When it prompts you to permanently add key, click "yes".
11) Now, you need to edit cpustart.sh and gpustart.sh in your home directory using either vi or nano, unless you want to mine to my XMR address
It looks like if you want to mine directly to exchange, just replace my XMR address in both files with YourExchangeXMRAddress.YourExchangePaymentID.
12) You need to run two commands, one to make gpuminer work, and other to make cpuminer much faster:
13) I just made another script called start.sh to launch both miners at once, and it seems to work. So do:
then vi or nano start.sh and add:
then:
and then launch with:
You need the screen so that when you disconnect your ssh session, the miners keep mining.
That's it. You can disconnect and both miners should be hashing away. You can ssh back in and run
and you should see minerd and ccminer listed in the processes somewhere near the bottom.
If you want to launch a shitload of instances, then obviously you want to automate this process and not do it manually every time. In this case, you need to make sure you edit the files so that they have your XMR address and not mine, and create the start.sh script in home directory, then edit the rc.local file by doing:
and add the following lines:
This way, as soon as the instance boots up, it should autolaunch the miners. I haven't tried this final automation part (as I don't normally launch a shitload of instances), but I think this should work, and I'm gonna verify it now.
Now, go back to your EC2 console, right-click on the g2.2xlarge instance in your Instances window, and select Create Image. This will sever your connection and cause a reboot, but you will now have your own image/AMI that you can launch 10s or 100s or 1000s of, just by entering however many instances you want when filling out your spot request form.
I just tried the rc.local thing, and it seems to auto-launch ccminer and minerd
2) Click Request Spot Instances blue button near top, and then click Community AMIs and search for XMRminer. Select XMRminer2.
3) For Instance Type, select GPU instances g2.2xlarge, click next and set your maximum price (kind of expensive now, need to do like
$0.09 per hour, used to be more like $0.06).
4) Click Review and Launch and then click Launch. At this point you need to setup your ssh keys. I did this a while ago, so I don't remember exact details, but it should be pretty straightforward. Here is a link to Amazon's official tutorial on key pair creation:
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html
Let me know if you have issues.
5) Make yourself a cup of tea and wait 30-120 seconds while your instance is prepared.
6) You'll need to ssh into your instance. On Linux you just put your ssh keys in ~/.ssh and set permissions for 400 (I think), and if you ssh from that folder, that's all you need to do. I think on Windows, using Putty, you need to maybe convert the key to putty's format using an extra putty tool. Let me know if you need additional help with this. Here are Amazon's official links on how to connect if you're having trouble:
ssh/Linux - http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AccessingInstancesLinux.html
Putty/Windows - http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/putty.html
More Putty - http://docs.aws.amazon.com/gettingstarted/latest/wah-linux/getting-started-deploy-app-connect.html
7) Click on Instances in the left sidebar, and you should see a g2.2xlarge instance with green circle that says running. Click that and then click Connect at the top, and it should give you your IP address to connect to with some instructions.
8 ) On Linux your ssh command should look like:
Code:
ssh -i aws1.pem [email protected]
9) Maybe it's more like 180-300 seconds. Drink some tea while waiting.
10) When it prompts you to permanently add key, click "yes".
11) Now, you need to edit cpustart.sh and gpustart.sh in your home directory using either vi or nano, unless you want to mine to my XMR address
It looks like if you want to mine directly to exchange, just replace my XMR address in both files with YourExchangeXMRAddress.YourExchangePaymentID.12) You need to run two commands, one to make gpuminer work, and other to make cpuminer much faster:
Code:
sudo ldconfig /usr/local/cuda-5.5/lib64
sudo sysctl -w vm.nr_hugepages=24
13) I just made another script called start.sh to launch both miners at once, and it seems to work. So do:
Code:
touch start.sh
Code:
#!/bin/bash
screen /home/ubuntu/cpustart.sh
screen /home/ubuntu/gpustart.sh
Code:
chmod 755 start.sh
Code:
sudo screen ./start.sh
That's it. You can disconnect and both miners should be hashing away. You can ssh back in and run
Code:
ps -A
If you want to launch a shitload of instances, then obviously you want to automate this process and not do it manually every time. In this case, you need to make sure you edit the files so that they have your XMR address and not mine, and create the start.sh script in home directory, then edit the rc.local file by doing:
Code:
sudo nano /etc/rc.local
Code:
ldconfig /usr/local/cuda-5.5/lib64
sysctl -w vm.nr_hugepages=24
screen /home/ubuntu/start.sh
Now, go back to your EC2 console, right-click on the g2.2xlarge instance in your Instances window, and select Create Image. This will sever your connection and cause a reboot, but you will now have your own image/AMI that you can launch 10s or 100s or 1000s of, just by entering however many instances you want when filling out your spot request form.
I just tried the rc.local thing, and it seems to auto-launch ccminer and minerd
Current hash rate: 16,655,833 H / s
UPDATE: Please consider SOLO mining, if you have to use pool make sure to use backups. BCX will try to DDOS pools in order to gain more control of the network in order to successfully execute the attack. BCX took down poloniex just minutes ago. Instructions for solo mining with private pool here
Jump to: