Search content
Sort by
Showing 20 of 626 results by Keefe
Reward sent:
https://blockchain.info/tx/5a8f9e6513631c21201d6d85d0f69707612f4297c4a46a94535ae006bc3224da
https://blockchain.info/address/1HgwzAJdu8r5h1pviriV7KGnqc6fUHNqiq
Thanks everyone for playing.
https://blockchain.info/tx/5a8f9e6513631c21201d6d85d0f69707612f4297c4a46a94535ae006bc3224da
https://blockchain.info/address/1HgwzAJdu8r5h1pviriV7KGnqc6fUHNqiq
Thanks everyone for playing.
Confirmed. Thanks BurtW!
I'll just post it on his behalf...
11cea-1h
1HgwzAJdu8r5h1pviriV7KGnqc6fUHNqiq
Balance 0.1 BTC:
https://blockchain.info/address/1HgwzAJdu8r5h1pviriV7KGnqc6fUHNqiq
11cea-1h
1HgwzAJdu8r5h1pviriV7KGnqc6fUHNqiq
Code:
Your MinAddress must be less than 11cea
HESUI6voO5mpQPRPYbZinqi/+Xl3nnszgVFxeItBZrdyvqkPWpIvqUg9x3HMD3hyBuVd1S1jA+tazkuDOI88zJU=Balance 0.1 BTC:
https://blockchain.info/address/1HgwzAJdu8r5h1pviriV7KGnqc6fUHNqiq
Its done I think. But wow, an old address there!
I think BurtW will post when it's done. He said sometime Monday.
I'll just post it on his behalf...
11cea-1h
1HgwzAJdu8r5h1pviriV7KGnqc6fUHNqiq
Balance 0.1 BTC:
https://blockchain.info/address/1HgwzAJdu8r5h1pviriV7KGnqc6fUHNqiq
11cea-1h
1HgwzAJdu8r5h1pviriV7KGnqc6fUHNqiq
Code:
Your MinAddress must be less than 11cea
HESUI6voO5mpQPRPYbZinqi/+Xl3nnszgVFxeItBZrdyvqkPWpIvqUg9x3HMD3hyBuVd1S1jA+tazkuDOI88zJU=Balance 0.1 BTC:
https://blockchain.info/address/1HgwzAJdu8r5h1pviriV7KGnqc6fUHNqiq
Re: [ANN] US/North American Bitfury sales NEW STOCK ***NOW SHIPPING***
What would be a fair asking price for 9 PCI Hash cards and M board?
1.75 btc
I'd offer 2.25 BTC for that, if I was looking to buy more hardware.
| Username | Order Number | Payment Date | Payment Type | Product | Hashrate | Destination | Date Shipped | Date Received |
| Keefe | 220x | 13 October | Bitcoin | CoinCraft Desk | 600 GH/s | United States |
Position in shipping queue: 18x
Estimated delivery date: "last week of December" as of Nov 8
On Mar 7, I received a 1TH Desk for this order. It was shipped Mar 3, but was delayed 2 days because of import paperwork.
Nice to hear that you received the miner!
Actually funny... I have also order number #220X, paid same day 13 Oct / BTC... so maybe delivery is nearby also here...
They emailed me the tracking number the morning of Mar 3. If you didn't get that, you should contact them.
| Username | Order Number | Payment Date | Payment Type | Product | Hashrate | Destination | Date Shipped | Date Received |
| Keefe | 220x | 13 October | Bitcoin | CoinCraft Desk | 600 GH/s | United States |
Position in shipping queue: 18x
Estimated delivery date: "last week of December" as of Nov 8
On Mar 7, I received a 1TH Desk for this order. It was shipped Mar 3, but was delayed 2 days because of import paperwork.
Then it does seem that most or all of the failed bitcoin withdrawals occurred around Feb 10-12. There are at least 7 people complaining about this on CampBX's facebook page, and CampBX acknowledged at least ~20.
I just did a small deposit and withdraw as a test, and everything went quickly as it should.
I just did a small deposit and withdraw as a test, and everything went quickly as it should.
A friend of mine tried to withdraw ~6.5 BTC from his CampBX account 17 days ago. CampBX apparently never broadcast the transaction to the bitcoin network, since blockchain.info doesn't see even an unconfirmed transaction. He submitted a support ticket the next day, and it has now been 16 days with no response.
Re: [ANN] US/North American Bitfury sales NEW STOCK ***NOW SHIPPING***
Yeah that's clearly Bitmain - aka antminer.
MBP is 3x as expensive as Bitmain, at least at the nominal speeds. 2x as expensive when overclocked. The Bitfury guys are way out of touch with the mining market now.
Re: [ANN] US/North American Bitfury sales NEW STOCK ***NOW SHIPPING***
^what about price adjustments in the MBP store?
lulzdouble lulz,
We have 3 pages of cost adjustment questions and we get a reply about where he is going/meeting. With the btc price low now, antminer is better choice by a huge margin. 400 for 35gh +controller or 750 for 180gh standalone machine, tough choice right?
Aside: Hmm - so why does my BA fury board do 40.1GH/s paid to the pool?
What's up with the ones made by the guys here?
(or is that something to do with my cgminer driver?)
Yes these are real questions ... I've only had access to a small number of BA fury boards and basically no access at all to the boards listed here.
So I've no idea if my driver needs more work to support a lot of boards (yeah there really isn't much CPU power in an RPi) or if something else is going on.
I guess I need to spend some time on a large BA fury setup and work out what's going on with these crappy performance figures reported for the hardware here.
Then once I'm sure cgminer performs well with lots of boards, then the question here will be why on earth the boards here are rated so low.
What voltage do the BA boards run at? My best MBP boards can get just over 40GH when the weather's cool. But the main bottleneck seems to be the voltage regulator. Most of my boards are overvolted to around 0.86v, and the speeds are set just below where the regulator would cut out due to overcurrent/temp. At 0.86v, they could usually be clocked higher before getting too many errors, if it weren't for the current limit. I can determine that by turning off a couple chips and clocking higher until the errors start. Do the BA boards have a higher current limit than 30A?
^really hope it involves actual competitive pricing. For a more-stable, stackable/enclosed bitfury I would gladly add it to my growing collection of antminers - but only if they can get their shit together and
1) price in BTC - for the love of god.
2) price no higher then 10% above the antminer - those things are simple, elegant tanks that dont wobble, dont blow sd cards, and only require the single fan that they ship with. The only upside to the bitfury is saving ~1w/GH
1) price in BTC - for the love of god.
2) price no higher then 10% above the antminer - those things are simple, elegant tanks that dont wobble, dont blow sd cards, and only require the single fan that they ship with. The only upside to the bitfury is saving ~1w/GH
And saving 1W/GH only saves $0.88/GH per year at $0.10/kwh. Bitfury 55nm will be obsoleted by even more efficient tech within a year anyway, so it's not worth the huge premium Punin seems to think it is.
Well, I am at a loss of whats going on with my setup.
Got replacement card and the rig been mining about 12 hours.
Now I get notification of hashrate drop. I login to see a few of the cards at Zero.
Reboot Pi and only first 3 cards are hashing.
My room is at a constant 60F with fans blowing over the cards.
Got replacement card and the rig been mining about 12 hours.
Now I get notification of hashrate drop. I login to see a few of the cards at Zero.
Reboot Pi and only first 3 cards are hashing.
My room is at a constant 60F with fans blowing over the cards.
Set all chip speeds to something slow like 50 with autotune off, and restart chainmminer. If the problem persists, reseat the cards.
Re: [ANN]ASICMiner Publicly Looking for Potential Customers/Partners for New Chips
For comparison, Bitfury chips use a similar package, and I figure they dissipate about 2.5W in my overvolted rigs with just high-flow fans and no heatsinks. Bitfury chips use thermal pads to dissipate most of the heat through the PCB.
ok, now it's happening to me; again.
absolutely no hashing with one of my 14 card rigs. changed out SD cards and raspi. can login into admin page but no hashing. took rig apart and checked for any burnt boards (none) and blew out M board connector in case of excess oxidation (none apparent).
what were all the suggestions given for this frequent problem?
absolutely no hashing with one of my 14 card rigs. changed out SD cards and raspi. can login into admin page but no hashing. took rig apart and checked for any burnt boards (none) and blew out M board connector in case of excess oxidation (none apparent).
what were all the suggestions given for this frequent problem?
I've said it many times before, so I'll let you scroll up for details, but you need to check the output of chainminer and the proxies.
i only have 2 screens:
Code:
pi@192-168-7-243:~$ sudo screen -r
There are several suitable screens on:
2069..192-168-7-243 (28/01/14 23:39:27) (Detached)
2063..192-168-7-243 (28/01/14 23:39:27) (Detached)
There are several suitable screens on:
2069..192-168-7-243 (28/01/14 23:39:27) (Detached)
2063..192-168-7-243 (28/01/14 23:39:27) (Detached)
here's some of the output of 2069:
Code:
JOB 145 PROCESSED 0.005 sec [nonces:0 errors:368 spi:48 miso:67 dup:0] (queue:0)
JOB 146 PROCESSED 0.006 sec [nonces:0 errors:366 spi:51 miso:67 dup:0] (queue:0)
JOB 147 PROCESSED 0.011 sec [nonces:0 errors:427 spi:50 miso:67 dup:0] (queue:0)
JOB 148 PROCESSED 0.003 sec [nonces:0 errors:276 spi:34 miso:68 dup:0] (queue:0)
JOB 149 PROCESSED 0.002 sec [nonces:0 errors:121 spi:27 miso:56 dup:0] (queue:0)
JOB 150 PROCESSED 0.005 sec [nonces:0 errors:357 spi:42 miso:65 dup:0] (queue:0)
JOB 151 PROCESSED 0.007 sec [nonces:0 errors:484 spi:33 miso:64 dup:0] (queue:0)
JOB 152 PROCESSED 0.005 sec [nonces:0 errors:394 spi:21 miso:68 dup:0] (queue:0)
JOB 153 PROCESSED 0.007 sec [nonces:0 errors:548 spi:55 miso:61 dup:2] (queue:0)
JOB 154 PROCESSED 0.005 sec [nonces:0 errors:426 spi:57 miso:60 dup:0] (queue:0)
JOB 155 PROCESSED 0.006 sec [nonces:0 errors:524 spi:40 miso:68 dup:2] (queue:0)
JOB 156 PROCESSED 0.005 sec [nonces:0 errors:382 spi:52 miso:65 dup:0] (queue:0)
JOB 157 PROCESSED 0.006 sec [nonces:0 errors:373 spi:41 miso:63 dup:0] (queue:0)
JOB 158 PROCESSED 0.004 sec [nonces:0 errors:357 spi:11 miso:58 dup:0] (queue:0)
JOB 159 PROCESSED 0.006 sec [nonces:0 errors:420 spi:56 miso:64 dup:0] (queue:0)
JOB 146 PROCESSED 0.006 sec [nonces:0 errors:366 spi:51 miso:67 dup:0] (queue:0)
JOB 147 PROCESSED 0.011 sec [nonces:0 errors:427 spi:50 miso:67 dup:0] (queue:0)
JOB 148 PROCESSED 0.003 sec [nonces:0 errors:276 spi:34 miso:68 dup:0] (queue:0)
JOB 149 PROCESSED 0.002 sec [nonces:0 errors:121 spi:27 miso:56 dup:0] (queue:0)
JOB 150 PROCESSED 0.005 sec [nonces:0 errors:357 spi:42 miso:65 dup:0] (queue:0)
JOB 151 PROCESSED 0.007 sec [nonces:0 errors:484 spi:33 miso:64 dup:0] (queue:0)
JOB 152 PROCESSED 0.005 sec [nonces:0 errors:394 spi:21 miso:68 dup:0] (queue:0)
JOB 153 PROCESSED 0.007 sec [nonces:0 errors:548 spi:55 miso:61 dup:2] (queue:0)
JOB 154 PROCESSED 0.005 sec [nonces:0 errors:426 spi:57 miso:60 dup:0] (queue:0)
JOB 155 PROCESSED 0.006 sec [nonces:0 errors:524 spi:40 miso:68 dup:2] (queue:0)
JOB 156 PROCESSED 0.005 sec [nonces:0 errors:382 spi:52 miso:65 dup:0] (queue:0)
JOB 157 PROCESSED 0.006 sec [nonces:0 errors:373 spi:41 miso:63 dup:0] (queue:0)
JOB 158 PROCESSED 0.004 sec [nonces:0 errors:357 spi:11 miso:58 dup:0] (queue:0)
JOB 159 PROCESSED 0.006 sec [nonces:0 errors:420 spi:56 miso:64 dup:0] (queue:0)
and some of 2063:
Code:
2014-01-28 23:43:18,070 INFO proxy getwork_listener._on_authorized # Worker '243' asks for new work
2014-01-28 23:43:19,099 INFO proxy getwork_listener._on_authorized # Worker '243' asks for new work
2014-01-28 23:43:20,026 INFO proxy getwork_listener._on_authorized # Worker '243' asks for new work
2014-01-28 23:43:21,051 INFO proxy getwork_listener._on_authorized # Worker '243' asks for new work
2014-01-28 23:43:22,077 INFO proxy getwork_listener._on_authorized # Worker '243' asks for new work
2014-01-28 23:43:23,104 INFO proxy getwork_listener._on_authorized # Worker '243' asks for new work
2014-01-28 23:43:24,031 INFO proxy getwork_listener._on_authorized # Worker '243' asks for new work
2014-01-28 23:43:25,057 INFO proxy getwork_listener._on_authorized # Worker '243' asks for new work
2014-01-28 23:43:26,084 INFO proxy getwork_listener._on_authorized # Worker '243' asks for new work
2014-01-28 23:43:27,109 INFO proxy getwork_listener._on_authorized # Worker '243' asks for new work
2014-01-28 23:43:28,035 INFO proxy getwork_listener._on_authorized # Worker '243' asks for new work
2014-01-28 23:43:29,061 INFO proxy getwork_listener._on_authorized # Worker '243' asks for new work
2014-01-28 23:43:30,088 INFO proxy getwork_listener._on_authorized # Worker '243' asks for new work
2014-01-28 23:44:06,631 DEBUG protocol protocol.lineReceived # > {u'params': [u'37f1', u'88e467b50f54143fe5be3226344ec74608e47c53696c43740000000000000000', u'01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff2703495104062f503253482f04eb40e85208', u'0d2f7374726174756d506f6f6c2f00000000015d1fe595000000001976a9141157b2fc397d2cf3161313d220017d0dba368db588ac00000000', [u'3f23b91dd29e182079db07b2ba415833c38118042b59ce5b212fca23d27092de', u'66dd511b2faf371bb39c8d93932d028117a97d5295a969757ce7a18bacfd5773', u'9d880202be148bc6c31caddc7562a36ea29676a3fde0200926fd39eae9a2f578', u'0c6d9ee7f9d8854354660349dd09689810db94e36e83d266f767f55267b02642', u'60797fb71da5a528d5244dec03eef24a83006f15eb4f82077de8d048d4c198ac', u'9fd0193634d5b229f850792b0fdebabfc359b5818e01710bed9174002f62a8ca', u'a07dadf4444bda448cc6db75f4060857cae3e0cf04b3bf465876caeb77a88844', u'cccc0a87384a359e2e019f4cb5857c7436c4f599834fb9bd245ddc7f834755b2', u'b8017af8253690aba7b706cfbaa635cc30d4e12736ff8a4518173d713470a8b2', u'bdb8e2711c4a3755bbb36127598da1af92e671ad568928273bbd8177a24fc398'], u'00000002', u'1901f52c', u'52e840e3', False], u'id': None, u'method': u'mining.notify'}
2014-01-28 23:44:06,634 INFO proxy client_service.handle_event # New job 37f1 for prevhash 88e467b5, clean_jobs=False
2014-01-28 23:43:19,099 INFO proxy getwork_listener._on_authorized # Worker '243' asks for new work
2014-01-28 23:43:20,026 INFO proxy getwork_listener._on_authorized # Worker '243' asks for new work
2014-01-28 23:43:21,051 INFO proxy getwork_listener._on_authorized # Worker '243' asks for new work
2014-01-28 23:43:22,077 INFO proxy getwork_listener._on_authorized # Worker '243' asks for new work
2014-01-28 23:43:23,104 INFO proxy getwork_listener._on_authorized # Worker '243' asks for new work
2014-01-28 23:43:24,031 INFO proxy getwork_listener._on_authorized # Worker '243' asks for new work
2014-01-28 23:43:25,057 INFO proxy getwork_listener._on_authorized # Worker '243' asks for new work
2014-01-28 23:43:26,084 INFO proxy getwork_listener._on_authorized # Worker '243' asks for new work
2014-01-28 23:43:27,109 INFO proxy getwork_listener._on_authorized # Worker '243' asks for new work
2014-01-28 23:43:28,035 INFO proxy getwork_listener._on_authorized # Worker '243' asks for new work
2014-01-28 23:43:29,061 INFO proxy getwork_listener._on_authorized # Worker '243' asks for new work
2014-01-28 23:43:30,088 INFO proxy getwork_listener._on_authorized # Worker '243' asks for new work
2014-01-28 23:44:06,631 DEBUG protocol protocol.lineReceived # > {u'params': [u'37f1', u'88e467b50f54143fe5be3226344ec74608e47c53696c43740000000000000000', u'01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff2703495104062f503253482f04eb40e85208', u'0d2f7374726174756d506f6f6c2f00000000015d1fe595000000001976a9141157b2fc397d2cf3161313d220017d0dba368db588ac00000000', [u'3f23b91dd29e182079db07b2ba415833c38118042b59ce5b212fca23d27092de', u'66dd511b2faf371bb39c8d93932d028117a97d5295a969757ce7a18bacfd5773', u'9d880202be148bc6c31caddc7562a36ea29676a3fde0200926fd39eae9a2f578', u'0c6d9ee7f9d8854354660349dd09689810db94e36e83d266f767f55267b02642', u'60797fb71da5a528d5244dec03eef24a83006f15eb4f82077de8d048d4c198ac', u'9fd0193634d5b229f850792b0fdebabfc359b5818e01710bed9174002f62a8ca', u'a07dadf4444bda448cc6db75f4060857cae3e0cf04b3bf465876caeb77a88844', u'cccc0a87384a359e2e019f4cb5857c7436c4f599834fb9bd245ddc7f834755b2', u'b8017af8253690aba7b706cfbaa635cc30d4e12736ff8a4518173d713470a8b2', u'bdb8e2711c4a3755bbb36127598da1af92e671ad568928273bbd8177a24fc398'], u'00000002', u'1901f52c', u'52e840e3', False], u'id': None, u'method': u'mining.notify'}
2014-01-28 23:44:06,634 INFO proxy client_service.handle_event # New job 37f1 for prevhash 88e467b5, clean_jobs=False
Hmm, that hasn't happened to me yet, so I don't know what's the problem. It seems the chips are getting work but are returning tons of bad nonces and other errors. Is this a multi-bank M-board? My first thought is a bad connection, but it's too coincidental for all banks to do that at once. Maybe one of the voltage regulators on the M-board went bad? One should be ~1.8v and the other ~5v. The 5v just powers the rPi, so must be ok. But I can imagine bad 1.8v for chip comm causing weird results like this.
ok, now it's happening to me; again.
absolutely no hashing with one of my 14 card rigs. changed out SD cards and raspi. can login into admin page but no hashing. took rig apart and checked for any burnt boards (none) and blew out M board connector in case of excess oxidation (none apparent).
what were all the suggestions given for this frequent problem?
absolutely no hashing with one of my 14 card rigs. changed out SD cards and raspi. can login into admin page but no hashing. took rig apart and checked for any burnt boards (none) and blew out M board connector in case of excess oxidation (none apparent).
what were all the suggestions given for this frequent problem?
I've said it many times before, so I'll let you scroll up for details, but you need to check the output of chainminer and the proxies.
Re: Bitstamp - wanted to withdraw money and was hit with these weird KYC questions
...
I hv refused to answer such questions and said i will move all my coins and that they already hv my ID.
I also said i will sue anyone who has asked them to do this namely the bank, and they can see i hv quite a fair few coins in my account. I am thinking of moving them before they see the ticket, which i excerpt below tho its been edited for my security:
...
I hv refused to answer such questions and said i will move all my coins and that they already hv my ID.
I also said i will sue anyone who has asked them to do this namely the bank, and they can see i hv quite a fair few coins in my account. I am thinking of moving them before they see the ticket, which i excerpt below tho its been edited for my security:
...
I look forward to hearing whether they give you any trouble when you try to withdraw all your BTC without answering their questions.