Topic

Security and attacks

121 writings, oldest first

Private email (Adam Back)

Citation of your Hashcash paper
20 August 2008, 17:30 UTC
I'm getting ready to release a paper that references your Hashcash paper and I wanted to make sure I have the citation right. Here's what I have: [5] A. Back, "Hashcash - a denial of service counter-measure,"…
Private email (Wei Dai)

Citation of your b-money page
22 August 2008, 16:38 (time as published; timezone not given)
I was very interested to read your b-money page. I'm getting ready to release a paper that expands on your ideas into a complete working system. Adam Back (hashcash.org) noticed the similarities and pointed me to your site. I need to find…
bitcoin.org

Bitcoin: A Peer-to-Peer Electronic Cash System
31 October 2008
Bitcoin: A Peer-to-Peer Electronic Cash System Satoshi Nakamoto satoshin@gmx.com www.bitcoin.org Abstract. A purely peer-to-peer version of electronic cash would allow online payments to be sent directly from one party to another without…
Cryptography mailing list (metzdowd)

Bitcoin P2P e-cash paper
31 October 2008, 18:10 UTC
I've been working on a new electronic cash system that's fully peer-to-peer, with no trusted third party. The paper is available at: http://www.bitcoin.org/bitcoin.pdf The main properties: Double-spending is prevented with a peer-to-peer…
Cryptography mailing list (metzdowd)

Bitcoin P2P e-cash paper
3 November 2008, 16:23 UTC
Thanks for bringing up that point. I didn't really make that statement as strong as I could have. The requirement is that the good guys collectively have more CPU power than any single attacker. There would be many smaller zombie farms…
Cryptography mailing list (metzdowd)

Bitcoin P2P e-cash paper
10 November 2008, 22:18 UTC
James A. Donald wrote: When there are multiple double-spent versions of the same transaction, one and only one will become valid. The receiver of a payment must wait an hour or so before believing that it's valid. The network will resolve…
Cryptography mailing list (metzdowd)

Bitcoin P2P e-cash paper
13 November 2008, 22:56 UTC
James A. Donald wrote: The proof-of-work chain is a solution to the Byzantine Generals' Problem. I'll try to rephrase it in that context. A number of Byzantine Generals each have a computer and want to attack the King's wi-fi by brute…
Cryptography mailing list (metzdowd)

Bitcoin P2P e-cash paper
15 November 2008, 04:43 UTC
I'll try and hurry up and release the sourcecode as soon as possible to serve as a reference to help clear up all these implementation questions. Ray Dillinger (Bear) wrote: Only the buyer signs, and there's no blinding. Identities are…
Cryptography mailing list (metzdowd)

Bitcoin P2P e-cash paper
15 November 2008, 18:02 UTC
Ray Dillinger wrote: Right, it's ECC digital signatures. A new key pair is used for every transaction. It's not pseudonymous in the sense of nyms identifying people, but it is at least a little pseudonymous in that the next action on a…
Cryptography mailing list (metzdowd)

Bitcoin v0.1 released
8 January 2009, 19:27 UTC
Announcing the first release of Bitcoin, a new electronic cash system that uses a peer-to-peer network to prevent double-spending. It's completely decentralized with no server or central authority. See bitcoin.org for screenshots.…
Private email (Hal Finney)

Re: Crash in bitcoin 0.1.0
10 January 2009, 14:59 (time as published; timezone not given)
I was temporarily able to reproduce the bug and narrowed it down to the "mapAddresses.count" in the following code. It was absolutely the last piece of code to go in and mainly only got tested with the MSVC build. It's not essential and…
Private email (Hal Finney)

Re: Crash in bitcoin 0.1.0
10 January 2009, 18:55 (time as published; timezone not given)
I isolated the problem. If I spawn a thread and do mapAddresses.count, even as the very first thing in the program, it segfaults. The workaround is to needlessly call mapAddresses.count in the main thread once and it's fine from then on.…
Private email (Hal Finney)

select failed 10038 fix
11 January 2009, 21:31 (time as published; timezone not given)
I believe I've fixed the bug related to "select failed: 10038" (error WSAENOTSOCK). The select error is not a big deal, but it led the communications thread to get blocked on a socket that should have been in non-blocking mode but wasn't.…
bitcoin-list (SourceForge)

[bitcoin-list] Bitcoin v0.1.2 now available
11 January 2009, 22:32 UTC
Bitcoin v0.1.2 is now available for download. See http://www.bitcoin.org for the download link. All the problems I've been finding are in the code that automatically finds and connects to other nodes, since I wasn't able to test it in the…
Private email (Hal Finney)

Re: select failed 10038 fix
12 January 2009, 08:41 (time as published; timezone not given)
It definitely looks like 0.1.3 solved it. It was getting so there were so many zombie nodes, I was having a hard time getting a reply to any of my messages. Now, four inventory messages go out, four getdata messages come back. Did you get…
bitcoin-list (SourceForge)

[bitcoin-list] Bitcoin v0.1 Alpha release notes
12 January 2009, 20:20 UTC
Release notes for Bitcoin v0.1 Alpha Bitcoin is a new electronic cash system that uses a peer-to-peer network to prevent double-spending. It's completely decentralized with no server or central authority. You can find screenshots and the…
Private email (Dustin Trammell)

Re: Bitcoin v0.1 released
13 January 2009, 07:39 UTC
Sweet, I was looking for a group like that on Usenet at one point to see what I would use if I needed, and nothing really fit. I'm sure Google groups is a lot easier to post to. There are some scenarios where a Usenet or Google group…
Private email (Dustin Trammell)

Re: A few thoughts...
15 January 2009, 19:42 UTC
I group attacks into two classes: 1) Attacks that can only be done by someone actually in the chain of communication 2) Attacks that can be done by anyone on the Internet from anywhere Type 1 exposes you to people in your house or company…
Cryptography mailing list (metzdowd)

Bitcoin v0.1 released
25 January 2009, 15:47 UTC
Hal Finney wrote: Another factor that would mitigate spam if POW tokens have value: there would be a profit motive for people to set up massive quantities of fake e-mail accounts to harvest POW tokens from spam. They'd essentially be…
Private email (Dustin Trammell)

Re: Bitcoin v0.1 released
25 January 2009, 15:47 UTC
Hal Finney wrote: Another factor that would mitigate spam if POW tokens have value: there would be a profit motive for people to set up massive quantities of fake e-mail accounts to harvest POW tokens from spam. They'd essentially be…
bitcoin-list (SourceForge)

[bitcoin-list] Bitcoin v0.1.5 released
4 February 2009, 19:46 UTC
Version 0.1.5 is now available. It includes the fix for the problem Nicholas had, checking for disk full and changes to try to improve things that were confusing. Special thanks to Nicholas and Dustin for all their help and feedback!…
P2P Foundation forum

Bitcoin open source implementation of P2P currency
11 February 2009, 22:27 UTC
I've developed a new open source P2P e-cash system called Bitcoin. It's completely decentralized, with no central server or trusted parties, because everything is based on crypto proof instead of trust. Give it a try, or take a look at…
P2P Foundation p2p-research list

[p2p-research] Bitcoin open source implementation of P2P currency
11 February 2009, 22:37 UTC
I've developed a new open source P2P e-cash system called Bitcoin. It's completely decentralized, with no central server or trusted parties, because everything is based on crypto proof instead of trust. Give it a try, or take a look at…
P2P Foundation p2p-research list

[p2p-research] Bitcoin open source implementation of P2P currency
12 February 2009, 19:08 UTC
Martien van Steenbergen wrote: > His concept makes sure money is anonymous unless it is compromised, i.e. > the same money spent more than once. As soon as it's compromised, the > ‘counterfeiter’ is immediately…
P2P Foundation p2p-research list

[p2p-research] Bitcoin P2P e-currency v0.1 released
13 February 2009, 18:52 UTC
Announcing the release of Bitcoin, a new open source peer-to-peer electronic cash system that's completely decentralized, with no central server or trusted parties. Users hold the crypto keys to their own money and transact directly with…
Private email (Mike Hearn)

Questions about BitCoin
12 April 2009, 22:44 (time as published; timezone not given)
Hi Mike, I'm glad to answer any questions you have. If I get time, I ought to write a FAQ to supplement the paper. There is only one global chain. The existing Visa credit card network processes about 15 million Internet purchases per day…
Private email (Mike Hearn)

Questions about BitCoin
13 April 2009, 23:00 (time as published; timezone not given)
Mike Hearn wrote: My best guess - it is the length of the global chain, and the rapid advance at the start is as the software downloads and verifies the preceding blocks in the chain as being valid. Right. I'm trying to think of more…
Private email (Mike Hearn)

Questions about BitCoin
19 April 2009, 02:14 (time as published; timezone not given)
The list is: bitcoin-list@lists.sourceforge .net Subscribe/unsubscribe page: http://lists.sourceforge.net/m ailman/listinfo/bitcoin-list Archives: http://sourceforge.net/mailarc hive/forum.php?forum_name= bitcoin-list I'll always announce…
Private email (Martti Malmi)

Re: Bitcoin
3 May 2009, 22:32 UTC
mmalmi@cc.hut.fi wrote: That would be great! I added you (dmp1ce) as a dev to the sourceforge project and gave you access to edit the web space and everything. Definitely. This will be an absolutely essential feature once things get…
Private email (Martti Malmi)

Re: Bitcoin
30 September 2009, 18:12 UTC
That's great, that's a good step forward. Yes, I worked out the sourceforge login problem, it was some tricky thing on the login page that exposed a quirky bug in a browser add-in. mmalmi@cc.hut.fi wrote:
Private email (Martti Malmi)

Zetaboards forum
14 November 2009, 05:46 UTC
I created a forum on Zetaboards, InvisionFree's new site that they're migrating to. http://s1.zetaboards.com/Bitcoin/index/ I made an admin account you can use to upgrade your own account to admin: u: admin pw: B98VzUUA BTW, the admin…
Private email (Martti Malmi)

Re: linux-0.1.6-test7
18 November 2009, 04:35 UTC
Finally an easy one. I see a way that could happen on a long operation such as the initial download. The TryLock bug is unrelated to the db stuff. Fix will be in test8. I've been able to reproduce the db::open/close exception 3 times now…
Private email (Martti Malmi)

Re: Bitcoin.org
4 December 2009, 04:24 UTC
mmalmi@cc.hut.fi wrote: That's strange, I've seen Firefox 3.5 on XP anti-alias large fonts. Well anyway, your way is safer. I changed it back to text for now though so I can keep tweaking the colours. Drupal puts the tags and junk…
BitcoinTalk

Re: A few suggestions
12 December 2009, 18:17 UTC
Mac support would be nice. wxWidgets really pays off for cross platform. Please don't try PPC. PPC is big-endian and Bitcoin is little-endian, there would be endless endian bugs making it harder for me to debug the network if there's a…
BitcoinTalk

Re: A few suggestions
18 December 2009, 17:37 UTC
What you can currently do is set "Minimize to the tray" in options, then run it as "bitcoin -min" so it starts minimized. The only visible part will be a small (20x20) icon on the tray, which can be doubleclicked if you want to access the…
BitcoinTalk

Re: 64bit support
29 January 2010, 00:42 UTC
I committed a fix for 64-bit compile and some fixes to support wxWidgets 2.9.0. There was one compile error in serialize.h with min(sizeof()) that I fixed for 64-bit. The rest of the 64-bit compile errors I was getting were in wxWidgets…
Private email (Martti Malmi)

UTF-8 to ANSI hack in CAboutDialog
4 February 2010, 19:33 UTC
What was the reason for this change? #if !wxUSE\_UNICODE ... if (str.Find('Â') != wxNOT\_FOUND) str.Remove(str.Find('Â'), 1); to: if (str.Find('ï¿½') != wxNOT\_FOUND) str.Remove(str.Find('ï¿½'), 1); wxFormBuilder turns the (c) symbol into…
Private email (Martti Malmi)

Re: UTF-8 to ANSI hack in CAboutDialog
5 February 2010, 18:39 UTC
Right, I'll change it to this so it doesn't get broken again: if (str.Find('\\xC2') != wxNOT\_FOUND) str.Remove(str.Find('\\xC2'), 1); mmalmi@cc.hut.fi wrote:
BitcoinTalk

Bitcoin client and website translation
8 February 2010, 01:27 UTC
Thank you for the offer to help translate. That is probably the best way you could help. I will need to prepare the code for translation first. wxWidgets has locale support, and most strings are in generated code that is already wrapped,…
BitcoinTalk

Re: DEB Package?
13 February 2010, 01:38 UTC
I couldn't get wxWidgets 2.8.9 to compile on Karmic 64-bit either. I have been compiling the latest SVN on Karmic 64-bit with wxWidgets 2.9.0, which compiles fine on 64-bit. Read build-unix.txt and use the given ../configure parameters on…
BitcoinTalk

Re: Command Line and JSON-RPC
25 February 2010, 22:54 UTC
OK, I made a build target bitcoind that only links wxBase and does not link GTK. Version 0.2.7 on SVN. I split out the init and shutdown stuff from ui.cpp into init.cpp, so now ui.cpp is pure UI. ui.h provides inline stubs if wxUSE_GUI=0.…
BitcoinTalk

Re: Dealing with SHA-256 Collisions
14 June 2010, 20:39 UTC
SHA-256 is very strong. It's not like the incremental step from MD5 to SHA1. It can last several decades unless there's some massive breakthrough attack. If SHA-256 became completely broken, I think we could come to some agreement about…
Private email (Martti Malmi)

0.3.0 rc1 quickie download link
22 June 2010, 17:36 UTC
If bandwidth is a problem, delete my link in the "0.3 almost ready" thread. I just don't want to upload it to sourceforge for a quickie share for a day or two, possibly taking it down immediately if there's a bug. Sourceforge has a policy…
BitcoinTalk

Re: Anonymity
8 July 2010, 19:12 UTC
It's hard to imagine the Internet getting segmented airtight. It would have to be a country deliberately and totally cutting itself off from the rest of the world. Any node with access to both sides would automatically flow the block…
BitcoinTalk

Re: BTC Vulnerability? (Massive Attack against BTC system. Is it really?)
9 July 2010, 03:28 UTC
What the OP described is called "cornering the market". When someone tries to buy all the world's supply of a scarce asset, the more they buy the higher the price goes. At some point, it gets too expensive for them to buy any more. It's…
BitcoinTalk

Re: bitcoin 0.3 win64 - broken access to APPDATA if non-latin characters in username
9 July 2010, 15:37 UTC
I tested this with a non-lower-ASCII account name on XP and confirmed the bug, then tested that the new GetDefaultDataDir fixed it. This change is revision 102 of the SVN.
BitcoinTalk

Re: 0.3.1 release candidate, please test
15 July 2010, 22:10 UTC
Yes a bug. It'll have to be fixed in the next version.
BitcoinTalk

Re: Hash() function not secure
16 July 2010, 16:13 UTC
SHA256 is not like the step from 128 bit to 160 bit. To use an analogy, it's more like the step from 32-bit to 64-bit address space. We quickly ran out of address space with 16-bit computers, we ran out of address space with 32-bit…
BitcoinTalk

Re: BUG Report: Rounding glitch
17 July 2010, 16:06 UTC
It must be a rounding error when getinfo converts to floating point to return the JSON-RPC result. The only place where it uses floating point to represent money is returning a value in JSON-RPC. 1.139999999999 is longer than bitcoin can…
BitcoinTalk

Re: Bitcoin snack machine (fast transaction problem)
17 July 2010, 22:29 UTC
I believe it'll be possible for a payment processing company to provide as a service the rapid distribution of transactions with good-enough checking in something like 10 seconds or less. The network nodes only accept the first version of…
BitcoinTalk

Re: Bitcoin 0.3.2 released
18 July 2010, 18:58 UTC
The change list is basically encompassed by what's listed in the first message. Everyone should upgrade to get the important security improvements. Minimizing to tray had at least 3 different glitches and bugs on Linux, including a crash…
BitcoinTalk

JSON-RPC password
18 July 2010, 20:49 UTC
I uploaded to SVN my changes to add a password to JSON-RPC. If you're set up to build, please test it. The -server switch is replaced with -rpcpw=<password>, which is also used with bitcoind. bitcoin -rpcpw=<password> -- runs with…
BitcoinTalk

Re: JSON-RPC Multiple Invocations
24 July 2010, 00:59 UTC
Obviously it's a bug that it repeats the header. I was trying to follow the 1.0 spec: http://json-rpc.org/wiki/specification It called for multiple invocation. I think they mean it's like this, but I'm not sure: Post: {"method":…
BitcoinTalk

Re: Stealing Coins
25 July 2010, 20:48 UTC
2^80 is if you can use a birthday attack. You can't use a birthday attack for this, so the difficulty is the full 2^160 bits. Although, if you were trying to crack any one of 1 million (2^20) transactions, you could do a partial birthday…
BitcoinTalk

Re: JSON-RPC password
25 July 2010, 21:34 UTC
+1 to you for having such a long password that you found this bug. Uploaded to SVN as rev 110.
BitcoinTalk

*** ALERT *** Upgrade to 0.3.6
29 July 2010, 19:13 UTC
Please upgrade to 0.3.6 ASAP! We fixed an implementation bug where it was possible that bogus transactions could be displayed as accepted. Do not accept Bitcoin transactions as payment until you upgrade to version 0.3.6! If you can't…
BitcoinTalk

Re: *** ALERT *** version 0.3.6
29 July 2010, 19:55 UTC
Haven't had time to update the SVN yet. Wait for 0.3.6, I'm building it now. You can shut down your node in the meantime.
BitcoinTalk

Re: *** ALERT *** version 0.3.6
29 July 2010, 20:30 UTC
SVN is updated with version 0.3.6. Uploading Windows build of 0.3.6 to Sourceforge now, then will rebuild linux.
BitcoinTalk

Re: *** ALERT *** Upgrade to 0.3.6 ASAP!
29 July 2010, 21:20 UTC
0.3.6 Linux build is back to the old makefile.unix. It static links libjpeg so that shouldn't be a problem. Is that working better? If you got 22DbRunRecoveryException and you've used someone else's build before, you may need to delete…
BitcoinTalk

Re: *** ALERT *** Upgrade to 0.3.6 ASAP!
29 July 2010, 21:43 UTC
"./bitcoin: /lib64/libc.so.6: version `GLIBC_2.11' not found (required by ./bitcoin)" isn't a new problem that started with 0.3.6 is it? This was built on the same OS installations as 0.3.0. Unfortunately I upgraded to Ubuntu 10.04 before…
BitcoinTalk

Re: Implementation bug prior to 0.3.6
29 July 2010, 22:04 UTC
Actually, it works well to just PM me. I'm the one who's going to be fixing it. If you find a security flaw, I would definitely like to hear from you privately to fix it before it goes public.
BitcoinTalk

Re: *** ALERT *** Upgrade to 0.3.6 ASAP!
29 July 2010, 23:12 UTC
We don't really need pre-compiled header. It only makes it compile slightly faster. I think I'll just get rid of it. Even still, you'd still need to remember to "make -f makefile.unix clean" or delete headers.h.gch one more time to get…
Private email (Martti Malmi)

\[bitcoin-list\] Alert: upgrade to bitcoin 0.3.6
30 July 2010, 05:34 UTC
Please upgrade to 0.3.6 ASAP to get an important bugfix. See the bitcoin.org homepage for download links. ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who…
bitcoin-list (SourceForge)

[bitcoin-list] Alert: upgrade to bitcoin 0.3.6
30 July 2010, 06:02 UTC
Please upgrade to 0.3.6 ASAP to get an important bugfix. See the bitcoin.org homepage for download links.
BitcoinTalk

Re: Bug: "Immature" coins lost in wallet.dat during transaction
30 July 2010, 19:19 UTC
I don't get how it let you send if it was not matured. Your balance would have been lower than the amount. It would have said balance 0.01, right? If I try that it says "you don't have enough money" or "Insufficient funds" from the…
BitcoinTalk

Re: *** ALERT *** Upgrade to 0.3.6 ASAP!
30 July 2010, 19:53 UTC
I can't understand why you're having so much pain. I just followed the instructions in build-unix.txt. I made a couple little corrections for Boost 1.37, which I'll put on SVN the next time I update it, noted below: Dependencies…
BitcoinTalk

Re: *** ALERT *** Upgrade to 0.3.6 ASAP!
30 July 2010, 21:44 UTC
Except that wouldn't work for boost 1.40+ (on Ubuntu 10.04), where you need to get libboost-all-dev. Seems they changed everything around in Boost recently, "-mt" and all that, makes it hard. BTW, I tried Boost 1.34 but it didn't have the…
BitcoinTalk

Re: What happens when network is split for prolonged time and reconnected?
3 August 2010, 22:45 UTC
creighto: I agree with that idea. After a few hours, it should be possible for the client to notice if the flow of blocks has dropped off by more than would be likely just by chance. It could tell if it's not hearing the hum of the world…
BitcoinTalk

Re: Flood attack 0.00000001 BC
4 August 2010, 16:25 UTC
Bitcoin isn't currently practical for very small micropayments. Not for things like pay per search or per page view without an aggregating mechanism, not things needing to pay less than 0.01. The dust spam limit is a first try at…
BitcoinTalk

Re: Flood attack 0.00000001 BC
5 August 2010, 16:03 UTC
Forgot to add the good part about micropayments. While I don't think Bitcoin is practical for smaller micropayments right now, it will eventually be as storage and bandwidth costs continue to fall. If Bitcoin catches on on a big scale, it…
BitcoinTalk

Re: Flood attack 0.00000001 BC
5 August 2010, 16:30 UTC
One alternative is to use a round-up system. You pay for, say, 1000 pages or images or downloads or searches or whatever at a time. When you've used up your 1000 pages, you pay for another 1000 pages. If you only use 1 page, then you have…
BitcoinTalk

Re: Flood attack 0.00000001 BC
5 August 2010, 16:39 UTC
I don't know a way to implement that. The transaction fee to the block creator uses a special trick to include the transaction fee without any additional size. If there was a transaction for each transaction fee, then what about the…
BitcoinTalk

Re: Flood attack 0.00000001 BC
5 August 2010, 17:49 UTC
If you're only going to have one person work on building the block, that could take days. Oh, do you mean send a different variation to each node with the tx fee written to them? The way it is now, it's whoever builds this gets it. If we…
BitcoinTalk

Re: Not a suggestion
11 August 2010, 00:14 UTC
This is a very interesting topic. If a solution was found, a much better, easier, more convenient implementation of Bitcoin would be possible. Originally, a coin can be just a chain of signatures. With a timestamp service, the old ones…
BitcoinTalk

Re: Where is the separate discussion devoted to possible Bitcoin weaknesses.
11 August 2010, 22:40 UTC
It doesn't have to be such a breaking change. New nodes could accept old transactions for a long time until most nodes have already upgraded before starting to refuse transactions without PoW. Or, they could always accept old…
BitcoinTalk

Re: Flood attack 0.00000001 BC
11 August 2010, 23:28 UTC
It would be nice to keep the blk*.dat files small as long as we can. The eventual solution will be to not care how big it gets. But for now, while it's still small, it's nice to keep it small so new users can get going faster. When I…
BitcoinTalk

Re: Not a suggestion
13 August 2010, 19:28 UTC
I'm not grasping your idea yet. Does it hide any information from the public network? What is the advantage? If at least 50% of nodes validated transactions enough that old transactions can be discarded, then everyone saw everything and…
BitcoinTalk

Re: 4 hashes parallel on SSE2 CPUs for 0.3.6
14 August 2010, 00:49 UTC
MinGW on Windows has trouble compiling it: g++ -c -mthreads -O2 -w -Wno-invalid-offsetof -Wformat -g -D__WXDEBUG__ -DWIN32 -D__WXMSW__ -D_WINDOWS -DNOPCH -I"/boost" -I"/db/build_unix" -I"/openssl/include" -I"/wxwidgets/lib/gcc_lib/mswud"…
Private email (Martti Malmi)

\[bitcoin-list\] ALERT - we are investigating a problem
15 August 2010, 20:37 UTC
\*\*\* WARNING \*\*\* We are investigating a problem. DO NOT TRUST ANY TRANSACTIONS THAT HAPPENED AFTER 15.08.2010 17:05 UTC (block 74638) until the issue is resolved.…
bitcoin-list (SourceForge)

[bitcoin-list] ALERT - we are investigating a problem
15 August 2010, 20:38 UTC
*** WARNING *** We are investigating a problem. DO NOT TRUST ANY TRANSACTIONS THAT HAPPENED AFTER 15.08.2010 17:05 UTC (block 74638) until the issue is resolved.
BitcoinTalk

Re: overflow bug SERIOUS
15 August 2010, 20:59 UTC
Here's the preliminary change. Look right? I have more changes to make, this isn't all of it. Will SVN shortly. Code: bool CheckTransaction() const { // Basic checks that don't depend on any context if (vin.empty() || vout.empty()) return…
BitcoinTalk

Re: overflow bug SERIOUS
15 August 2010, 21:06 UTC
It would help if people stop generating. We will probably need to re-do a branch around the current one, and the less you generate the faster that will be. A first patch will be in SVN rev 132. It's not uploaded yet. I'm pushing some…
BitcoinTalk

Re: overflow bug SERIOUS
15 August 2010, 21:23 UTC
Once you have an update, you could download knightmb's block chain. You'll want one that's old enough that it ends before block 74000 so the most recent security lockin will check it. Can someone find the link for that?
BitcoinTalk

Re: overflow bug SERIOUS
15 August 2010, 21:40 UTC
Patch is uploaded to SVN rev 132! For now, recommended steps: 1) Shut down. 2) Download knightmb's blk files. (replace your blk0001.dat and blkindex.dat files) 3) Upgrade. 4) It should start out with less than 74000 blocks. Let it…
BitcoinTalk

Re: overflow bug SERIOUS
15 August 2010, 22:58 UTC
Don't update the block chain download. When you take someone's block chain download, you don't want it right up to the end. A somewhat old one is better so it can download and verify the most recent blocks. tcatm's 4-way SSE2 SHA-256 is…
BitcoinTalk

Re: overflow bug SERIOUS
15 August 2010, 23:17 UTC
Just leave the old one alone! Older is better. What block number is it? Anywhere from 60000-74000 is good. The one that you've had available for a while has been vetted and is the best choice.
BitcoinTalk

Re: overflow bug SERIOUS
15 August 2010, 23:36 UTC
Starting at 67000 is perfect. Yeah, at the moment you'll stop at 74638. It should start slowly creeping up as more nodes upgrade and generate. Linux build links below. The Linux version includes tcatm's 4-way SSE2 SHA-256 that makes…
BitcoinTalk

Re: overflow bug SERIOUS
15 August 2010, 23:37 UTC
Agree, wanted to do that for a long time, haven't had time to do it. For now, you could also subscribe to the bitcoin-list mailing list. It rarely gets used except for announcements like this and major new versions. Subscribe/unsubscribe…
BitcoinTalk

Version 0.3.10 - block 74638 overflow PATCH!
15 August 2010, 23:48 UTC
Version 0.3.10 patches the block 74638 overflow bug. http://bitcointalk.org/index.php?topic=823 The Linux version includes tcatm's 4-way SSE2 SHA-256 that makes generating faster on i5, i7 (with hyperthreading) and AMD CPU's. Try the…
BitcoinTalk

Re: overflow bug SERIOUS
16 August 2010, 01:00 UTC
Right, it will get reincorporated into the fixed chain. The transaction won't disappear, it'll still be visible on both sides, but the confirmation count will jump back to 0 and start counting up again. It's only if you generated a block…
BitcoinTalk

Re: overflow bug SERIOUS
16 August 2010, 01:02 UTC
If you still show 74638 blocks then you aren't connected to any 0.3.10 nodes. For today, try adding these parameters: -addnode=75.158.131.108 -addnode=99.27.237.13 -addnode=68.68.99.14 See http://bitcointalk.org/index.php?topic=828
BitcoinTalk

Re: overflow bug SERIOUS
16 August 2010, 01:12 UTC
1) Once more than 50% of the node power is upgraded and the good chain overtakes the bad, the 0.3.10 nodes will make it hard for any bad transactions to get any confirmations. 2) If you didn't remove your blk*.dat files, you're not…
BitcoinTalk

Re: overflow bug SERIOUS
16 August 2010, 02:16 UTC
The bad chain is also slowed down as more nodes upgrade. We've already generated 14 blocks since 74638. The builds of 0.3.10 were uploaded about 2 and 3 hours ago. Of the nodes I'm connected to, more than half are already 0.3.10. I would…
BitcoinTalk

Re: overflow bug SERIOUS
16 August 2010, 02:38 UTC
On Windows, findstr /c:"version message" debug.log It looks like the bad chain was on block 74678 recently. Can't wait to overtake it. On the stats at http://nullvoid.org/bitcoin/statistix.php there's been 5 blocks per hour in the last 3…
BitcoinTalk

Re: overflow bug SERIOUS
16 August 2010, 12:59 UTC
It looks like we overtook the bad chain somewhere around 74689. 0.3.9 and lower nodes have been responding with the current block number for some hours now. That means it's no longer necessary to delete blk*.dat before upgrading. You can…
BitcoinTalk

Re: overflow bug SERIOUS
16 August 2010, 22:54 UTC
Un-upgraded nodes have the correct chain most of the time, but they are still trying to include the overflow transaction in every block, so they're continually trying to fork and generate invalid blocks. If an old version node is…
BitcoinTalk

Development of alert system
22 August 2010, 23:55 UTC
I've been working on writing the alert system. Alerts are broadcast through the network and apply to a range of version numbers. Alert messages are signed with a private key that only I have. Nodes can do two things in response to an…
BitcoinTalk

Re: Development of alert system
24 August 2010, 23:51 UTC
If you're so paranoid that you're getting hysterical over this, then surely you're paranoid enough that if a warning message displays on the status bar, you'll check the website and forum. I think if another bug like the overflow bug…
BitcoinTalk

Re: Development of alert system
25 August 2010, 00:06 UTC
This is in SVN rev 142 as version 0.3.11.
BitcoinTalk

Re: Development of alert system
25 August 2010, 15:17 UTC
It can't do arbitrary actions remotely. Maybe some of you are responding to other posters who suggested the alert system should do more? If there is an alert, the following json-rpc methods return an error: sendtoaddress getbalance…
BitcoinTalk

Re: Development of alert system
25 August 2010, 16:40 UTC
I changed the switch name to -disablesafemode.
BitcoinTalk

Re: Development of alert system
25 August 2010, 16:56 UTC
WRT the alert system, who cares? The most the key can do is temporarily disable six json-rpc commands until the site owners either add the -disablesafemode switch or upgrade. All nodes keep running and generating, the network stays up. If…
BitcoinTalk

Re: Development of alert system
25 August 2010, 17:59 UTC
getinfo has a new field that shows any alert messages or other errors that would be displayed on the status bar. The rpc methods return a json-rpc error with the error description "Safe mode: " followed by additional text specified by the…
BitcoinTalk

Re: Development of alert system
26 August 2010, 00:08 UTC
My apologies, your post was indeed a question not a statement.
BitcoinTalk

Version 0.3.11 with upgrade alerts
27 August 2010, 21:54 UTC
Version 0.3.11 is now available. Changes: - Some blk*.dat checking on load - Built the -4way code with -march=amdfam10, which makes it a little faster - Warning if your clock is too far off - Warnings/errors/alerts can also be seen in the…
BitcoinTalk

Re: Issues building bitcoin on Windows 7
19 September 2010, 18:46 UTC
The lines it's tripping on: Code: ERROR extern map<string, string> mapAddressBook; ERROR extern CCriticalSection cs_mapAddressBook; ERROR extern vector<unsigned char> vchDefaultKey; OK extern bool fClient; OK extern int nBestHeight; OK…
BitcoinTalk

Re: Bug? /usr/bin/bitcoind ""
19 September 2010, 19:58 UTC
I don't know anything about any of the bug trackers. If we were to have one, we would have to make a thoroughly researched choice. We're managing pretty well just using the forum. I'm more likely to see bugs posted in the forum, and I…
BitcoinTalk

Re: [PATCH] increase block size limit
4 October 2010, 19:48 UTC
It can be phased in, like: if (blocknumber > 115000) maxblocksize = largerlimit It can start being in versions way ahead, so by the time it reaches that block number and goes into effect, the older versions that don't have it are already…
BitcoinTalk

Re: ERROR - PLEASE HELP ME!
23 October 2010, 18:22 UTC
He was generating invalid blocks at difficulty 1.0. He must have a corrupted entry in his blk0001.dat or blkindex.dat file. He just needs to delete blk*.dat and let it redownload. The safety lockdown detected the problem and was…
BitcoinTalk

Re: Some testing that I did on the testnetwork, my findings.
13 November 2010, 23:25 UTC
Thank you for limiting flood tests to the testnet. Version 0.3.15 combines several features to help legitimate transactions jump the queue during a flood attack. The key was Gavin's idea for prioritising transactions based on the age of…
BitcoinTalk

Re: Transaction / spam flood attack currently under way
19 November 2010, 23:50 UTC
I'm doing something like that. Priority is a more formalised version of the concept you're describing. Yes, like this. And the no-priority-requirement area is 3K, about a dozen transactions per block. I just uploaded SVN rev 185 which has…
Private email (Martti Malmi)

What was the bitcoin.org outage?
2 December 2010, 22:00 UTC
Do you know what caused that outage? Did it need to be rebooted, or was it a DoS or something? The IP was pingable during the outage. Did you get back to davidonpda about his doing a mirror backup? I think that's a really good idea. Do…
BitcoinTalk

Re: JSON-RPC method idea: list transactions newer than a given txid
8 December 2010, 20:21 UTC
It's not safe to use listtransactions this way. I know I've been criticized for being reluctant about listtransactions. Let me explain my reluctance. Transactions are dynamic. Past transactions can become unconfirmed, go away and come…
BitcoinTalk

Re: Fees in BitDNS confusion
9 December 2010, 23:58 UTC
Not locktime. There's a possible design for far in the future: You intentionally write a double-spend. You write it with the same inputs and outputs, but this time with a fee. When your double-spend gets into a block, the first spend…
BitcoinTalk

Re: Bitcoin and buffer overflow attacks
11 December 2010, 13:32 UTC
If you ever find anyone who turned it on. It's disabled by default. It's all STL. There are almost no buffers.
BitcoinTalk

Added some DoS limits, removed safe mode (0.3.19)
12 December 2010, 18:22 UTC
There's more work to do on DoS, but I'm doing a quick build of what I have so far in case it's needed, before venturing into more complex ideas. The build for this is version 0.3.19. - Added some DoS controls As Gavin and I have said…
Private email (Martti Malmi)

\[bitcoin-list\] Bitcoin 0.3.19 is released
13 December 2010, 16:11 UTC
This is a minor release to add some DoS protection. Changes: - Added some DoS limits, though it's still far from DoS resistant. - Removed "safe mode" alerts. http://www.bitcoin.org/smf/index.php?topic=2228.0 Download:…
bitcoin-list (SourceForge)

[bitcoin-list] Bitcoin 0.3.19 is released
13 December 2010, 16:12 UTC
This is a minor release to add some DoS protection. Changes: - Added some DoS limits, though it's still far from DoS resistant. - Removed "safe mode" alerts. http://www.bitcoin.org/smf/index.php?topic=2228.0 Download:…
Private email (Mike Hearn)

More BitCoin questions
10 January 2011, 20:47 (time as published; timezone not given)
By the way, if you didn't see it already, there's a discussion on the security of secp256k1 on the forum: http://www.bitcoin.org/smf/ind ex.php?topic=2699.0 Hal (i presume this is Hal Finney) Yes, it's him. He was supportive on the…
Private email (Mike Hearn)

Open sourced my Java SPV impl
9 March 2011, 17:15 (time as published; timezone not given)
I hope you are doing well. I finally got all the lawyers happy enough to release BitCoinJ under the Google name using the Apache 2 license: It's incomplete - notably it doesn't properly handle block chain splits yet - but the rest is…
Private email (Mike Hearn)

Open sourced my Java SPV impl
9 March 2011, 19:39 (time as published; timezone not given)
See these threads: http://www.bitcoin.org/smf/ind ex.php?topic=1786.msg22119#msg 22119 http://www.bitcoin.org/smf/ind ex.php?topic=2181.msg28729#msg 28729 I see. So right now fees are tricky because you have to decide up front what the…

All topics · Search the archive