Show Posts
|
Pages: [1]
|
Four blocks found in an hour and a half. gg pool ![Cool](https://bitcointalk.org/Smileys/default/cool.gif)
|
|
|
CIA probably created bitcoin as a way to deal with the world after the collapse of the fiat currency experiment, which is inevitable.
|
|
|
It would be interesting to see AMD produce SHA256 or scrypt specific GPUs... I like to imagine they will, considering what steps they're taking to return to profitability. Shares of AMD trade around 3.50 for the last several months... association with bitcoin/cryptocurrency could be very good publicity for them and create another revenue stream.
|
|
|
lol, I already own quite a lot of btc, but want a solid mining plan as well. Everyone seems so against mining on these forums, but if anyone has any legit suggestions Id like a little input. If theres really NO profitable way to get a hosting/cloud thing going within the next month, then I suppose Ill just wait till Feb/March and purchase some bigger units to run...
Cloud mining seems sketchy to me; gear-in-hand is exciting. I'd wait until next gen ASICs come out, or order some KNC Jupes for the next shipment. Reselling is also an option with an in-hand miner. Good luck!
|
|
|
Drop the 50k on BTC instead, and then spend 1 BTC on 2 terrahash in less than a year.
|
|
|
I think so too, perhaps something with the blade requesting work by RPC call before the previous request closes... anyone have this same problem?
|
|
|
So I've gotten the two blades to receive work from bitcoind and I can see it in their webgui that they are receiving work. After about two minutes, however, they stop receiving work and their timers reset and bitcoind on the server becomes unresponsive and have to reboot to get bitcoind to start up correctly again.
Even running one blade directed at bitcoind hangs up and bitcoind becomes unresponsive. Anyone have any ideas for solutions?
|
|
|
Also why the f*** do people in these forums use decimals instead of commas to represent number segments?? wtf is 100.000?
100.000 = 100!!!
100,000 = 100000!!!!
Europe uses periods instead of commas.
|
|
|
It seems every thread about solo mining with block erupter blades gets this far and then dies... bump.
This is my bitcoin.conf :
server=1 daemon=1 rpcuser=user rpcport=8332 rpcallowip=192.168.2.254 (blade's IP) listen=1 gen=0
These are my blades settings:
MHS: 000000 Received: 0 Accepted: 0 IP: 192.168.2.254 Mask: 255.255.255.0 Gateway: 192.168.2.1 Primary/Secondary DNS: 192.168.2.1 Ports: 8332,8332 ServerAddresses: 192.168.2.101,192.168.2.101 user:pass: user:pass,user:pass
So the blades are not receiving work from bitcoind? Port 8332 is open, so firewall is not getting in the way.
|
|
|
Using BTC is the death knell of all financial institutions around the world because the protocol records all transactions and transactions are relatively easy to trace. Once you've been identified and assigned a wallet address, every transaction you conduct is traceable; tax evasion becomes a thing of the past... we will see how things unfold. SocialistFascist nations like the United States WILL utilize this important facet of bitcoin to control people even more; atleast those that wish to participate in 'normal' society. But the benefit of bitcoin is governments cannot manipulate the value of bitcoin as easily as it can manipulate the value of fiat.
|
|
|
I started a thread similar to this one, and I suppose I'm exactly where the OP is in set up. I have a few ASIC blades I'd like to solo with but I can't verify that the blades are connecting and receiving the block headers from bitcoind running on a linux server. I've tried commands like '$ ss' and cannot see the blade IP addresses in the output. Should I run as -testnet and point the blades at port 18332 and let it run for a while and see if testcoins end up in my wallet?
Also, for bitcoin.conf setting gen=0 will tell bitcoind to not hash using server resources, but will still give block headers to the blades to solve?
|
|
|
We might see the rise of multiple cryptocurrencies in our lifetimes that certain regions support at a greater rate than other regions. While people are pushing hard at developing machines capable of hashing more and more SHA256 per second per watt, perhaps the altcoins will see their hayday where people have been slow to the punch with bitcoin and mining and decide to focus on supporting alternative currency that they can participate in. So you may see China fully supporting bitcoin, while another country decides LItecoins (or any other altcoin) properties are most beneficial for it's economy. Cryptocurrencies are fascinating and it seems there has been a gigantic vacuum for the utility that the medium provide. $1,000/btc, no problem. $10,000/btc? Definitely. $100,000/btc? Bring it on ![Cool](https://bitcointalk.org/Smileys/default/cool.gif) The total amount of dollars and dollar liabilities around the world most likely eclipses $50 trillion; I've read somewhere the total lies in the quadrillions of dollars. With this in mind, I believe the exchange rate for BTC/$ will exponentially decrease until the dollar is made completely obsolete by unproductive monetary policy and ineffective/terroristic political practices domestically and internationally by the United States Federal government.
|
|
|
Thanks for the replies!
I've got bitcoind installed and created the bitcoin.conf containing:
server=1 daemon=1 rpcuser=USERNAME rpcpassword=PASSWORD rpcport=8332
I start bitcoind and it begins to download the blockchain. I've got my block erupter blades running, pointed at the server's IP address, with the user:pass field on the blades set as USERNAME:PASSWORD,USERNAME:PASSWORD. Have I proceeded correctly?
Now a few more questions...
If I were to solve a block, where would those bitcoins go? The wallet associated with bitcoind?
Is there any way that I can verify the blades are hashing?
Cheers!
|
|
|
I've searched all over bitcointalk.org for an answer to this question and I haven't found it yet: how do I go about setting up Block Erupter Blades to solo mine the blockchain? Right now, I have blades mining using mining_proxy.py from slush's pool and it works fairly well but I am concerned about the return in the future and feel like solo mining might be useful at some point. Here are my concerns: - Am I able to point mining_proxy.py to the IP address where bitcoin-qt is listening to solo mine?
- Would I be better off with something like BFGminer? What parameters should I run it with to solo mine?
If y'all could help by pointing me in the right direction I'd really appreciate. Cheers!
|
|
|
$300? Definitely. When? Probably by the end of the year. Bitcoin will come to shine brighter and brighter as time passes due to the inevitaable death knell of the United States financial hegemony through their increasingly invasive and abrasive financial regulations. I imagine $1000/BTC in a few years due to rapid inflation that will occur when circulating cash 'round the world returns to the United States... but I also imagine the DOW at 20,000 due to the same inflation.
I own stocks, gold, and BTC. Priced in dollars...I'm bullish on all three.
|
|
|
|