I have been happy with Bitfloor so far... been fairly flawless and I've done several ACH withdrawals without incident or delay. Glad I spent the time getting my automated platform converted over, which was a fairly painless process in and of itself.
|
|
|
That error is a result of your SSH client trying to forward X packets, not any particular setting in BAMT.
|
|
|
Yes, once I have everything setup like I want it, I will be slowly figuring out what's the most efficient firmware for each single.
|
|
|
Did you factor in the high stale rate compared to a normal pool?
|
|
|
GPUs aren't added to BFLS as backed hardware. The equivalent shares are added to me to make management easier. I think maybe that's where the confusion lies - there is no distributed shares out there that are not backed by BFL singles.
Electricity/maintenance rates are not factored into the shares at all, only pure hashrate vs shares, which is what the BFLS shares are. The maintenance/electricity is already factored into the 170/200 share split per unit, so 200 shares = 826 MH/s, which includes all maintenance/operational costs. Any additional costs from operating a GPU vs a BFL Single comes directly out of my pocket, not the BFLS dividends.
The "extra" shares that are currently showing are factored from my GPU farms at a rate of 826 MH/s per 200 shares, but this is purely because all the mining income is going to the same bucket and would be difficult to split out (I already tried to keep them separate and it was a nightmare accounting wise). So all my mining income is put into GLBSE and then dividends are paid out there - it makes the accounting much simpler.
Because of the negative response to the GPUs backing BFLS, I have not converted BFLS Futures shares and am instead waiting on actual BFLS hardware - that's why there is still BFLS Futures shares outstanding. I am the only one holding shares that are backed by GPUs and I will not be selling/distributing shares that are not backed by BFL hardware.
|
|
|
Basically what's happening is this:
I have a large farm, and trying to manage it individually based on the type and location was proving to be almost impossible and still maintain and efficient operation. As such, I pooled all of my mining resources one giant bucket, so they all mine to the same place and all the resulting revenues are generated together. The odd share arrangement are shares that I have allocated to myself for the hardware I have in the bucket at a rate of 826 MH/s per 200 shares, minus some fudge factor (so I end up shorting myself a few shares).
As I slowly sell off my GPU holdings, I am returning those shares to the BFLS bucket of unallocated shares (which is why you see the share count going down), and it will increase again when BFL finally gets me my remaining units.
|
|
|
Nope, site has been working fine for awhile now. There's about 1000 people connected at the moment.
|
|
|
Use Bitfloor. ACH withdrawals FTW
|
|
|
Mining went fairly well this week. I was waiting on one last payment to come in and it just came in, but the transfer to GLBSE is taking longer than I'd like (Yay for 1 hour + confirmations). As such, I am going to be headed to bed soon, so dividend payments will happen first thing in the morning (for me).
|
|
|
Ok, server is back up... it's going to take awhile for the shares to catch up since it's been caching for so long.
Might take up to an hour before they stabilize and everything is caught up and displaying properly.
|
|
|
Sorry guys, the file server is/was having some issues. They have been resolved now and the systems are all rebooting.
I am ordering new hardware next week to replace the current file server, but it should be fine until then, once everything comes back up. One of the boot disks failed and had to be replaced, but in the process and I also replaced one of the storage disks that was acting very slow (prefail most likely) and I'm hoping that's whats been causing the stuttering this past week.
Things should be up and running in about 10 - 20 minutes. Bringing up all the servers is not a fast process unfortunately. All the pool shares should be fine and I will look into the DNS issue, but DNS should have failed over to the backup DNS servers not located in this DC. Strange... but I will get that corrected as well.
|
|
|
I am going to be taking the website down in about an hour to replace some hardware. Pool should continue to run fine though... website will be offline for ~1/2 - 1 hour.
|
|
|
I am providing escrow for Blaztoize and RandomSeller for 4BTC. I have received 4 BTC from Blaztoize with txid b967e755e5c78f05f39e34cc5959ea90b06d121a689519debaccf11954650083
I will release the 4 BTC to RandomSeller once Balztoize verifies the accounts he is being sold are valid.
|
|
|
That will be a problem for me in about a month...
|
|
|
When was EMC down? I did not get any notifications... was the website down or the pool server?
Reading several threads, it almost seems as if it were only limited to some people, leading me to believe there was a backbone router somewhere that might have went tits up.
|
|
|
Stiftmaster: That problem is (obviously fixed) .
Punin: I'm not sure what you're talking about, can you elaborate?
|
|
|
Why is dwolla now saying it will take a month to complete a dwolla transfer. Is there another exchange? Waiting a month to get my money. They must be using it themselves.
Is there another exchange that can be used to get USD for BTC?
Bitfloor lets you withdraw via ACH. Faster than Dwolla and directly to your checking account.
|
|
|
Thanks guys, I appreciate it. It's true, I do run the pool for the miners... basically I just try to run a pool I want to mine in, which is why I started a pool in the first place; none of the pools offered the things I wanted. I'm definitely all about the miners and not about the money. Unfortunately, no Ferrari's for me from the pool proceeds, but I'm ok with that.
|
|
|
Our site is highly secure. Security experts agree a password at least 6 characters long with a mixture of upper and lowercase letters numbers and symbols is very secure. Our generated passwords meet this criteria, but are at least 8 characters long. Such a password is impossible to guess. There are two other things that make this secure: 1) The site allows only 7 login attempts before locking the user out so brute force attacks won't work. (otherwise brute forcing would take over 200 years to crack) 2) We use two-factor authentication which means an intruder must not only get the password right, but also your security answer to your security question. If interested please also check out this informative article on password security: http://www.baekdal.com/insights/password-security-usabilityWe don't allow users to set their own password to ensure they don't use a weak one, and also to ensure it's not duplicated from their other Web accounts. You may have heard LinkedIn and Last.fm databases with passwords were recently hacked. This makes all user online accounts vulnerable if they used the same password. Wow... talk about not understanding security. This post alone scares me away from this venture. Hint: Security questions are not 2FA. Hint: 6 characters are not enough.
|
|
|
|