503 and I'm in.
wobber leaads at 503 BTC |
|
|
|
|
Well, after some thinking, I think it's finally not a good idea indeed.
First, indeed there is no incentive to seed torrents. Therefore, you can not be sure all blocks will be available unless you store them on yur own node.
Second, bitcoin requires quick communication between nodes, for transactions. Therefore it needs its own communication network anyway. So using it to exchange blocks is a small payload.
Anyway, I now kind of trust Satoshi to have come up with a pretty good network structure. I doubt we could do much better.
|
|
|
|
Well that happens now doesnt it? Files could be hosted on tahoe and the tracker just knows the location.
I don't know. Maybe. Anyway, what we really need is a distributed database, imo. |
|
|
|
What if you created a block chain composed of torrent files ?There would be no need to have a central website all you would need is a client that searches the block chain for you and finds the torrent you want. How would the transaction side of it work ? The file hosting could be left for tahoe lafs or something . No torrent search site to send take down notices too.  +1 ! I've already smitted this idea on the "python client" thread. http://bitcointalk.org/index.php?topic=231.msg28952#msg28952I also whish those files would be in ASCII, so that we implement the bitcoin client in a scripting language. One question is : is it possible to share several hundreds of thousands of files in P2P ? We could consider using the GNUnet framework, because I think it can be used with a datastore, instead of files. |
|
|
|
An interesting article (via Slashdot) came up that I think is of interest to the Bitcoin community:
I think it's important to be ready for a change in the sha function when it's necessary. It might require a change of both the software and the block chain, I guess. However, there is no reason to jump into it until SHA256 is cracked. I also hope it will not lead to any weirdness/incoherence in the code or in the blockchain. What I'd like to see is a fork of bitcoin with this new hash function, so that people/market can decide which is better. |
|
|
|
It's all in the title of the article.
Many people only read the title of the article.
The article clearly linked Wikileaks to Bitcoin.
I think the title was fine. It any case, it wasn't "lazy journalism". The journalist asked if the "wikileaks scandal could lead to a new currency". This is a legitimate question, for the seizure of wikileaks's accounts revealed the NEED of a decentralised currency. To put it simply, this affair is not linked to the creation of bitcoin, but to its upcoming notoriety. |
|
|
|
Si vous cherchiez en *europe* et pas en France ?  En France vu les régulations en vigueur, c'est clairement mort :p En Belgique peut-être ? Un belge de ce forum peut-il se renseigner ? Je me rend parfois à Bruxelles donc je pourrais en profiter pour acheter des cartes si nécessaire. |
|
|
|
The genesis block part was clear, but note that you have to guess the exact same information. Your guess is also still completely vague. In a computer program there is only one answer and in a good program one should not need guessing.
I don't see why I should even point out any other issue if this is clearly a valid objection.
Well, I guess you're right : at least ther should be a comment. But anyway we know Satoshi's code is poorly commented. It is just an example amonst many others. |
|
|
|
Very specifically line 24 in my SVN chechout contains the following number, but there is no explanation as to why this number is there; I can guess why it is there, but it shouldn't be my task to figure out why something is there. A comment above this constant should say why exactly it is that value and not some other value, why it is important for the system, etc. uint256 hashGenesisBlock("0x000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f");
Lol As the name of the variable indicates it, it's the genesis block. I guess it's the public key of the first ever bitcoins. This is certainly not the best critic of Satoshi's code you can make. |
|
|
|
I'd like to hear some specific criticisms of the code. To me it looks like an impressive job, although I'd wish for more comments. Now I've mostly studied the init, main, script and a bit of net modules. This is some powerful machinery.
I agree. Actually I'm amazed this is the product of only one person's work. |
|
|
|
It was published right before the forum went down for a few hours haha.
Was it ? It's certainly correlated, then. The amount of new visitors blew up the bitcoin website. Thanks for pointing it out. |
|
|
|
(S3502 + 1 )
Please confirm your bid at 502 BTC |
|
|
|
501
S3052 leads at 501 BTC |
|
|
|
500
davout leads at 500 BTC |
|
|
|
Could you tell us, from which country are you sending this coin and do you know the weight of the coin in gramms ?
From France. All informations about the coin can be found on the web. The swiss 20 CHF gold coin is quite famous. It has the same gold value and purity as the french napoleon. |
|
|
|
210
S3052 leads at 210 BTC |
|
|
|
Let me start with 100 BTC
MagicalTux initiates the auction and leads at 100 BTC. |
|
|
|
After a few successful sellings of 1g mini gold bars, I now start the first ever gold coin auction on this forum. So, this is a standard 20 CHF (swiss franc) gold coin. See internet for details about this coin. No starting price. Price will include postal fees to wherever in the world. It will be a standard letter. I will just hide carefully the coin into the letter. It should be fine. Auction will end at block number 100,000. At this time, I will lock this thread and thus close the auction. I might close it a bit earlier and end the auction on IRC, though. DO NOT BID IF YOU DON'T REALLY INTEND TO BUY THE COIN. I will require paiement before sending it anyway, so there is no point making fake bids. Do not PM to make your bid. Just post it in this thread. Have fun !   |
|
|
|
I am convinced that the foundation of bitcoin (ie. the block chain) is secure from any non-nationally funded attack. The only attack that makes me scared is a buffer overflow attack that steals the private keys in the wallet, however doesn't spend them.
If a significantly large attack happens to the block chain, we can always make a new branch that doesn't include the attack; with the theft of private keys, there is no easy recovery option, save (in the case of a massive attack), starting the block chain from 0 again.
As I'm not a security expert, I do not know how secure bitcoin is against this sort of attack. However from my non-expert understanding direct to IP address transfers seems like a obvious surface area to attack.
Two questions: what attack areas dose the current bitcoin software have that could enable the theft of bitcoin private keys?
Secondly, what efforts can be taken to minimize the attack surface area of bitcoin?
I've always thought that the only known possible attacks could allow double spendin or freeze the whole network. I doubt any attack could steal private keys, apart from conventionnal attacks to the file system. But I'm not an expert at all. |
|
|
|
Hi,
I like bitcoin, but i don't like install apps using "make install" in my debian box, in the last weeks, i worked to create debian/ubuntu packages, for easy install and fast update (maybe).
Good. There is a official packaging in progress for debian : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=578157But it's progressing very slowly. Hopefully you could help. |
|
|
|
|
Show Posts
