Dat verklaart wel waarom je wallet.dat ineens weg was inderdaad.

Wat een klote actie

Ik kan wel allerlei advies gaan ophangen over hoe je het beste een aparte PC/netbook kan gebruiken voor je BTC activiteiten, maar daar krijg je je geld niet mee terug.

It'd also need to mark the inputs as spent so that further transactions don't double-spend.
This could be done using `lockunspent` but these are not saved when bitcoind is restarted.

What's stopping you?

The only time I was a bit concerned was when Satoshi left. Luckily, the other core dev team members and the rest of the community have picked up the pieces very well.

There is a Linux script in contrib/qos that allows throttling the outgoing bandwidth for connections on the Bitcoin network.
For other operating systems, there are likely similar ways to throttle certain applications/ports.

Yes, this is still a concern.

There is wallet software that uses "deterministic wallets" (BIP 0032) that use keys that are derived from a single seed. For example, Armory. Those you only need to back up once.

But for example Bitcoin-Qt (and Multibit AFAIK) does not, so you need to back up regularly if you use the wallet actively as new keys are added to the wallet all the time.

Yes. It is encrypted with the same passphrase.

It's baffling.
Also looks like it's mostly US banks doing this.
Sure, there have been some (for example) Dutch banks as well that have blocked transfers to bitcoin exchanges for "fraud" reasons, but none that close or threaten to close accounts.

It is important to distinguish between narrow AI and general AI.

Narrow AI is very realistic. Pattern recognition, data mining, AI in games, trading bots, and so on. Computers can beat humans hand-down in narrowly defined cognitive tasks. Autonomous drones and self driving cars are no longer science fiction.

General AI on the other hand is not much closer than it was in the 60's. Computers are not creative, do not perform ground-breaking science or philosophy, and do not develop a consciousness. They may get there one day, as there is no physical reason why it would not be possible, but this is far future sci-fi.

However, what is defined as "AI" tends to shift over time. Back in the 60's, a computer playing world-level Chess would be defined as AI, on-par with a human. But in time we discovered that there is much more to it than playing games effectively.

Yes. But as always, backup your wallet.dat regularly to make sure a freak accident doesn't lose your coins.

I've added a note to the forum post.

You can't put the genie back into the bottle.

If you insist on sticking with Apple you can use Kyle Drake's coinpunk wallet, which is completely HTML5 based so cannot be banned by Apple.

See https://www.youtube.com/watch?v=L77XfFnoxdI

The -beta has been there in every release since the beginning.

* dumpprivkey
* dumpwallet
* importwallet
* keypoolrefill
* sendfrom
* sendmany
* sendtoaddress
* signmessage
* signrawtransaction (if keys are not provided on command line)

(just look where EnsureWalletIsUnlocked is used)

As many people have done, I guess it qualifies as learning experience.

Bitcoin-Qt version 0.8.6 final is now available from:

  http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.8.6/

This is a maintenance release to fix a critical bug; we urge all users to upgrade.

Please report bugs using the issue tracker at github:

  https://github.com/bitcoin/bitcoin/issues

How to Upgrade
--------------

If you already downloaded 0.8.6rc1 you do not need to re-download. This release is exactly the same.

If you are running an older version, shut it down. Wait
until it has completely shut down (which might take a few minutes for older
versions), then run the installer (on Windows) or just copy over
/Applications/Bitcoin-Qt (on Mac) or bitcoind/bitcoin-qt (on Linux).

If you are upgrading from version 0.7.2 or earlier, the first time you
run 0.8.6 your blockchain files will be re-indexed, which will take
anywhere from 30 minutes to several hours, depending on the speed of
your machine.

0.8.6 Release notes
===================

- Default block size increase for miners.
  (see https://gist.github.com/gavinandresen/7670433#086-accept-into-block)

- Remove the all-outputs-must-be-greater-than-CENT-to-qualify-as-free rule for relaying
  (see https://gist.github.com/gavinandresen/7670433#086-relaying)

- Lower maximum size for free transaction creation
  (see https://gist.github.com/gavinandresen/7670433#086-wallet)

- OSX block chain database corruption fixes
  - Update leveldb to 1.13
  - Use fcntl with `F_FULLSYNC` instead of fsync on OSX
  - Use native Darwin memory barriers
  - Replace use of mmap in leveldb for improved reliability (only on OSX)

- Fix nodes forwarding transactions with empty vins and getting banned

- Network code performance and robustness improvements

- Additional debug.log logging for diagnosis of network problems, log timestamps by default

- Fix Bitcoin-Qt startup crash when clicking dock icon on OSX

- Fix memory leaks in CKey::SetCompactSignature() and Key::SignCompact()

- Fix rare GUI crash on send

- Various small GUI, documentation and build fixes

Warning
-------

- There have been frequent reports of users running out of virtual memory on 32-bit systems
  during the initial sync.
  Hence it is recommended to use a 64-bit executable if possible.
  A 64-bit executable for Windows is planned for 0.9.

Note: Gavin Andresen's GPG signing key for SHA256SUMS.asc has been changed from  key id 1FC730C1 to sub key 7BF6E212 (see https://github.com/bitcoin/bitcoin.org/pull/279).

Big bitcoin holders only control the market up until the point that they sold all their coins. They can have deep pockets, but not infinite ones.

This is very different from the FED which can print new money as they wish.

Okay, good luck! The project can always use more devs

I'm not sure -- I suggest discussing this on the development mailing list. There are quite a few people that don't want to put all eggs in one basket on github.

You don't understand how it works. We always have two active branches:

- 0.8.x AKA stable AKA "maintenance releases"
- master AKA unstable (which will be 0.9 when it is released, this is expected end of next month)

The new features that you mention (and more) are in the master branch, thus will be in 0.9.0rc1 when it is released. These new features also introduce potential bugs so the risk profile is larger.

Stable releases such as this one only contain bugfixes and very minor changes. By all means help by testing Bitcoin-OMG and other test builds, but they are not recommended for production usage.

(and this is a release candidate for a stable release, which is unusual, but we decided to go for this instead of a straight 0.8.6 release because we're not 100% that the MacOSX corruption fixes fix the entire problem. In any case, given that no new issues arise, this will be relabeled 0.8.6 final really soon)

Extremely cool project, I'll certainly be watching this.