I vote for "1.0" and not "1.3" or something, bleh! (I also advice we use a major, minor and patch level version number, "0.0.00".) I've used bitcoin-1.3.0.rc3-linux [1] and found it to be mature enough to be called "1.0" in my opinion. (It was already called 1.3 there, but I guess we cal all agree it's the next release, thus right now can be called both 1.3 and 0.3.) [1] http://www.bitcoin.org/download/bitcoin-1.3.0.rc3-linux.tar.gz |
|
|
|
|
It's a relief to hear this.
And what were you exactly testing?
Like, how can it affect the whole network?
If this is a bug that can bring down the whole network, it's pretty serious, heh.
|
|
|
|
At 21:11 dutch time (CEST), around 10 minutes ago from when I made this post, the Bitcoin clients are getting k-lined. (note, times are CEST.) --- SNIP ---
[21:11:36] * u4euc453wZ599zQ has quit (K-Lined)
[21:11:37] * u4mZRTtQwC6NskZ has quit (K-Lined)
[21:11:37] * x398030675 has quit (K-Lined)
[21:11:37] * u4m5AmvGVaM8MNU has quit (K-Lined)
[21:11:37] * x92119461 has quit (K-Lined)
[21:11:38] * u4iQ9mpGopGTd6D has quit (K-Lined)
[21:11:39] * u4iqow5D1WqBmPH has quit (K-Lined)
[21:11:39] * u4qsjyU6VRAtfRD has quit (K-Lined)
--- SNIP ---
Anyhow, this leaves the bitcoin network unable to operate. I see some clients getting back slowly. But this worries me. I suggest we apply what ever other bootstrapping mechanism we have right now, and release 0.3 ASAP. Someone in #freenode suggested this: <gwillen> Xunie: as a potential user of bitcoin, I would suggest that if your project is going to connect to IRC in the background, you should document that fact somewhere. I'm suddenly much more wary of using it now that I know that it does this. This does make Bitcoin seem a bit... malicious to say the least... |
|
|
|
|
Lol, bitnickel!
Anyhow, I was expecting this.
And what about those using proxies?
I don't wanna be an #@!%!#% here, but ehh... I think the "5 BTC for FREE!" thing, is kinda... flawed...
|
|
|
|
Yay, Vasiliev won!  I will setup a website, and some other place to get my random numbers from. Thanks to everyone for participating! |
|
|
|
|
Well, obviously no one won.
So eh, we'll wait until someone finally does!
|
|
|
|
|
Whoohoo! Can't wait!
Note, is there somewhere I can get a devel build?
Maybe we can setup nightly builds or something...
|
|
|
|
In case the weakening of SHA-256 is gradual instead of sudden (much more likely, IMO), BitCoin could stretch the process of switching to a different hash algorithm over a long time. First accept SHA-512 (or whatever) in addition to SHA-256, then use SHA-512 by default, and finally stop accepting SHA-256 for new blocks.
Wouldn't the users lose their coins? |
|
|
|
I don't see any problems here, running 10.04 myself now!  |
|
|
|
How about Sundays, around 19-21 GMT time?
Great time for me too. And I strongly support this. Although we'd need to have something to discuss. Thus sorta gather some information over the week everyone wants to discuss... Who are the developers anyways?  |
|
|
|
|
Okay, so what about Bitcoin?
What about our safety?
|
|
|
|
So far, I got these lot numbers taken by these owners! I find this increasing fast though!  00 Vasiliev 15 bencoder 34 solar- 53 solar- 55 Vasiliev 77 Lachesis 81 Lachesis 90 Vasiliev 93 solar- 96 Lachesis That makes the current jackpot 500 BTC! |
|
|
|
Okay, this is what's going to happen. Everyone who wants to buy one or more Bitcoin lottery ticket(s), you post in this thread what number(s) you're buying, send me and I'll contact you how to pay. Please note that I really want you to post in this thread what lot number(s) you're buying because other people will know what lot numbers are taken. (And I do not like getting accused of scamming!  ) If two people "buy" the same lot number, the person who posted first in this thread, gets that lot. A maximum of 3 lots per player, no exceptions. The lot price is 50 BTC. The lottery will be drawn in 7 days on June 21. The winning numbers are the last 2 numbers (middle and right) on this page, http://www.lottery.ok.gov/pick3.asp. If no one wins, the next day's numbers are used, and we'll keep doing that until there's a winner. (No need to buy lots a second time, you'll keep playing.) So when no one wins, it's only a matter of time before someone does. And finally, everyone's money will be going into the jackpot in full, so there's no profit in it for me. (I ain't ripping Bitcoin off here! ) (And I wont be playing myself.) Let the 'game' begin, hehe. PS: A website's coming! |
|
|
|
Please note that revision 77 is buildable (by default) and 78 isn't I believe. And can you next time wait for your answer in IRC? I mean, you asked your question twice, we're just not in the room 24/7!  |
|
|
|
Hey Satoshi, if I translate to tlhIngan Hol (Klingon), will you add it to the SVN? |
|
|
|
I've been doing some quick research, Oklahoma Lottery's "Pick 3" game is perfect. It requires the player to select 3 numbers between 0 through 9. (We'll only use the last 2 numbers ofcourse.) It's drawn daily. You can easily check the drawing's results here: http://www.lottery.ok.gov/pick3.asp. |
|
|
|
|
I've been thinking and I'll be hosting world's first Bitcoin lottery!
We'll be using the last two numbers of a real lottery, which one I do not know yet. (Maybe one that we can check online?)
When you'll buy your lot, you'll "bet" on a number between 00-99. (including 00 and 99 ofcourse!)
So, who's in for it?
What real lottery should we pick for our random numbers, or does anyone have a better source?
What price of the "lot" sounds preferable? 50 BTC? 25 BTC?
And what's the maximum amount of lots I want to let people buy? 3? 5 at most?
Please note that if the "jackpot" doesn't "fall" (no one wins), I'll keep hosting rounds until there does win someone, and I wont play myself.
So I want like a lottery that draws numbers every week if we can't get one that draws every day.
|
|
|
|
|
Or it should just look the hostname up before it dismisses it as an invalid address.
This has probably just slipped the mind of the developer.
|
|
|
|
It's like logging into your bank's website without HTTPS.
I agree, this is a pretty large security hole. We need a bug tracker for this stuff. |
|
|
|
Here is the almost complete (93%) translation into Dutch. It might contain some errors though. I can has credit now? |
|
|
|
|
Show Posts
