Good idea, I will setup the pool early and "activate" it at 23:00.
Awesome thanks = ) This is wrong. One needs to suffer sleepless night to get CATCOIN  It's more like, I'm on the West Coast, and when this goes live I'll be hanging out with my girlfriend, hence the need to get this stuff setup before I leave lol. It drops at 3:00 PM today my time. |
|
|
|
Good idea, I will setup the pool early and "activate" it at 23:00.
Awesome thanks = ) |
|
|
|
Well with just hours left to launch the source cannot be built.. this is moving to become flopcoin..
So you want to compile wallet by yourself and start mining before release? It will be unfair. Hope that developer will announce qt-wallet just in 23:00 and only after that will update the whole code on github. Yeah, I'm pretty that's the point. To make sure no one premines it before its officially released. Not sure what you're complaining about. Pretty sure its intended. Yep it is. Actually I'm going to release all the code but the genesis block, and then do the last commit at 23:00 so everyone can start mining. You will be able to see from the block timestamps and block count that I did not premine. So, I'm not going to be available when the coin launches at 23:00. Any chance of setting up the pool early so we can at least setup our workers and get them ready to go before you release the genesis block? |
|
|
|
Well with just hours left to launch the source cannot be built.. this is moving to become flopcoin..
So you want to compile wallet by yourself and start mining before release? It will be unfair. Hope that developer will announce qt-wallet just in 23:00 and only after that will update the whole code on github. Yeah, I'm pretty that's the point. To make sure no one premines it before its officially released. Not sure what you're complaining about. Pretty sure its intended. |
|
|
|
Hey there, I'm getting a problem on your very last step to actually make the miner, I followed your steps exactly:  apt-get install git
git clone https://github.com/pooler/cpuminer.git
cd cpuminer
./autogen.sh
./configure
make
make install
that all right after I type in ./autogen.sh I get the following: ./autogen.ssh 8: ./autogen.sh: aclocal: not found I think I figured it out. I had to install automake. Thanks! |
|
|
|
Hey there, I'm getting a problem on your very last step to actually make the miner, I followed your steps exactly: apt-get install git
git clone https://github.com/pooler/cpuminer.git
cd cpuminer
./autogen.sh
./configure
make
make install
that all right after I type in ./autogen.sh I get the following: ./autogen.ssh 8: ./autogen.sh: aclocal: not found |
|
|
|
What is going on with all the people pushing cloud cpu mining? It is not profitable at all. Taken right from your guide: Costs: 5 x 8 CPUs = 40 CPUs (aprox 250 khash/s) = $20 per day $20 a day for 250kh/s. There is NO coin that you can mine at this rate that would make you more than $20 a day. If there was, people would be pointing their large mining rigs at it. Do the math guys, this isn't worth it. This only works for when coins are first released, I think that's what he's getting at. In the first 24 hours its possible to get so many coins that you can recoup the losses for running it for one day. |
|
|
|
Hey there, I'm getting a problem on your very last step to actually make the miner, I followed your steps exactly: |
|
|
|
+1 for LCC request. LOLCAT is way more recognizable.  - I think all these memecoins are hilarious. If they bring more people into the space, all the power to the devs and the communities behind them. That does have a ring to it, but Cat Coin is pretty simple since everyone knows the internet is made of cats. |
|
|
|
If we wanted to, we could go back to lolcats roots:  |
|
|
|
|
I think we definitely need to go with Business Cat.
|
|
|
|
Again, is there anyone that has successfully set up their cubes for solo mining? I would really like to learn how to do this. I posted a thread by itself but so far no answer has been useful. if youve set up the wallet as a server then all you have to do is point the miner to that computer you dont need stratum proxys just point the mining gear to that wallet and your solo mining
I've tried this. When I set my "pool addresses" to my IP (I'm on a router, so 192.168.x.x) and I have the wallet running as a server, it never connects and the cubes themself never show a hashrate. I'm also assuming that neither CGMiner or BFG Miner could be used in this situation. Anyone? Solo mining is mainly done now on other crypto-currencies where the difficulty level is much lower and can be done on a normal PC. In Bitcoin, the difficulty has gone so high since March 2013 that it would take you more than 5 years and 131 days from today to solve a block depending on luck! Since ASIC mining equipment adoption is growing, pool-mining is the way forward. I know this. That's why I want to solo mine other SHA-256 altcoins. I've been around long enough to know that for solo mining BTC today you need an industry sized hashrate. |
|
|
|
Again, is there anyone that has successfully set up their cubes for solo mining? I would really like to learn how to do this. I posted a thread by itself but so far no answer has been useful. if youve set up the wallet as a server then all you have to do is point the miner to that computer you dont need stratum proxys just point the mining gear to that wallet and your solo mining
[/quote
I've tried this. When I set my "pool addresses" to my IP (I'm on a router, so 192.168.x.x) and I have the wallet running as a server, it never connects and the cubes themself never show a hashrate. I'm also assuming that neither CGMiner or BFG Miner could be used in this situation.
Anyone? |
|
|
|
if youve set up the wallet as a server then all you have to do is point the miner to that computer you dont need stratum proxys just point the mining gear to that wallet and your solo mining
[/quote
I've tried this. When I set my "pool addresses" to my IP (I'm on a router, so 192.168.x.x) and I have the wallet running as a server, it never connects and the cubes themself never show a hashrate. I'm also assuming that neither CGMiner or BFG Miner could be used in this situation. |
|
|
|
Maybe it's just me, but I have had zero hardware problems with all of the cubes I've ordered from both Canary and SSB. I feel like you guys all have mail carriers that kick around all of the packages before they get to your house.
Of course I had to open my big mouth. One of my cubes now has one half of a board all Xs. I'll have to tear that one done and find out what the deal is. |
|
|
|
|
Maybe it's just me, but I have had zero hardware problems with all of the cubes I've ordered from both Canary and SSB. I feel like you guys all have mail carriers that kick around all of the packages before they get to your house.
|
|
|
|
|
Payment and PM sent for another cube = )
This is like a god damn addiction now.
|
|
|
|
|
Hello there.
I've been trying to figure out how I would configure solo mining (for Sha-256 altcoins) with an AsicMiner Cube, but I can't currently figure it out. With something like a BFL Jalapeno that mines through BFG Miner, it's not hard to point at solo mining, but since bfg miner support with the cube is minimal I'm having trouble figuring out what I should be looking at, what miningproxy.exe should be doing, where it should be pointed etc etc.
If anyone has figured out how to solo mine with the cube please respond with some tips = )
|
|
|
|
Also, your miningproxy port does not have to be identical to the pool ports on the cube. Actually, yes it does. The -p port refers to the stratum port on the pool; the -gp port refers to the getwork listen port which must be the same as the "Pool port" on the Cube. If you don't specify a getwork port in mining_proxy, it defaults to 8332. If you need to run multiple proxies, like a secondary/failover pool, you need to specify a different getwork port in the second proxy instance, and match that port in the secondary pool config on the Cube. So in my case, what happens when the cube is defaulted to 8332 and the port specified in the batch file is 3334? It hasn't shown any problems that I can see in this configuration. Wait, answered my own question. The cube getwork pool port is 8332, and since I don't have a -gp specified on my miningproxy it defaults to 8332, while the -p refers to the stratum port 3334. So technically that means I'm right, even though my thinking was incorrect lol, since the port (-p) is in fact different than the ports listed in the cube. |
|
|
|
|
Show Posts
