|
As far as I know, the client will keep track of it properly, you just won't be able to spend it because the lowest the GUI allows is 0.01 so far.
|
|
|
|
Yeah, works well. I'll let it run on a few servers for a while to see how stable it is. At this rate, we'll all double the difficult again just because we keep getting clients that double up over and over on the khash/s  These builds now out-pace my linux machines on similar hardware, very impressive! |
|
|
|
so you weren't the guy who sent me 0.02 I take it? LOL, no I was the one who sent about 3,080 times that much |
|
|
|
|
Yeah, a block is being solved every 10 minutes or less, it shouldn't take 2 hours unless the client has somehow lost connection to the rest of the network.
|
|
|
|
Wondering if anyone else gets this? I have a P4 machine... sometimes I generate blocks with it. Other times it's shut off.
When I it on, load bitcoin, there may be 500-1000 blocks that it needs to download. This issue has happened since version 2.0 and still happens with 3.3
I start getting connections. Maxes out at 8, and I don't start downloading blocks anywhere from one minute to 30 minutes. Once it starts downloading, it usually gets them all. But sometimes it sticks at some point in the middle. Stops for 2 to 10 minutes before downloading the rest of them.
I noticed this on another computer when it shut down accidentally. Turned it back on, and it took a solid 15 minutes after getting 8 connections to start downloading blocks. No windows defender or anything going on.
Has anyone else seen this?
The longest I've seen on a windows client was under a 1 minute to start updating blocks. The latest client downloads about 500 at a time before verifying and moving on to the next 500 batch. I have to agree, 15 minutes of waiting does seem a bit excessive, especially since 8 connections is just the max, not usually the requirement for it to work. It's possible the clients it was connected to were slow or were having issues and you had to wait until your computer moved to other clients that weren't so slow. |
|
|
|
|
It's tough to make a sliding scale where one range doesn't overlap another unless you make a huge chart, so for the math to make more sense I changed the numbers around a little at the end.
|
|
|
|
Now i know why my last lot of bitcoin sales went through so fast!  Yeah, I noticed a lot of those sales were going to the same e-mail address over and over  |
|
|
|
|
I'll be glad to offer up services. Contact me by e-mail or message system here.
==== Range ======== Fee
1 BTC - 10.99 BTC ;; 0.25 BTC
11 BTC - 50.99 BTC ;; 0.50 BTC
51 BTC - 100.99 BTC ;; 1.00 BTC
101 BTC - 500.99 BTC ;; 2.00 BTC
501 BTC - 1000.99 BTC ;; 4.00 BTC
1001 BTC - 3200 BTC ;; 8.00 BTC
3200+ BTC ;; 0.5% of amount (half of 1%)
|
|
|
|
That's very fascinating insight, knightmb. Some incredible machines on-tap. I have been doing a lot of btc-per-energy calculations, but outright renting cores for off-peak khash is taking it to the next level. At the current difficulty level, I've stopped all coin generation on machines where I pay for power or cooling. Even the highest-end i7 machines had enough of a delta between idle/light-load and full steam that it was not worth the marginal cost. Not by a longshot. Recovering bulk coins from the dusty wallets of early adopters is very clever.  Same for me, I had a set budget by the investors and doing another month of servers at the current difficulty just isn't economical anymore when I can buy it from the market/members here for much less now. On top of that, the amount gathered should be more than enough to start with. If things take off, then it just means everyone's BTC will be worth more since I'll have to raid all the market sites again. |
|
|
|
|
It would certainly be hard by both luck and CPU/storage power to do this.
If you found a collision and a private key, that would do you no good since you would have to peg an account out of the
541,638,008,296,341,754,635,824,011,376,225,346,986,572,413,939,634,062,667,808,768 possible combinations of people using accounts.
So look at it two-fold. I find a collision in the hash and I find the private key. Now I have to hope my odds are that someone else is using that hash. Since there are more possible hash account numbers than every person every born on this planet and was each using a million addresses, the attack by it's own nature, while interesting, just isn't really feasible on a large scale.
|
|
|
|
Also, in my experience, one can switch from one build to another and use the same wallet etc.
Same experience for me, plus I've generated coin with these builds, never had any trouble transferring it around or spending it, so the experimental builds are following the Bit Coin protocol properly like the rest of the *release* clients out there. |
|
|
|
That is pretty awe inspiring! You didn't assemble all those machines for this project did you?
Were some of them cloud machines (like amazon ecc?)
I'm hoping you'll give some details on your project soon. I've got some anonymous banking ideas if you want to share.
Machines from about a dozen different hosting companies around the US here. Basically, each machine rented for between $19 to 50 a month, so this is the last month for their rental and the next month we won't be renewing the rental. I did try some Amazon cloud machines, but they ended up being nearly the same speed as the other servers we were renting for the price. I could rent a Amazon instance for about a $1 / hour to churn 10,000 khash/s but then I could rent a server from another hosting company for an entire month for $19.99 and it could churn close to 7,000 khash/s so using Amazon didn't make economical sense; an entire day of hashing was the same price as an entire month of hashing at another hosting service. There were some special machines that were rented from some hosting centers in GA that had a lot of cores and mainly we used idle time (since it was cheaper, it would really burn up the khash at night when the server load was nearly non-existent) And then course, just go out and buy the Bit Coin through the market place and members here (thanks to everyone willing to part with their BTC for USD) Overall, the server farms only churned out about 1/3 of the total, the other 2/3 was bought over the last few months from members and the market websites. Some members here even gave me a large chunk at no cost simply because they were early adopters and didn't know what else to do with large amounts they had generated early on. So it paid off for me to try and contact all the early adopters of Bit Coin. |
|
|
|
It is well known that one person has 10% of all existing coins. Most are being "hoarded" because he is developing a new venture that requires the coins as collateral. If his venture were to fail before it started and he were to "burn" his wallet with 10% of all existing bitcoins. NOBODY WOULD NOTICE! Nobody knew he had the coins until he told us. If he had never told us, the math is no different.
If he decided to sell them all at once the market would notice. But nothing happens if someone takes NO action.
A side point, it's now a lot more economical to buy them off the market/members than it is to generate them. So as this month ends, all the server time that was being used will be slowly fazed out (as it has been for 1 week now) and the difficulty still continues to remain high so interest in Bit Coin continues to remain high around the world from what I'm seeing. In case anyone was curious, the servers were made up of about -330- 64bit ( 8 )-core Xeon processor systems that all ranged from Linux to Windows along with another 20 special systems that ranged from 8 to 64 core systems running various flavors and windows and Linux. After the end of this month, it will just fall back to a half dozen 8-core servers to keep the daemons running for testing and keeping the BitCoin network going of course A month of running all of those servers 24/7 produced a lot of coin of course, but it's been a better process just to purchase it (and faster, less maintenance) and now with the difficulty much higher than it was last month, it's more economical just to buy it from the market sites. So unless the difficulty falls back down below single digits, I'll be glad to not have to worry about monitoring that many servers in the future. |
|
|
|
I guess I never expected people to stake their life's saving or even a day's wages on the thing at its current stage of development. It still doesn't make sense to me to do anything of the sort. Obviously some people see it differently. I will try not to repeat my mistake.
The same could be said about any currency or object, but to come to the forum to ask for advice, expect to get plenty of advice. The test network is there to test and if anything it would be the best place to start. You would want to move up to more production testing later on once you are certain that the test is doing what you want it to do and NOT what you want it to do. You can't test for something looking for a certain result and end up getting 20 other results that you didn't expect and have no idea why they are being produced until each was examined later on. You could always build you own network with the -connect=xxx.xxx.xxx.xxx option to make a private network of actual release version BitCoin clients and try to blow it up that way. |
|
|
|
Haven't found much on the topic there, so asking away.
Let's say i have a practicable quantum computer or other device capable of rapid factorization of large enough integers.
What are the consequences to a developed bitcoin network?
Any way it could let me cheat in generation?
Any way it would let me cheat in transactions?
With a device of this kind i can get the private key from public key, right?
So after receiving a bitcoin from someone, can i subsequently successfully fake a transfer of all there was on his side?
I would say no to all questions because quantum computing is not like a magic converter. If you have a working quantum computer, you won't be able to feed in BitCoin hashes and spit out Private Keys. I think it would fall under the hashing collision topics here more than trying to factor large integers. While the media makes quantum computers seem like they will operate like a 1 Trillion MHz processor, they actually operate in a specialized way that is kind of hard to explain in terms of computer science. |
|
|
|
|
As far as I can tell, nothing else has been done. Seems to only work on a few select Mac at the moment and even then appears to be a little unstable.
|
|
|
|
if the unofficial bitcoin crashes, does it lose any progress it has made and have to restart from the beginning of whatever it was working on? yes, i'm a bit of a thickie, still not quite sure of the internal workings  You won't lose your balance, but it will have to start over. It already starts over each time a new block is found, so at most you'll lose a few minutes spent on the previous block. |
|
|
|
|
All possible coin should have been sent.
On a note, NoAgendaMarket, I sent yours to the address you had in your signature since there wasn't any address in your ticket entry.
If anyone thinks I missed sending you the split of the winnings, just let me know.
|
|
|
|
|
Winning Number was 217 and well, someone missed it by one number, but that's ok, because it just means everyone won! There were 189 tickets, so the jackpot was 339 BTC divided by all 189 tickets giving each ticket 1.79365079 BTC or for rounding purposes, it will be 1.79 BTC and the remainder after everyone gets their share will be given back to the Bit Faucet site.
I'll start sending back Coin right now, so everyone should expect it to arrive shortly. I'm doing the entries as they came in, so don't be surprised if you get several payments for all the times you entered.
|
|
|
|
I'll attend if my schedule works out, would be interesting to see what topics are chat about. |
|
|
|
|
Show Posts
