Last post of BkkCoins:
I'm still here and haven't abandoned the project. I've had some disruptions over the last week as the tile guys that I've been waiting for since March finally arrived and started putting in floors. I've been moving stuff around from room to room, and it's a mess, stuff piled up everywhere. Timing couldn't have been worse, and my time diverted. I'm setting up my workbench and tools again and back working again, though the room I'm in still has no floor and I'll have to move back again in 2 days. If it were just me here I could probably have delayed them but my wife (and other family) presses on me as well. Plus I really need a floor.
I appreciate the kind words above and want to finalize this whole thing so I can move on. I feel like I'm stumbling around not knowing what's actually going to happen regarding Avalon chips, much disheartened by everything, but trying to keep a more positive outlook.
Last post of Satoshi:
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 clearly before, the software is not at all resistant to DoS attack. This is one improvement, but there are still more ways to attack than I can count.
I'm leaving the -limitfreerelay part as a switch for now and it's there if you need it.
- Removed "safe mode" alerts
"safe mode" alerts was a temporary measure after the 0.3.9 overflow bug. We can say all we want that users can just run with "-disablesafemode", but it's better just not to have it for the sake of appearances. It was never intended as a long term feature. Safe mode can still be triggered by seeing a longer (greater total PoW) invalid block chain.
Builds:
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.19/See the similarities?
Okay, I'm the first to speak out what everyone thinks:
BkkCoins is in fact a group of anonymous developers!
Ente