|
When you think about the number of possible hashes and hash collision; it only becomes a problem if the collision you find (if by accident or on purpose) actually matches someones account. If everyone person on the planet had a BitCoin address, your odds that a collision is going to be someone's account is still so small as to make the use of it impractical.
When you can target a specific BitCoin address with the collision, then it becomes a problem. Otherwise, you're likely to end up with an account that has only 1BTC in it or no account at all.
|
|
|
|
ran great for me the first 18hrs then crashed, has been crashing since every once in a while. I am using the script posted to keep it up and running. I have not generated any coins either but, the difficulty per block has jump again recently.
the script works fine. only one problem, when bc crashes, windows puts up a box asking do i want to close the program and search for a solution online, or just close the program. is there any way of bypassing this? because the script comes to a halt while this box is waiting for input from me. I've never seen that on mine, it blows up silently. I think it's because I have the "error reporting service" disabled so that the box never comes on my servers. |
|
|
|
OK, thanks. I'd also like to know if it runs fine as long as you don't turn on Generate. You'd think as long as it doesn't actually execute any SSE2 instructions, it would still load. At least Pentium 3's could run it without generating.
I thought the SSE2 mode would just be for those those with processors that support it, so far the release client runs just fine on older PI, PII, PIII machines, just very slow on the khash/s part. For example, a PIII 933MHz Linux machine can muster about 125 khash/s, some old 1.1GHz Celerons I have can reach 172 khash/s I wouldn't want to exclude those that have older processors from at least trying to generate coin, hehe. |
|
|
|
...
I guess it's using SSE2. It automatically sets its build configuration at compile time based on the compiler environment.
It looks like it has some SSE2 detection at runtime, but it's hard to tell if it actually uses it to fall back if it's not available. I do want the release builds to have SSE2. SSE2 has been around since the first Pentium 4. A Pentium 3 or older would be so slow, you'd be wasting your electricity trying to generate on it anyway.
I've got some older machines (for the windows client and linux clients) to test with that don't support SSE2. Mainly if you try to run them, the program just crashes when I tried some of the experimental builds here, but I'll be glad to test some future official builds to see if the "detect SSE2" part works or the program goes belly up. |
|
|
|
I just love the "Pitock Hubbub". Thanks all for you support and the market projections.
Could you explain this for the unenlightened? William Pitock, aka Nenolod, is self-proclaimed as the sole party responsible for the "attack" on bitcoin proof-of-work increases that "shoot up from 45.0 to 181.5" in the middle of the month of July: http://nenolod.net/thoughts-on-bitcoin/The difficulty never went down after his *attack* was done, so I have just as much evidence that I'm the one who raised the difficulty rate as he did. My opinion is that the influx of new users is what raised the difficulty and he was just using that as a cover to get himself attention in some way. You'll find a more detailed opinion on this page https://www.bitcoin.org/smf/index.php?topic=431.60 near the bottom, look for my long post. |
|
|
|
|
The noon deadline has passed, I'm certain we will have a winner today! (You or everyone, hehe)
|
|
|
|
I've run into perhaps a client issue, I'm not sure. When someone sends a payment from BitCoin address to BitCoin address, you'll always have a return address if you need to refund for example. When someone sends a payment by IP address, if they leave the from field blank, BitCoin fills in the BitCoin address, but if they fill in anything else well you have no idea where the payment came from. Case in point, while running a small lotto in the Marketplace forum area, I had someone send some Coin and ticket picks, but they forgot to include the return address and had some other comments written in the "from" field. So I'm not sure how to find how what address it came from. I've tried digging through the log files, but didn't find anything relevant. If you send payment direct from IP to IP, the BitCoin address is recorded somewhere right? If not, then a feature request would be way to find out (maybe when you double-click the transaction, it brings up a summary screen, maybe include that in the summary screen) Feedback welcome or if someone knows where this info is and I'm not finding it.  |
|
|
|
I've updated the jackpot and picked numbers. Just 3 more hours until ticket entry closes. I have a good feeling someone is *bound* to win this now!! On a side note, someone recently bought a lot tickets and didn't leave an address of where to send all the winnings (should they win), so if you are that person message me.  |
|
|
|
It's a good thing all those phantom super-clusters went off line a few weeks ago or who knows how high the difficulty would have jumped to? |
|
|
|
Or those with servers stuck on 32-bit OSes. :-D Quad core Xeon@1.6GHzStock: 1100kh/s Full Opt: 2600kh/s THANKS! BitCoins are always appreciated, address in my sig I just sent you a wad of coin  |
|
|
|
|
So the very first 50BTC is what you are after, what if that person had other BitCoins generated into it since then, how do you know which is which?
|
|
|
|
Wouldn't that be a good reason to dump a lot of coins in real quick?
Well if you dump in alot, that's more division, right now I think there are 87 tickets. Each person would get back 2.7 BTC, but if you dump in say another 100 tickets, that would be barely 1.2BTC each, so one could spend 100BTC and make 120 BTC if no one wins. There's the risk that if you dump in a lot, someone will win the whole jackpot and you'll lose everything you put in. So if someone wants to risk it, that's up to them. |
|
|
|
|
Since things are really picking up with my other projects, I won't have time to run another lotto, so here's the fun part.
If no one wins the jackpot tomorrow, then *everyone* wins. I'll take the jackpot and split it up among every single ticket that was bought. Currently that means everyone that spent 1 BTC for a ticket, will end up getting about 2.7(give or take haven't done the exact math yet) BTC back as a winner per ticket.
So if you bought 1 ticket or 20 tickets, you'll get back a portion the full jackpot for each ticket. So one person wins big or everyone wins small tomorrow!
The best of luck to you all!
|
|
|
|
My guess is that this is fine if you trust the source or don't mind defaulting. If it's in a block 1/unconfirmed it's 'mine' so it's good to go right? What about 0/unconfirmed, can I still send without problems?
Yes, you send around 0/unconfirmed coins forever from what I've found out in my testing. The only issue is, should those be fake, everyone that the fake coin was sent will have their balance adjusted to subtract the fake coin. If it's someone you trust (best friend, family, good business partner) then yeah, spend it. If it's someone you've never done business with, I would wait before spending just in case. |
|
|
|
Here's me showing my age  I created a batch file and put it in the same folder at BitCoin.exe Just create a file, like bitcoin.bat Edit the file and paste in echo off
:10
echo Starting BitCoin Crazy Unstable But Oh So Fast!
start /wait bitcoin.exe
date /t
time /t
ping -n 1 -w 5000 1.1.1.1
goto 10
Save the file and use it to start BitCoin. If the program crashes, it will log to console when and restart the client. This only works in the Windows Client GUI, won't work for services. I figured I would add this if it's helpful to anyone. |
|
|
|
|
Yeah, I easily see 10,000 khash/s on some of my lower end 8 core servers. This should give just about anyone a major speed boost.
|
|
|
|
They do physically, but if you use a virtual machine, you can set environments to have 3 for example. Windows will work with 3 cores or 4 cores just fine, it doesn't care how many it has.
VMware only permits even numbers of processors/cores although I believe you can expose 8 cores and then configure the OS to only see 7. if he really does have this setup, I'm going to bet that he's opted for more processors/cores than his CPU actually has (yep, you can do this but it will have a pretty negative effect on performance) I was thinking about Virtual Box when I wrote that |
|
|
|
|
They do physically, but if you use a virtual machine, you can set environments to have 3 for example. Windows will work with 3 cores or 4 cores just fine, it doesn't care how many it has.
|
|
|
|
I hit 2700, up from 1250 stock.
I have 7 cores, how do I tell how many it's using? Can I control it?
Task Manager and Yes, options in Bit Coin allows you to control how many cores it's using. |
|
|
|
|
Show Posts
