I don think bitmixer will release any info unless the department want from them
else it will just broke thier business .
I don't think anyone else would look at bitmixer any differently if they gave up those details. They are doing the right thing in this instance. Really? I'd certainly campaign for users to boycott them. WTF is the point of mixers if the community is going to arbitrarily decide when mixers ought to betray the trust of their customers? This is a much bigger question than just saying, "just this one time." You are either for privacy, or against it when it doesn't suit you. Pick one. If the latter, then just denounce the very premise of mixers already. What country is this service located? They might be legally obliged to keep a record and cooperate with the authorities. Theft of this amount of money is a felony in the US (over 10 years prison). If they don't disclose the information and did not keep a record, they might be legally responsible both criminally and open to civil lawsuit. Probably none of the mixers are operating from US, not even from some properly regulated EU country. So catching a mixer owner is not an easy deal. But, if they're caught, it'll be difficult for them to evade imprisonment. Only if they knew that they were aiding and abetting some crime, and I guess the penalties for that would vary a lot by country, no clue. I could think of a few good reasons why someone might want to use such a thing for entirely legal purposes... bitcoind stuff is stored in ramfs on my machine, but I guess I couldnt know if it was being actively monitored or logged. i'd think germany would have laws to prevent such a thing, w/o something akin to a search warrant |
|
|
|
Awesome work windpath  Can I ask, what is the end game for hosting a 0% p2pool node? Obviously it costs you money. One is to support a decentralized bitcoin I am sure, but what else are your goals? I'm running a 0% fee node because it cost me a pittance to run it. I can contribute that pittance to keeping the network going. M Yeah, I've already had a dedicated server for years, p2pool doesn't take much resources. I ran a bitcoin one for a long time, now it's on doge for the last 3 or 4 months. (nogleg.com:9555, hoho) Oh, I did put a 0.1% fee, 'cause of several people thinking there must be shenanigans going on |
|
|
|
Hello,
I am looking to buy 1 spray bottle of Liquid ass for about 0,015 BTC including shipping.
Is this possible?
Just to say, I have gotten scammed too many times, so either use escrow or you go first, although I am not sure how I should use escrow because I never used it before.
I recommend the Tex-ASS |
|
|
|
|
I need some more negro. Badly.
|
|
|
|
again..  can be used in store or online, from USA, Puerto Rico, and Canada for .065 bitcoins, ~40USD, 80% face value |
|
|
|
hi
can you tell me the price of these trackers separately :
HDWINGS
WIHD
HDFRENCH
thanks a lot
hdwings as in hdwing.com? |
|
|
|
I've always thought that bitcoin was doomed to fail because of the carelessness/ignorance/whatever you want to call it of most people. You can just use Facebook as an example of how easy it is to get your random joe to install all sorts of crap on their computers by clicking random links that promise free credits, pr0n, whatever. Thanks Javascript! Ah, and then we have wireless and public networks and what not. I'm sure most people will keep their bitcoin wallets on their main computer, easily accessible (and many w/o even a backup). If they use some online wallet service, then someone could just grab their password over unprotected network, keylogger, etc. (as well as targeting this online wallet service itself, if it's not set up properly) Most of the people in the industrialized world have internet access now, sure as hell isn't the 80's anymore... speaking of which, I was sad when Operation Sundevil owned killer  |
|
|
|
Hi, newbie here.
I want to modify bitcoin.conf to add RPCuser and RPCpassword lines but can't find bitcoin.conf in the place it suppose to be c:\Users\User\Appdata\Roaming, there is no Bitcoin folder there.
I m using Windows 7 64 and Bitcoin Core 0.9.2.1.
I am in the right place to ask this question?
You can use internal search function in windows. Not if it doesn't generate a bitcoin.conf file to begin with. I've had all that junk turned off for some godawful long period of time, anyway. Just slows things down. If you need to find something, i.e. bitcoin.conf, go to command prompt, root directory, and type dir /s bitcoin.conf |
|
|
|
i sold both of them on facebook here is a screenshot of the code use....  yeah, i still have an extra code that i got by mistake, re: asking them for one because I thought I hadn't gotten one when I had i was under the impression they no longer worked, guess i was wrong shoulda sold them a few months ago, tho i guess you're taking paypal, so someone could always charge back if you werent legit |
|
|
|
The only way this works is to have the buyer use the "gift" feature of Paypal to give the seller money. This is not reversible.
Nope, this is still reversible. Gift payment is reversible but not easily, you have to prove that your account was hacked or you did not transact that transaction. gift is only a secure payment if it was paid via paypal balance, if funded via a cc it can be chargebacked. Unless that paypal balance was funded with a credit card, heh heh. |
|
|
|
|
OK, so who are these two people that bought them and successfully used?
|
|
|
|
if you're using windows 7, use netlimiter www.netlimiter.comnetlimiter 4 may still be free too, im not sure. that works with windows 8 |
|
|
|
|
It goes incredibly slow depending on what peers you're connected to. If you're connected to some bum peers, sometimes it'll just stop until a new block hits the network.
I only connect to one node when I'm downloading the blockchain
|
|
|
|
I still can't check the getaddr.bitnodes.io site with my public address:8333.
It comes up with address not connected. I know I've got outgoing connections because my ethernet monitor sometimes sends at 150Kb/s without anything running and I've got 12 connections.
Is there something wrong with that site?
If it can't access your address, then it's not listed as a valid node.. i.e. it's full, nobody else can connect, including getaddr ed: this is with the assumption that you did what the fellow up above said to, and set to maxconnections 12. |
|
|
|
I was using the latest github pull yesterday... or trying to anyway. Whenever I restarted bitcoin it had to reindex, so I reverted ed: actually, I am guessing this person had the same issue, since he is on 0.9.99 as well, and usually has no problems with connecting to me. on the second log, note the block counts 2014-07-09 07:29:05 accepted connection 108.45.xx.xx:36528
2014-07-09 07:29:05 send version message: version 70002, blocks=309898, us=5.9.xx.xx:8333, them=108.45.xx.xx:36528, peer=108.45.xx.xx:36528
2014-07-09 07:29:05 receive version message: /Satoshi:0.9.99/: version 70002, blocks=0, us=5.9.xx.xx:8333, them=108.45.xx.xx:8333, peer=108.45.xx.xx:36528
2014-07-09 07:29:05
PROCESSMESSAGE: INVALID MESSAGESTART
2014-07-09 07:29:06
PROCESSMESSAGE: ERRORS IN HEADER addr
2014-07-09 07:29:07
PROCESSMESSAGE: ERRORS IN HEADER getdata
2014-07-09 07:29:08 ProcessMessages(getdata, 2304 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:29:08 ProcessMessage(getdata, 2304 bytes) FAILED
2014-07-09 07:29:08
PROCESSMESSAGE: INVALID MESSAGESTART
2014-07-09 07:29:09 ProcessMessages(getdata, 36 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:29:09 ProcessMessage(getdata, 36 bytes) FAILED
2014-07-09 07:29:09
PROCESSMESSAGE: ERRORS IN HEADER gtdata
2014-07-09 07:29:12
PROCESSMESSAGE: INVALID MESSAGESTART
2014-07-09 07:29:14
PROCESSMESSAGE: INVALID MESSAGESTART
2014-07-09 07:29:18
PROCESSMESSAGE: INVALID MESSAGESTART
2014-07-09 07:29:19 ProcessMessages(getdata, 36 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:29:19 ProcessMessage(getdata, 36 bytes) FAILED
2014-07-09 07:29:22 ProcessMessages(addr, 30 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:29:22 ProcessMessage(addr, 30 bytes) FAILED
2014-07-09 07:29:28
PROCESSMESSAGE: ERRORS IN HEADER getdata
2014-07-09 07:29:34
PROCESSMESSAGE: INVALID MESSAGESTART
2014-07-09 07:29:35 ProcessMessages(getdata, 36 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:29:35 ProcessMessage(getdata, 36 bytes) FAILED
2014-07-09 07:29:37
PROCESSMESSAGE: ERRORS IN HEADER getdata
2014-07-09 07:29:37 ProcessMessages(getdata, 36 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:29:37 ProcessMessage(getdata, 36 bytes) FAILED
2014-07-09 07:29:38
PROCESSMESSAGE: ERRORS IN HEADER getdata
2014-07-09 07:29:41
PROCESSMESSAGE: ERRORS IN HEADER getdataÝ
2014-07-09 07:29:42
PROCESSMESSAGE: INVALID MESSAGESTART
2014-07-09 07:29:43
PROCESSMESSAGE: ERRORS IN HEADER getdata
2014-07-09 07:29:46
PROCESSMESSAGE: ERRORS IN HEADER getdata
2014-07-09 07:29:47
PROCESSMESSAGE: INVALID MESSAGESTART
2014-07-09 07:29:47 ProcessMessages(getdata, 38 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:29:47 ProcessMessage(getdata, 38 bytes) FAILED
2014-07-09 07:29:48
PROCESSMESSAGE: INVALID MESSAGESTART
2014-07-09 07:29:48
PROCESSMESSAGE: INVALID MESSAGESTART
2014-07-09 07:29:53 ProcessMessages(getdata, 36 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:29:53 ProcessMessage(getdata, 36 bytes) FAILED
2014-07-09 07:30:01 ProcessMessages(getdata, 36 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:30:01 ProcessMessage(getdata, 36 bytes) FAILED
2014-07-09 07:30:02 ProcessMessages(getdata, 36 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:30:02 ProcessMessage(getdata, 36 bytes) FAILED
2014-07-09 07:30:03 ProcessMessages(getdata, 36 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:30:03 ProcessMessage(getdata, 36 bytes) FAILED
2014-07-09 07:30:04
PROCESSMESSAGE: ERRORS IN HEADER geÌtata
2014-07-09 07:30:05 ProcessMessages(getdata, 38 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:30:05 ProcessMessage(getdata, 38 bytes) FAILED
2014-07-09 07:30:06 ProcessMessages(getdata, 36 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:30:06 ProcessMessage(getdata, 36 bytes) FAILED
2014-07-09 07:30:06
PROCESSMESSAGE: INVALID MESSAGESTART
2014-07-09 07:30:08
PROCESSMESSAGE: ERRORS IN HEADER g×tdata
2014-07-09 07:30:08 ProcessMessages(getdata, 36 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:30:08 ProcessMessage(getdata, 36 bytes) FAILED
2014-07-09 07:30:11 ProcessMessages(getdata, 36 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:30:11 ProcessMessage(getdata, 36 bytes) FAILED
2014-07-09 07:30:16
PROCESSMESSAGE: ERRORS IN HEADER getdataè
2014-07-09 07:30:17
PROCESSMESSAGE: ERRORS IN HEADER getdata
2014-07-09 07:30:26 ProcessMessages(getdata, 36 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:30:26 ProcessMessage(getdata, 36 bytes) FAILED
2014-07-09 07:30:27
PROCESSMESSAGE: INVALID MESSAGESTART
2014-07-09 07:30:27 ProcessMessages(getdata, 36 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:30:27 ProcessMessage(getdata, 36 bytes) FAILED
2014-07-09 07:30:29 ProcessMessages(getdata, 36 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:30:29 ProcessMessage(getdata, 36 bytes) FAILED
2014-07-09 07:30:29
PROCESSMESSAGE: INVALID MESSAGESTART
2014-07-09 07:30:31
PROCESSMESSAGE: INVALID MESSAGESTART
2014-07-09 07:30:33
PROCESSMESSAGE: ERRORS IN HEADER °etdata
2014-07-09 07:30:36
PROCESSMESSAGE: INVALID MESSAGESTART
2014-07-09 07:30:41
PROCESSMESSAGE: ERRORS IN HEADER getdta
2014-07-09 07:30:52 ProcessMessages(getdata, 35 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:30:52 ProcessMessage(getdata, 35 bytes) FAILED
2014-07-09 07:30:55
PROCESSMESSAGE: INVALID MESSAGESTART
2014-07-09 07:30:57 ProcessMessages(getdata, 35 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:30:57 ProcessMessage(getdata, 35 bytes) FAILED
2014-07-09 07:31:00
PROCESSMESSAGE: ERRORS IN HEADER gÐetdata
2014-07-09 07:31:04 ProcessMessages(getdata, 36 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:31:04 ProcessMessage(getdata, 36 bytes) FAILED
2014-07-09 07:31:06
PROCESSMESSAGE: ERRORS IN HEADER getdata
2014-07-09 07:31:07 ProcessMessages(getdata, 36 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:31:07 ProcessMessage(getdata, 36 bytes) FAILED
2014-07-09 07:31:08
PROCESSMESSAGE: INVALID MESSAGESTART
2014-07-09 07:31:14
PROCESSMESSAGE: ERRORS IN HEADER égetdata
2014-07-09 07:31:19
PROCESSMESSAGE: ERRORS IN HEADER get¯ata
2014-07-09 07:31:21
PROCESSMESSAGE: ERRORS IN HEADER göetdata
2014-07-09 07:31:23 ProcessMessages(getdata, 36 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:31:23 ProcessMessage(getdata, 36 bytes) FAILED
2014-07-09 07:31:24
PROCESSMESSAGE: INVALID MESSAGESTART
2014-07-09 07:31:26
PROCESSMESSAGE: INVALID MESSAGESTART
2014-07-09 07:31:28 ProcessMessages(getdata, 36 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:31:28 ProcessMessage(getdata, 36 bytes) FAILED
2014-07-09 07:31:29
PROCESSMESSAGE: INVALID MESSAGESTART
2014-07-09 07:31:30 ProcessMessages(getdata, 36 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:31:30 ProcessMessage(getdata, 36 bytes) FAILED
2014-07-09 07:31:32 ProcessMessages(getdata, 36 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:31:32 ProcessMessage(getdata, 36 bytes) FAILED
2014-07-09 07:31:33 ProcessMessages(getdata, 36 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:31:33 ProcessMessage(getdata, 36 bytes) FAILED
2014-07-09 07:31:34
PROCESSMESSAGE: INVALID MESSAGESTART
2014-07-09 07:31:34
PROCESSMESSAGE: ERRORS IN HEADER geÀtdata
2014-07-09 07:31:46 ProcessMessages(getdata, 37 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:31:46 ProcessMessage(getdata, 37 bytes) FAILED
2014-07-09 07:31:47
PROCESSMESSAGE: INVALID MESSAGESTART
2014-07-09 07:31:48
PROCESSMESSAGE: ERRORS IN HEADER getdata
2014-07-09 07:31:52
PROCESSMESSAGE: INVALID MESSAGESTART
2014-07-09 07:31:54 ProcessMessages(getdata, 36 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:31:54 ProcessMessage(getdata, 36 bytes) FAILED
2014-07-09 07:31:59 ProcessMessages(getdata, 36 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:31:59 ProcessMessage(getdata, 36 bytes) FAILED
2014-07-09 07:32:04
PROCESSMESSAGE: INVALID MESSAGESTART
2014-07-09 07:32:11
PROCESSMESSAGE: ERRORS IN HEADER gÎetdata
2014-07-09 07:32:14
PROCESSMESSAGE: INVALID MESSAGESTART
2014-07-09 07:32:15
PROCESSMESSAGE: ERRORS IN HEADER getdata
2014-07-09 07:32:18
PROCESSMESSAGE: INVALID MESSAGESTART
2014-07-09 07:32:19 ProcessMessages(getdata, 36 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:32:19 ProcessMessage(getdata, 36 bytes) FAILED
2014-07-09 07:32:19 ProcessMessages(getdata, 36 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-09 07:32:19 ProcessMessage(getdata, 36 bytes) FAILED
2014-07-09 07:32:21
PROCESSMESSAGE: ERRORS IN HEADER gtdata
2014-07-09 07:32:24
PROCESSMESSAGE: ERRORS IN HEADER getdata
2014-07-09 07:32:28 disconnecting node 108.45.xx.xx:36528
2014-07-03 11:29:53 accepted connection 108.45.xx.xx:57549
2014-07-03 11:29:53 send version message: version 70002, blocks=309011, us=5.9.xx.xx:8333, them=108.45.xx.xx:57549, peer=108.45.xx.xx:57549
2014-07-03 11:29:53 receive version message: /Satoshi:0.9.99/: version 70002, blocks=309011, us=5.9.xx.xx:8333, them=108.45.xx.xx:8333, peer=108.45.xx.xx:57549
2014-07-03 17:14:05 disconnecting node 108.45.xx.xx:57549
2014-07-03 21:14:23 accepted connection 108.45.xx.xx:39882
2014-07-03 21:14:23 send version message: version 70002, blocks=309061, us=5.9.xx.xx:8333, them=108.45.xx.xx:39882, peer=108.45.xx.xx:39882
2014-07-03 21:14:23 receive version message: /Satoshi:0.9.99/: version 70002, blocks=309061, us=5.9.xx.xx:8333, them=108.45.xx.xx:8333, peer=108.45.xx.xx:39882
2014-07-03 22:17:21 disconnecting node 108.45.xx.xx:39882
2014-07-04 05:25:58 accepted connection 108.45.xx.xx:36186
2014-07-04 05:25:58 send version message: version 70002, blocks=309116, us=5.9.xx.xx:8333, them=108.45.xx.xx:36186, peer=108.45.xx.xx:36186
2014-07-04 05:25:58 receive version message: /Satoshi:0.9.99/: version 70002, blocks=309065, us=5.9.xx.xx:8333, them=108.45.xx.xx:8333, peer=108.45.xx.xx:36186
2014-07-04 05:41:58 disconnecting node 108.45.xx.xx:36186
2014-07-04 05:42:19 accepted connection 108.45.xx.xx:40326
2014-07-04 05:42:19 send version message: version 70002, blocks=309118, us=5.9.xx.xx:8333, them=108.45.xx.xx:40326, peer=108.45.xx.xx:40326
2014-07-04 05:42:19 receive version message: /Satoshi:0.9.99/: version 70002, blocks=309118, us=5.9.xx.xx:8333, them=108.45.xx.xx:8333, peer=108.45.xx.xx:40326
2014-07-04 05:43:22 disconnecting node 108.45.xx.xx:40326
2014-07-04 05:44:32 accepted connection 108.45.xx.xx:41563
2014-07-04 05:44:32 send version message: version 70002, blocks=309118, us=5.9.xx.xx:8333, them=108.45.xx.xx:41563, peer=108.45.xx.xx:41563
2014-07-04 05:44:32 receive version message: /Satoshi:0.9.99/: version 70002, blocks=309118, us=5.9.xx.xx:8333, them=108.45.xx.xx:8333, peer=108.45.xx.xx:41563
2014-07-04 05:49:06 disconnecting node 108.45.xx.xx:41563
2014-07-04 05:59:24 accepted connection 108.45.xx.xx:56392
2014-07-04 05:59:24 send version message: version 70002, blocks=309121, us=5.9.xx.xx:8333, them=108.45.xx.xx:56392, peer=108.45.xx.xx:56392
2014-07-04 05:59:24 receive version message: /Satoshi:0.9.99/: version 70002, blocks=309120, us=5.9.xx.xx:8333, them=108.45.xx.xx:8333, peer=108.45.xx.xx:56392
2014-07-04 06:01:01 disconnecting node 108.45.xx.xx:56392
2014-07-04 07:12:19 accepted connection 108.45.xx.xx:34793
2014-07-04 07:12:19 send version message: version 70002, blocks=309127, us=5.9.xx.xx:8333, them=108.45.xx.xx:34793, peer=108.45.xx.xx:34793
2014-07-04 07:12:19 receive version message: /Satoshi:0.9.99/: version 70002, blocks=309121, us=5.9.xx.xx:8333, them=108.45.xx.xx:8333, peer=108.45.xx.xx:34793
2014-07-04 09:00:26 disconnecting node 108.45.xx.xx:34793
2014-07-04 09:09:37 accepted connection 108.45.xx.xx:49044
2014-07-04 09:09:37 send version message: version 70002, blocks=309136, us=5.9.xx.xx:8333, them=108.45.xx.xx:49044, peer=108.45.xx.xx:49044
2014-07-04 09:09:37 receive version message: /Satoshi:0.9.99/: version 70002, blocks=309135, us=5.9.xx.xx:8333, them=108.45.xx.xx:8333, peer=108.45.xx.xx:49044
2014-07-04 09:42:41 disconnecting node 108.45.xx.xx:49044
2014-07-04 09:43:26 accepted connection 108.45.xx.xx:53912
2014-07-04 09:43:26 send version message: version 70002, blocks=309140, us=5.9.xx.xx:8333, them=108.45.xx.xx:53912, peer=108.45.xx.xx:53912
2014-07-04 09:43:26 receive version message: /Satoshi:0.9.99/: version 70002, blocks=309140, us=5.9.xx.xx:8333, them=108.45.xx.xx:8333, peer=108.45.xx.xx:53912
2014-07-04 10:05:13 disconnecting node 108.45.xx.xx:53912
2014-07-04 10:08:28 accepted connection 108.45.xx.xx:59373
2014-07-04 10:08:28 send version message: version 70002, blocks=309144, us=5.9.xx.xx:8333, them=108.45.xx.xx:59373, peer=108.45.xx.xx:59373
2014-07-04 10:08:28 receive version message: /Satoshi:0.9.99/: version 70002, blocks=309144, us=5.9.xx.xx:8333, them=108.45.xx.xx:8333, peer=108.45.xx.xx:59373
2014-07-04 10:32:13 disconnecting node 108.45.xx.xx:59373
2014-07-04 11:04:19 accepted connection 108.45.xx.xx:52769
2014-07-04 11:04:19 send version message: version 70002, blocks=309152, us=5.9.xx.xx:8333, them=108.45.xx.xx:52769, peer=108.45.xx.xx:52769
2014-07-04 11:04:19 receive version message: /Satoshi:0.9.99/: version 70002, blocks=309147, us=5.9.xx.xx:8333, them=108.45.xx.xx:8333, peer=108.45.xx.xx:52769
2014-07-04 11:16:34 disconnecting node 108.45.xx.xx:52769
2014-07-04 11:22:23 accepted connection 108.45.xx.xx:58560
2014-07-04 11:22:23 send version message: version 70002, blocks=309154, us=5.9.xx.xx:8333, them=108.45.xx.xx:58560, peer=108.45.xx.xx:58560
2014-07-04 11:22:23 receive version message: /Satoshi:0.9.99/: version 70002, blocks=309154, us=5.9.xx.xx:8333, them=108.45.xx.xx:8333, peer=108.45.xx.xx:58560
2014-07-04 11:34:29 disconnecting node 108.45.xx.xx:58560
2014-07-04 11:54:27 accepted connection 108.45.xx.xx:35789
2014-07-04 11:54:27 send version message: version 70002, blocks=309158, us=5.9.xx.xx:8333, them=108.45.xx.xx:35789, peer=108.45.xx.xx:35789
2014-07-04 11:54:27 receive version message: /Satoshi:0.9.99/: version 70002, blocks=309154, us=5.9.xx.xx:8333, them=108.45.xx.xx:8333, peer=108.45.xx.xx:35789
2014-07-04 11:54:48 disconnecting node 108.45.xx.xx:35789
2014-07-04 11:58:06 accepted connection 108.45.xx.xx:36811
2014-07-04 11:58:06 send version message: version 70002, blocks=309158, us=5.9.xx.xx:8333, them=108.45.xx.xx:36811, peer=108.45.xx.xx:36811
2014-07-04 11:58:06 receive version message: /Satoshi:0.9.99/: version 70002, blocks=309158, us=5.9.xx.xx:8333, them=108.45.xx.xx:8333, peer=108.45.xx.xx:36811
2014-07-04 12:09:50 disconnecting node 108.45.xx.xx:36811
2014-07-04 12:13:30 accepted connection 108.45.xx.xx:39735
2014-07-04 12:13:30 send version message: version 70002, blocks=309161, us=5.9.xx.xx:8333, them=108.45.xx.xx:39735, peer=108.45.xx.xx:39735
2014-07-04 12:13:30 receive version message: /Satoshi:0.9.99/: version 70002, blocks=309160, us=5.9.xx.xx:8333, them=108.45.xx.xx:8333, peer=108.45.xx.xx:39735
2014-07-05 06:45:38 disconnecting node 108.45.xx.xx:39735
2014-07-05 08:50:34 accepted connection 108.45.xx.xx:47068
2014-07-05 08:50:34 send version message: version 70002, blocks=309304, us=5.9.xx.xx:8333, them=108.45.xx.xx:47068, peer=108.45.xx.xx:47068
2014-07-05 08:50:34 receive version message: /Satoshi:0.9.99/: version 70002, blocks=0, us=5.9.xx.xx:8333, them=108.45.xx.xx:8333, peer=108.45.xx.xx:47068
2014-07-06 02:10:39 accepted connection 108.45.xx.xx:38163
2014-07-06 02:10:39 send version message: version 70002, blocks=309414, us=5.9.xx.xx:8333, them=108.45.xx.xx:38163, peer=108.45.xx.xx:38163
2014-07-06 02:10:39 receive version message: /Satoshi:0.9.99/: version 70002, blocks=-1, us=5.9.xx.xx:8333, them=108.45.xx.xx:8333, peer=108.45.xx.xx:38163
2014-07-06 02:18:39 disconnecting node 108.45.xx.xx:38163
2014-07-06 06:09:32 accepted connection 108.45.xx.xx:56273
2014-07-06 06:09:32 send version message: version 70002, blocks=309440, us=5.9.xx.xx:8333, them=108.45.xx.xx:56273, peer=108.45.xx.xx:56273
2014-07-06 06:09:32 receive version message: /Satoshi:0.9.99/: version 70002, blocks=672, us=5.9.xx.xx:8333, them=108.45.xx.xx:8333, peer=108.45.xx.xx:56273
2014-07-09 07:29:05 accepted connection 108.45.xx.xx:36528
2014-07-09 07:29:05 send version message: version 70002, blocks=309898, us=5.9.xx.xx:8333, them=108.45.xx.xx:36528, peer=108.45.xx.xx:36528
2014-07-09 07:29:05 receive version message: /Satoshi:0.9.99/: version 70002, blocks=0, us=5.9.xx.xx:8333, them=108.45.xx.xx:8333, peer=108.45.xx.xx:36528
2014-07-09 07:32:28 disconnecting node 108.45.xx.xx:36528
2014-07-09 08:14:13 accepted connection 108.45.xx.xx:38402
2014-07-09 08:14:13 send version message: version 70002, blocks=309903, us=5.9.xx.xx:8333, them=108.45.xx.xx:38402, peer=108.45.xx.xx:38402
2014-07-09 08:14:13 receive version message: /Satoshi:0.9.99/: version 70002, blocks=10, us=5.9.xx.xx:8333, them=108.45.xx.xx:8333, peer=108.45.xx.xx:38402
2014-07-09 08:26:02 disconnecting node 108.45.xx.xx:38402
2014-07-09 08:27:28 accepted connection 108.45.xx.xx:40442
2014-07-09 08:27:28 send version message: version 70002, blocks=309905, us=5.9.xx.xx:8333, them=108.45.xx.xx:40442, peer=108.45.xx.xx:40442
2014-07-09 08:27:28 receive version message: /Satoshi:0.9.99/: version 70002, blocks=488, us=5.9.xx.xx:8333, them=108.45.xx.xx:8333, peer=108.45.xx.xx:40442
2014-07-09 09:09:11 disconnecting node 108.45.xx.xx:40442
2014-07-09 09:10:51 accepted connection 108.45.xx.xx:41815
2014-07-09 09:10:51 send version message: version 70002, blocks=309907, us=5.9.xx.xx:8333, them=108.45.xx.xx:41815, peer=108.45.xx.xx:41815
2014-07-09 09:10:51 receive version message: /Satoshi:0.9.99/: version 70002, blocks=407, us=5.9.xx.xx:8333, them=108.45.xx.xx:8333, peer=108.45.xx.xx:41815
I was offline for about 10 hrs yesterday until I reverted also. It'd crash every once in a while and then you'd have to reindex. |
|
|
|
|
I had to sell my bitcoin as I mined to buy more mining hardware.
Didn't have the luxury of having extra money I could just throw at it, outside of my initial purchase of three 5830's (for four total, already had one from months prior).
... though I suppose I would have made a lot more money just mining with those four 5830's and never expanding, but that's just how it was w/ Bitcoin... pretty crap mentality for most things.
|
|
|
|
A good calculator for mining: https://bitcoinwisdom.com/bitcoin/calculatorPlay with these inputs and you'll realize that it's almost impossible ever to break even. I managed to make a profit of 0.65 BTC only by using some very strong assumptions: Price = 0.75 BTC (I.e. no VAT/customs, free PSU) Electricity only $0.10/kWh Only 10% difficulty increment It implies that no EU resident will ever be able to make a profit. If you live in some parts of the US, you might profit marginally, but not worthwhile given the risk of hardware failure. May someone explain their rationale for investing in Antminer S3? Maybe something I missed? Nope...you pretty much hit the nail on the head. Even here in the states the likelihood of recovering your initial investment in hardware is slim to none. Plus, your also assuming 100% uptime. Rig's quit unexpectedly for a variety of reasons: 1.) Hardware issue(s) (failed fans, etc.) 2.) Internet connection lost 3.) Pool(s) going down (this can be largely mitigated by having secondary and tertiary pools but you still lose some hash power switching pools) All and all mining isn't even a 0 sum game at this point. It's a guaranteed loss! If you keep them and mine with them, yes. I don't know if it's still true or not, but people used to offer above the already bloated retail value to buy ASICs "in hand". and most people talking about mining with their ASICs aren't people that have been on this board for more than a year or two |
|
|
|
|
ASIC companies wouldn't sell their ASICs if it was more profitable for them to mine with them, lol.
The sole exceptions being the very first startups that needed funding to begin R&D and manufacturing of ASICs (i.e. Avalon batch 1, somewhat for batch 2, then batch 3 was nonsense, like all the rest)
|
|
|
|
but with the rental I have aimed there it seemed though I got a lot more consistant little payments but in the calculation over the 24hrs it still lost BTC compared to the cost of rental.
Am I missing something here? - What is the point of renting a rig if it is only going to cost you BTC in the long run?
Common sense dictates the following: If somebody has hash rate and is willing to lease it to you, why would they charge you less than what it could mine for themselves? Outside of the pool you point it at being lucky during your rental period, you will always lose money renting hash power. Otherwise nobody would ever let you rent the hash power at that price in the first place. Aha! This is true only for the type of leasing that cex does (no contract). If you leased based off of, say, an annual contract, then you should expect to pay less than what this mining hardware you're leasing will eventually put out in a year. Why? Other guy is basically getting insurance for that year +. Two huge benefits off the top of my head; protects them against bitcoin price drop, allows them to reinvest straight away -- in better hardware, in bitcoins (smart move if they believe the price will continue going up... assuredly beating whatever meager profits you'd realize after a year).... or maybe they'd just take it to Morgan Stanley. ... that being said, all the yearly + contracts I've seen on this board are insanely overpriced + they require you to take that leap and have a large amount of trust in some "company" that nobody has ever heard of before. |
|
|
|
Uh, wasn't sure what forum this belongs in, but figured some people would want to know about this at least. Hetzner's prices were good before, but they're incredibly low with the 0€ setup fee. http://www.hetzner.de/en/hosting/produktmatrix/rootserverRemember that all the prices on there include VAT. So the EX40 is ~41.15€ if you aren't subjected to a VAT charge. Nothing can even compete with that right now as long as that setup fee is removed (it even makes their robot auction prices obsolete). |
|
|
|
|
Show Posts
