The bitcoin figures ( http://blockexplorer.com/address/1FGAftzSTztFSB8LMwsrdCKTyqGY6zr3sU) not moving because avalon already has a good cash reserve, as such they may Not need to convert this bitcoin into fiat currency, I am sure TSMC does not accept bitcoin. Butterfly selling Asic Chip that will be interesting because they still have a back log of Miners to delivered, or may be they need cash ..
and his cost price from this chip is likely half of his selling price, maybe $1 or $2 per chip or even less?
Topic: internet speed and hashing speed (Read 2922 times)
I wouldn't expect them to cash out all the BTC in the chip account, but they have probably close to $1M order now of chips from TSMC (maybe only $750K, but more orders get added every day - http://blockexplorer.com/address/1FGAftzSTztFSB8LMwsrdCKTyqGY6zr3sU )... they are still going to need to pull 7500 coins from somewhere. For accounting purposes, I would assume they would pull it from the actual account that they have chip sales... but maybe not.
Rumor is BFL might start selling raw chips as well... I think it would be a smart play to stay relevant.
Apparently Yifu said he can handle the chip orders without cashing out the BTC. Thats what he said when asked at the conference about having to cash out all those BTC in that wallet.
GBT
https://en.bitcoin.it/wiki/Getblocktemplate
So as we were saying... setting up your own pool moves all the miner traffic to LAN and only bitcoind interfaces with the WAN.
Frankly with 1TH I would still solo mine for a while... but my pain threshold for variance may be higher than yours and I am not a professional/commercial miner.
https://bitcointalksearch.org/topic/miner-variance-208520
There were a couple of threads on setting up your own private stratum pool a couple of months back:
Eloipool:
https://bitcointalksearch.org/topic/avalon-users-bitcoind-eloipool-configuration-158105
Slush's Pool:
https://bitcointalksearch.org/topic/avalon-users-bitcoind-and-slushsgeneralfaults-mining-pool-setup-162788
I suspect chip shipments will be delayed as no movement has been seen from Bitsyncom's chip wallet yet
http://blockexplorer.com/address/1FGAftzSTztFSB8LMwsrdCKTyqGY6zr3sU
But it is currently holding ~60,000 BTC which represents 760,000 Asic chips which translates to +215THash worth of asics coming on line once they ship.
AsicMiner... BTCGarden and others are good for another 100 - 200 THash in the next 2 months. BFL will most likely still struggle to add any serious hashpower onto the network for a couple of months.
If you don't have your miners in hand... or ordered in Avalon Batch2 or Batch3, you might want to consider joining a pool (or just investing in one of these mining farm companies).
Good luck!
https://en.bitcoin.it/wiki/Getblocktemplate
So as we were saying... setting up your own pool moves all the miner traffic to LAN and only bitcoind interfaces with the WAN.
Frankly with 1TH I would still solo mine for a while... but my pain threshold for variance may be higher than yours and I am not a professional/commercial miner.
https://bitcointalksearch.org/topic/miner-variance-208520
There were a couple of threads on setting up your own private stratum pool a couple of months back:
Eloipool:
https://bitcointalksearch.org/topic/avalon-users-bitcoind-eloipool-configuration-158105
Slush's Pool:
https://bitcointalksearch.org/topic/avalon-users-bitcoind-and-slushsgeneralfaults-mining-pool-setup-162788
I suspect chip shipments will be delayed as no movement has been seen from Bitsyncom's chip wallet yet
http://blockexplorer.com/address/1FGAftzSTztFSB8LMwsrdCKTyqGY6zr3sU
But it is currently holding ~60,000 BTC which represents 760,000 Asic chips which translates to +215THash worth of asics coming on line once they ship.
AsicMiner... BTCGarden and others are good for another 100 - 200 THash in the next 2 months. BFL will most likely still struggle to add any serious hashpower onto the network for a couple of months.
If you don't have your miners in hand... or ordered in Avalon Batch2 or Batch3, you might want to consider joining a pool (or just investing in one of these mining farm companies).
Good luck!
For pool mining:
Say your hashrate is 567MHash and that uses 12kb/s.
Divide by 567, times by 1000, that gives you 1GHash
Now you do the same to your bandwidth.
12 divide by 567, times by 1000.
Equals 21kb/s per ghash.
Replace 12 and 567 in all instances with your bandwidth and hashrate.
if i use your calculation it s showing 21 meg/terahashSay your hashrate is 567MHash and that uses 12kb/s.
Divide by 567, times by 1000, that gives you 1GHash
Now you do the same to your bandwidth.
12 divide by 567, times by 1000.
Equals 21kb/s per ghash.
Replace 12 and 567 in all instances with your bandwidth and hashrate.
so means for 10 tera you need 210 meg?
am i correct?
Keep in mind that this traffic you are talking about (between the miner and the pool server) does not go out on the internet for typical solo mining setups. Why? Because you typically have your miner(s), pool server and bitcoind all on the same local area network. The only thing that goes out on the internet is your bitcoind network traffc. All the stratum / GBT stuff happens on the local network.
ok let s sum up
let s say i have 10 rig of 1 tera each.
let s say i have one sever where my bitcoin d is located .
with 1 rj45 going from my hub to the 10 mini rig i will be able to make all this works right?
but how much my server will need as bw ? 21 meg or 210 meg?
1) Traffic between miner(s) and pool server (stratum/GBT/getwork on LAN)
2) Traffic between pool server and bitcoind (none if both are on the same server)
3) Traffic between bitcoind and internet
Your initial post asked about internet traffic requirements (item 3)).
The answer to your example is 210 meg on the LAN, but this is talking about item 1). It does has nothing to do with internet connection speed.
Unless you are solving all the blocks on the network the internet traffic used by bitcoind has little to do with the hashrate of your solomining setup.
so if i m right
the internet bandwith will be ridiculously low comparing to the hashpower in this type of setup,right
even 1 mbps/sec would be enough
but now complementary question
how to setup own stratum or gbt (what is gbt btw)?
i ve read some info on setting stratum pool on shush website so that basically install the software and tweak the setting and all is on?
it s seems too simple
am i missing something here?
For pool mining:
Say your hashrate is 567MHash and that uses 12kb/s.
Divide by 567, times by 1000, that gives you 1GHash
Now you do the same to your bandwidth.
12 divide by 567, times by 1000.
Equals 21kb/s per ghash.
Replace 12 and 567 in all instances with your bandwidth and hashrate.
if i use your calculation it s showing 21 meg/terahashSay your hashrate is 567MHash and that uses 12kb/s.
Divide by 567, times by 1000, that gives you 1GHash
Now you do the same to your bandwidth.
12 divide by 567, times by 1000.
Equals 21kb/s per ghash.
Replace 12 and 567 in all instances with your bandwidth and hashrate.
so means for 10 tera you need 210 meg?
am i correct?
Keep in mind that this traffic you are talking about (between the miner and the pool server) does not go out on the internet for typical solo mining setups. Why? Because you typically have your miner(s), pool server and bitcoind all on the same local area network. The only thing that goes out on the internet is your bitcoind network traffc. All the stratum / GBT stuff happens on the local network.
ok let s sum up
let s say i have 10 rig of 1 tera each.
let s say i have one sever where my bitcoin d is located .
with 1 rj45 going from my hub to the 10 mini rig i will be able to make all this works right?
but how much my server will need as bw ? 21 meg or 210 meg?
1) Traffic between miner(s) and pool server (stratum/GBT/getwork on LAN)
2) Traffic between pool server and bitcoind (none if both are on the same server)
3) Traffic between bitcoind and internet
Your initial post asked about internet traffic requirements (item 3)).
The answer to your example is 210 meg on the LAN, but this is talking about item 1). It does has nothing to do with internet connection speed.
Unless you are solving all the blocks on the network the internet traffic used by bitcoind has little to do with the hashrate of your solomining setup.
i wouldn't solo mine with only 1TH now.
I believe having 1TH mining hardware wouldnt mean problems with internet connection but with power supply... the amount of power that can go through each fuse is limited.
right power will be an issue also
so beside internet connection speed we ll have to deal with the powe issue as well
we ll need some industrial level wattage
Or hosting... It would be probably best when one could get industrial power prices too... the power-suppliers can do this with businesses. The result can be that one can buy power directly at power exchange for lower prices. But then... it would be a hassle to do this all i believe...
I believe having 1TH mining hardware wouldnt mean problems with internet connection but with power supply... the amount of power that can go through each fuse is limited.
right power will be an issue also
so beside internet connection speed we ll have to deal with the powe issue as well
we ll need some industrial level wattage
I believe having 1TH mining hardware wouldnt mean problems with internet connection but with power supply... the amount of power that can go through each fuse is limited.
Just call your local telco and get an OC-3072 installed. you'll be fine then.
More to the point DO you have 10 mini rigs or the equivalent on order?!
For pool mining:
Say your hashrate is 567MHash and that uses 12kb/s.
Divide by 567, times by 1000, that gives you 1GHash
Now you do the same to your bandwidth.
12 divide by 567, times by 1000.
Equals 21kb/s per ghash.
Replace 12 and 567 in all instances with your bandwidth and hashrate.
if i use your calculation it s showing 21 meg/terahashSay your hashrate is 567MHash and that uses 12kb/s.
Divide by 567, times by 1000, that gives you 1GHash
Now you do the same to your bandwidth.
12 divide by 567, times by 1000.
Equals 21kb/s per ghash.
Replace 12 and 567 in all instances with your bandwidth and hashrate.
so means for 10 tera you need 210 meg?
am i correct?
Keep in mind that this traffic you are talking about (between the miner and the pool server) does not go out on the internet for typical solo mining setups. Why? Because you typically have your miner(s), pool server and bitcoind all on the same local area network. The only thing that goes out on the internet is your bitcoind network traffc. All the stratum / GBT stuff happens on the local network.
ok let s sum up
let s say i have 10 rig of 1 tera each.
let s say i have one server where my bitcoin d is located .
with 1 rj45 going from my hub to the 10 mini rig i will be able to make all this works right?
but how much my server will need as bw ? 21 meg or 210 meg?
For pool mining:
Say your hashrate is 567MHash and that uses 12kb/s.
Divide by 567, times by 1000, that gives you 1GHash
Now you do the same to your bandwidth.
12 divide by 567, times by 1000.
Equals 21kb/s per ghash.
Replace 12 and 567 in all instances with your bandwidth and hashrate.
if i use your calculation it s showing 21 meg/terahashSay your hashrate is 567MHash and that uses 12kb/s.
Divide by 567, times by 1000, that gives you 1GHash
Now you do the same to your bandwidth.
12 divide by 567, times by 1000.
Equals 21kb/s per ghash.
Replace 12 and 567 in all instances with your bandwidth and hashrate.
so means for 10 tera you need 210 meg?
am i correct?
Keep in mind that this traffic you are talking about (between the miner and the pool server) does not go out on the internet for typical solo mining setups. Why? Because you typically have your miner(s), pool server and bitcoind all on the same local area network. The only thing that goes out on the internet is your bitcoind network traffc. All the stratum / GBT stuff happens on the local network.
If you have a terahash of hashing power you should be using a miner supporting stratum or gbt mining protocols. These protocols allow for variable difficulty rather than just difficulty one. This means that your hashers work harder get more credit for the work they do and don't need to contact that pool as frequently.
If the stratum/gbt protocol is working properly, I don't think 1 terahash consumes significantly more data than 10 GHash.
If the stratum/gbt protocol is working properly, I don't think 1 terahash consumes significantly more data than 10 GHash.
I ve never heard about gbt mining protocols?
do you have any links for the stratum and gbt protocols?
thanks in advance
If you have a terahash of hashing power you should be using a miner supporting stratum or gbt mining protocols. These protocols allow for variable difficulty rather than just difficulty one. This means that your hashers work harder get more credit for the work they do and don't need to contact that pool as frequently.
If the stratum/gbt protocol is working properly, I don't think 1 terahash consumes significantly more data than 10 GHash.
If the stratum/gbt protocol is working properly, I don't think 1 terahash consumes significantly more data than 10 GHash.
For pool mining:
Say your hashrate is 567MHash and that uses 12kb/s.
Divide by 567, times by 1000, that gives you 1GHash
Now you do the same to your bandwidth.
12 divide by 567, times by 1000.
Equals 21kb/s per ghash.
Replace 12 and 567 in all instances with your bandwidth and hashrate.
if i use your calculation it s showing 21 meg/terahashSay your hashrate is 567MHash and that uses 12kb/s.
Divide by 567, times by 1000, that gives you 1GHash
Now you do the same to your bandwidth.
12 divide by 567, times by 1000.
Equals 21kb/s per ghash.
Replace 12 and 567 in all instances with your bandwidth and hashrate.
so means for 10 tera you need 210 meg?
am i correct?
Basically you host your own pool..
Check out the mining software pools forum... they will get you started. Some popular ones are eloipool and slush's which both support stratum. If you have terahash of hashing power, I recommend you read up on this stuff fast.
The bandwidth usage will be on your private network between your hashers and your bitcoind. Bitcoind will be your big data hog unless you throttle it, but if you are dedicating your bandwidth to your pool... 1Mb/s should be sufficient for bitcoind.
Check out the mining software pools forum... they will get you started. Some popular ones are eloipool and slush's which both support stratum. If you have terahash of hashing power, I recommend you read up on this stuff fast.
The bandwidth usage will be on your private network between your hashers and your bitcoind. Bitcoind will be your big data hog unless you throttle it, but if you are dedicating your bandwidth to your pool... 1Mb/s should be sufficient for bitcoind.
For pool mining:
Say your hashrate is 567MHash and that uses 12kb/s.
Divide by 567, times by 1000, that gives you 1GHash
Now you do the same to your bandwidth.
12 divide by 567, times by 1000.
Equals 21kb/s per ghash.
Replace 12 and 567 in all instances with your bandwidth and hashrate.
Say your hashrate is 567MHash and that uses 12kb/s.
Divide by 567, times by 1000, that gives you 1GHash
Now you do the same to your bandwidth.
12 divide by 567, times by 1000.
Equals 21kb/s per ghash.
Replace 12 and 567 in all instances with your bandwidth and hashrate.
If you are solo mining and everything is local, your hash rate does not affect your internet connection speed requirements.
Instead, if you are running a full bitcoind node your connection requirements are dictated by the current transaction rate, blocksizes on the Bitcoin network AND most importantly the number of peer nodes connecting to you.
If you choose not to run a full bitcoind node, you save bandwidth because peers cannot directly connect to you. However when you solve a block it will take much longer for it propagate out and you risk orphaning it and losing the reward.
Edit: You can restrict the max. number of incoming peers to you bitcoind through a configuration parameter in bitcoinconf.
Instead, if you are running a full bitcoind node your connection requirements are dictated by the current transaction rate, blocksizes on the Bitcoin network AND most importantly the number of peer nodes connecting to you.
If you choose not to run a full bitcoind node, you save bandwidth because peers cannot directly connect to you. However when you solve a block it will take much longer for it propagate out and you risk orphaning it and losing the reward.
Edit: You can restrict the max. number of incoming peers to you bitcoind through a configuration parameter in bitcoinconf.
Jump to: