THIS DAY IN BITCOIN HISTORY
July 29
12 of Satoshi’s emails and forum posts are dated July 29 (2010), quoted from the original sources.
What Satoshi wrote on July 29.
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…
Re: *** ALERT *** Upgrade to 0.3.6 ASAP!Quote from: lachesis on July 29, 2010, 10:14:36 PM On Debian testing 32-bit, I get a few build errors, all resembling: Code: script.cpp:114: error: OP_NOP1 was not declared in this scope I got these when attempting…
Re: *** ALERT *** Upgrade to 0.3.6 ASAP!"./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 t…
Re: *** ALERT *** Upgrade to 0.3.6 ASAP!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…
Re: *** ALERT *** version 0.3.6SVN is updated with version 0.3.6. Uploading Windows build of 0.3.6 to Sourceforge now, then will rebuild linux.
Re: *** ALERT *** version 0.3.6Haven'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.
Re: DifficultyYou were looking at the wrong code. Here's the code that applies: Code: bool CBlock::CheckBlock() const { ... // Check timestamp if (nTime > GetAdjustedTime() + 2 * 60 * 60) return error("CheckBlock() : block times…
Re: Implementation bug prior to 0.3.6Actually, 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.
Re: Linux distribution downloadYeah, acutely aware that I should have stayed on 9.04 or 9.10. It's a lot more work to downgrade than upgrade and I've been squeezed for time. Ubuntu is the most popular distro, so I'm staying with that.
Re: Scalability and transaction rateThe current system where every user is a network node is not the intended configuration for large scale. That would be like every Usenet user runs their own NNTP server. The design supports letting users just be users…
Re: Transaction disappeared in the void...If the transaction didn't go out immediately at first, like if you weren't connected at the time, it may take up to 2 hours to resend it. Long term, it does keep relentlessly sending it. I'll shorten that length of ti…
Re: wiki registration email?WTF? How did we get on that? AFAIK, the only e-mail is if you tell the forum to do notifications, and I guess the wiki registration. I'd consider turning off the forum notification e-mails, I don't know why we have that.
As an additional firewall, a new key pair should be used for each transaction to keep them from being linked to a common owner. Some linking is still unavoidable with multi-input transactions, which necessarily reveal…Read the full quotes ↗
Pick another date.
This day in Bitcoin history.
One short email each morning with what Satoshi wrote on that date, linked to the original source. Unsubscribe anytime.