To mine you just need to purchase a specialised "fart mining" device (a WiFi "cushion" that broadcasts the specific details of each fart to the "fart mining network" which in a distributed manner decides which farts will be used to extend the chain of all memorable farts).

Units can be pre-ordered in BTC and we'll deliver them when we are good and ready.

Note: there will no pre-mined farts and please consider the environment before ingesting large amounts of beans.

I was rather surprised to see Bruno's posts about Bitcoin100 deciding to donate money to the Bitcoin Documentary film idea (fielded by a member who AFAIA has mostly only posted in the Speculation board previously).

I don't know if I am alone in this thinking but I thought that Bitcoin100 was created to help charities and I don't see how making a documentary film about Bitcoin really fits into that vain (it seems to be rather a world apart in my view at least).

I have been a supporter of the original Bitcoin100 idea (and was one of the initial donators to it) and I would like to be convinced that this is a good idea so perhaps this could be answered.

Please note that this is not intended as any sort of trolling thread but just to gauge what other Bitcoin100 donators think about this.

Could not believe this - went to HSBC and also BOC and neither banks would *let* you *open* an account despite having sufficient ID. In the mainland you just go into any bank with your passport and they open an account with zero questions.

Rather surprising to say the least.

Was thinking about "emptying" my wallet (for better anonymity) and although not that tricky is a slight pain to have to do pull up a "calculator" to work out the exact amount to send when taking into account the tx fee (assuming it would be > than the minimum due to cleaning out the "lint" of small unspent outputs).

Perhaps it might be worth adding a "Send All Funds To" check box to the "Send coins" tab so that the amount to send (minus the required fee) can just be worked out automatically for the end-user?

Running bitcoin-qt on a not so powerful laptop running XP can be a pain as it consumes basically all CPU every time it validates a new block (so every 10 minutes or so my computer *freezes* for generally around 5 seconds which feels like a long time when you're trying to code).

Of course I know how to lower the priority of the bitcoin-qt process (and do this for now) but I think this makes for a pretty bad new user experience (especially if you are catching up blocks) and I would guess that many users may not even know how to adjust the process priority.

So maybe it would be a good idea to have a setting to "Run as low priority"?

For the newbies who can't reply to the main thread (in Project Development) I've created this thread (please refer to the main thread https://bitcointalk.org/index.php?topic=132006.0 for details of how CIYAM Open works).

Please try and help me out by pushing this raw tx if you can:

Code:

01000000012083d029fb7d82921aac5e36e02c152f8dd74e5798197f060ecdff0ed7cb7a3b010000008a4730440220231c75022c55603400521a0daba522afdf16f8a71b3c00108e00c15b0707f43202200ca00128831405020055183c83e0ed4e786fd6297dfc1da0718a22301a7e2b6001410478733799662c00333f074ce5b24935fe140572d83cf176989fdd260dea1609a07e42708fed07ad9c9d2ddfccf4451037dc380221b690abf740f30beaca94d80affffffff010092b2e3040000001976a914164ed07f460ece3dbc4c04509b75580b7bee736a88ac00000000

If I can't get it back via a doublespend then I hope that if the lucky miner is one of the major pools then they would consider making a generous donation to the CIYAM Project (as otherwise that is 100 BTC less I will have to pay people for tasks).

Another milestone towards CIYAM Open's 2013 mission has been achieved with the publication of the CIYAM Safe LiveOS on SUSE Studio: http://susestudio.com/a/kp8B3G/ciyam-safe

Using the distro as the LiveOS and after installing ZBar on your online computer you can create addresses and sign transactions in a manner that does not require USB (other than the live distro itself) as long as both your online and offline computers have webcams.

All source code is included - several various scripts and utilities are included from https://github.com/ciyam/safe and a slightly modified (just command line args not algo) version of "scrypt" from https://github.com/ciyam/scrypt.

If anyone would like to help test this it would be greatly appreciated (please consider it to be a "beta" at this stage and only test with very small amounts of BTC).

It should be noted that this is *not* trying to be an offline "wallet" in the same vein as Armory (although I guess it could be used for that purpose) and is not suitable for the technically non-savvy (you need to construct raw tx's) or for performing large numbers of tx's quickly. It's a bit more of a "nuts and bolts" type solution that was put together for the purpose of being able to create "paranoid" levels of security (as CIYAM Open intends to make sure its donations do not go anywhere apart from where they are meant to).

It has been tested with real transactions and testing also included re-installing the LiveOS (i.e. as if you'd lost it). The documentation is serviceable but far from "great" and the whole package could certainly be improved with some polish (if others are interested in using this and would be prepared to donate some funds towards adding more functionality then I will consider opening a project for it on CIYAM Open for it).

Of course others are welcome to copy this (or add QR comms to their own offline wallet projects).

After some brainstorming about this whole difficult passphrase and keeping it safe I have come up with the following:

http://ciyam.org/memory_key.html

Please note that the form doesn't actually post anything to my or any other website and of course it can be run offline.



R21L03A251E16Y72D03E13O122X21R19F31Z34

I have been trying to think how it might be possible to create a UI to supply (at least part) of a hash that is somewhat like a password but nothing typed and nothing difficult to remember and came up with this idea:

Picture a specific memory that is significant to you and let's go and find it:

Code:

beach #-- party
park      sunbathing #-- music
home      swimming       book
lake      volleyball     clouds
snow      ...            water #-- swimmer
office                   ...       shartk
school                             dolphin #-- summer #-- early morning  #-- happy
...                                whale       winter     mid morming        sad
                                   boat        spring     late morning       surprised
                                   ...         autumn     early afternoon    amazed
                                                          ...                alarmed
                                                                             ...

Has this already been built (if so is there an open source version) and if not is anyone interested in doing so (for bitcoins of course)?

Okay - I have sent 10 BTC to the following Bitcoin address (generated using vanitygen):

1CpueVNsEWgEhGD44ymVNoksyFp9Eekec7

and the next piece of information is the private key for that address that has been GPG encrypted:

-----BEGIN PGP MESSAGE-----
Version: GnuPG v1.4.9 (MingW32)

hQEMA8M4in1e/mjNAQf9HZKDFHUx+bn1/UqxSnEL161h1Yjplp5ijqeW36CrO6HR
PQgxfgT8Jddxkly+7bqZHwOHW68J8X0J/yfuO0mQ4MSVg3+x8Y1Ty/cujVv55bD0
/S3bHmPepKm57dHLsZ1CY3DT3/9mACnhqsQ84pPQKLQl7UNbhXhc9Il8hkcLS/Co
zpXh7GUuAMrA6TZZM+FLcD/oy5RU/50l5HIomG/fmRimtYu/N7i7y4mJYLh506DW
3HEaRUH4uEgPlpUIiSEQPPsiTt/9nRWdZB6t0mRLMivs/uvqmXygEa+BDV9ZWe7W
wB71vA+IHfPWmu5nXnYuqIvVBlGR8aCi6toXgaD5eNLADAG6kctTwLVA3l8dP/BE
bJNdi5HrYiPuz4hiE4xgTcwL8zppWoWfZCvmSpo1UE7Pmvdw2o60jtCOcK/qM/Bo
jpmvGRRvZVUuGV2flbf0DiTHTOGZ03AR81B+zoJKcN+VqeX/aLSG/QgKZAmkonSt
mGynLSYJgXlKttMNy6bzdSH1ImXH4ZYHjK4HLmVdoZ2DX5tEPMwRa7v9EzGmwNxT
Ii+TXhbaSd5PIRHobqticGcMGaLOgaAOloml18Pz65pYvzOMRTUBhyFu07BnOQ==
=nmS0
-----END PGP MESSAGE-----

Now the GPG public key and private key (encrypted of course) are as follows:

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.4.9 (MingW32)

mQENBFDZhQIBCAD7GbsEa7PGP69KBSc/iOiXcqPr1BfYg6jBTZOz1G/qpJcSjG/Y
asGmnTh4zYlNy2qXvmcvoz0HAg3JatMUJKRTLIhs784QrzC3iRsvvf1RkWA2L34d
2B3/N3hI+ws/Q+3Q2lv5KkpcfYCZeVFkzPhGx3kanwZdGycTxmtlSBvLBYXKYpTF
aw/NE93of584/C/zzr0dqGj4T4izGBhW6SioPFgKwCE6meQJhHtstprDM0PYE7Uq
huZ5pgUL270KBctDqau6jXUMXRaRURFElcZmFzHhMagcDovcScmk1LHyQ5IwrAxs
6ZdIOLnZin1GQqwcpt4IPdb+CXLFFDIoFWr1ABEBAAG0H0NoYWxsZW5nZSA8Y2hh
bGxlbmdlQGNpeWFtLm9yZz6JATgEEwECACIFAlDZhQICGwMGCwkIBwMCBhUIAgkK
CwQWAgMBAh4BAheAAAoJEG9KjkBCBMbav1sIAOpol6INIBZ96QX8EGKJ38ptcW+C
7iFfZcCR8ObaTqpwvlgOw+n+H6sbw3i9xbfnplHo59dfhCCSQaObRIIH7Nb7Xxn7
Ep490lBcAXeeWd7jcnEKEFvuOUhSlQVGiunMUroHlZ1j38cNeXwUm9+hyZTZ+oHv
Izs0DeXZZDIvc51aBreTTJd6d9NSk+Zr99xw5oBdWfyPqFv+wnB60w4IEtdS5r6K
26O6JelDCzek0C9umOIRv3S6RlR0s9vkaunviV8zqfYnxZR6cch9utEcc3cdApus
uSjZS4nAQxBdUmyzY3hDKXHkLweS9MWBRAD6y+qJ9xyntac2/+QD3KKYVO65AQ0E
UNmFAgEIAOfP4v8I1Dy86eJUdqvVEAJlPPa0XGrPT2ew1AkNsxvBrEBSV4iQvnQW
x8VbEVxPa9jK/DB08wCNsC2gOhLVOf3GMSEeqhJVr+eZoHAF6f/Ozuw6kL04tb0I
GjHMtRh1MtJJBs3q3rBhGnB67weyY9VZmtcanCHTGygfzmGlfQuHwC1e/exl6AtW
HRZTEhx3FK+f/6kU8Zci6WA1QjDfxoCFXey8Va9XPdr8VPwPzyPDhEtlZD8/cIVZ
l55l77NhubYl1qs2SH6sWCDEYyA23O0pxrN2EGVv4jz6GkH5Ufr8IkfS5oEKEeHb
XLUOIK++ABQPLvvbJ9M1rFdxD11NGfsAEQEAAYkBHwQYAQIACQUCUNmFAgIbDAAK
CRBvSo5AQgTG2j7CB/9yQMbYz3tC8X7uoUrHAWYT/9JajH1Qr/2lzssvBYO8CEZY
6zedXBanMWNsTKHcDQkhZ2GFSsC74nA7Nn8vTv2WkY1Nfp/qZT95cg8B0FNQPLOu
/zHU5lZD/oJkgc28uv0z7C+saMXpNnoddhztEn7IOyXrSIu1+TucWnyDapzeOS4x
sUMk8nYzrdCjg1dbpqm+EEW0iFaZlITRkeUA94F627DWa3Fp7g+u/z3pUtkpFmRB
YYzRUiI7HEoNUmTGN1sSfgUD1bT0kd5Azy2+bE53B0LEUjMsBKcKQ5SHciLnkhU+
ehVrzP1BZQI6RuF14c7Bzkba7wt8OafmEAqoYO8Z
=nIuP
-----END PGP PUBLIC KEY BLOCK-----

-----BEGIN PGP PRIVATE KEY BLOCK-----
Version: GnuPG v1.4.9 (MingW32)

lQO+BFDZhQIBCAD7GbsEa7PGP69KBSc/iOiXcqPr1BfYg6jBTZOz1G/qpJcSjG/Y
asGmnTh4zYlNy2qXvmcvoz0HAg3JatMUJKRTLIhs784QrzC3iRsvvf1RkWA2L34d
2B3/N3hI+ws/Q+3Q2lv5KkpcfYCZeVFkzPhGx3kanwZdGycTxmtlSBvLBYXKYpTF
aw/NE93of584/C/zzr0dqGj4T4izGBhW6SioPFgKwCE6meQJhHtstprDM0PYE7Uq
huZ5pgUL270KBctDqau6jXUMXRaRURFElcZmFzHhMagcDovcScmk1LHyQ5IwrAxs
6ZdIOLnZin1GQqwcpt4IPdb+CXLFFDIoFWr1ABEBAAH+AwMCFjQ1G6zKAqxgwLG1
VWj/tRSQhSb6e7JvNVLhok7sRtgF4FmcbU3vYRHSLEMfx4jO0BzBPqplYpMtAyUb
d+bwYLx42etKy77Ky8xATUjQ/Wg3rL6q1H3NUCqvFxNVXTgL9auV/5vTgYjCftOZ
fK3f36uRnaDYcxAdL6xU8znALQnG3ytJkNKOkrOIg1N+gfCZIVM1gzLLJYMecjnF
y+CmGFLtyCd65B65YayetNHLqyhHQcWWiqJfEkMt7VqWczOhHVx6NWN868zTImMy
+Xo05/YXxNJ49qZdogSfFqk/mib5/nQD7tvRVuF9cKIBL1eoiQ0FgDYD7BtEnzeV
1qwab9xrQpupv45qqRbnUqhFQp96Xx4LysXAdkjt8TLOeHEt+t4J9yN/fBbgn0qo
W5FNyXhaI4FqgN/mnBw26GWKisdWD3oOptA/n/fA3ATn+QOFBg1++pIjbCuqWsnD
76ZxX2t1e1t7jAOsG964PxM6WfIdsAdYaUyfiNw+P9URky97dphYDGXslpcsgNfq
POTDZPEdOK27Ugyo1NNzgX31l3/Q1XqjjWj+u9/zf/+6illj1xjDA5T6trYVDAPL
49uTs/NKiI5cJsvcYrc9x+RsZaTcz1nOq3rI6mKUhaajOv8VVc55odzDG89fYnQB
pFGBhKZsxSUAmddUjzxNAlxL9/zPC4dLJBetyt+84TvFc88BOnD8aOG08tdsBoiQ
7uja99fHMsEtf9Tjtgta9DMVQT/LljiG28AEvLgrhPdWF6llf3phwDow9LO49GO9
42pKmFa2QL/KfVnb6wYRE3cWv2Rv1vKM3RbD+A/+DMjUSQDM+KuEAHAVhmaHHVO2
n94k0U6kobMAQiprAOQo79wRza7xexWTtmpZgX8JFlSnByhUnDZUQhoFvG2PsXb8
q7QfQ2hhbGxlbmdlIDxjaGFsbGVuZ2VAY2l5YW0ub3JnPokBOAQTAQIAIgUCUNmF
AgIbAwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AACgkQb0qOQEIExtq/WwgA6miX
og0gFn3pBfwQYonfym1xb4LuIV9lwJHw5tpOqnC+WA7D6f4fqxvDeL3Ft+emUejn
11+EIJJBo5tEggfs1vtfGfsSnj3SUFwBd55Z3uNycQoQW+45SFKVBUaK6cxSugeV
nWPfxw15fBSb36HJlNn6ge8jOzQN5dlkMi9znVoGt5NMl3p301KT5mv33HDmgF1Z
/I+oW/7CcHrTDggS11Lmvorbo7ol6UMLN6TQL26Y4hG/dLpGVHSz2+Rq6e+JXzOp
9ifFlHpxyH260Rxzdx0Cm6y5KNlLicBDEF1SbLNjeEMpceQvB5L0xYFEAPrL6on3
HKe1pzb/5APcophU7p0DvgRQ2YUCAQgA58/i/wjUPLzp4lR2q9UQAmU89rRcas9P
Z7DUCQ2zG8GsQFJXiJC+dBbHxVsRXE9r2Mr8MHTzAI2wLaA6EtU5/cYxIR6qElWv
55mgcAXp/87O7DqQvTi1vQgaMcy1GHUy0kkGzeresGEacHrvB7Jj1Vma1xqcIdMb
KB/OYaV9C4fALV797GXoC1YdFlMSHHcUr5//qRTxlyLpYDVCMN/GgIVd7LxVr1c9
2vxU/A/PI8OES2VkPz9whVmXnmXvs2G5tiXWqzZIfqxYIMRjIDbc7SnGs3YQZW/i
PPoaQflR+vwiR9LmgQoR4dtctQ4gr74AFA8u+9sn0zWsV3EPXU0Z+wARAQAB/gMD
AhY0NRusygKsYO5Pw1DjgpQRR40Ap2/VtpklqmVVphBk8Vr6SdnULIAU14S+7VS6
8jJInTtntgG/KqXGALCAbHZjehcq1pt5KLaQxjAAgDgo4YOEqqsU2/6vVdOyuLBp
DUG0HbIEKFicUcsw7LUIpHukAk7kajomRIYCKjwsGU5/igVeIu9N3vOT1DOWz5Fd
FvilzXmazIIms1RUZhWdS1kojXK1Rw5osW5TxuLMTmtS6Cw1v5U8PTJoi+/OmxtH
RnCcGS3liZIBTrv6YvgcD+MZ2xgY87LzZKeEGq9eG34cLme64pNgjSoPqRcbgWDU
wgE6x8eTRLqQaZ1bwIBciRE08X+PyiHcxPZAOEopahuNguMpn+5THfOhwOLESxP1
yvXpQtSZdtKoLdMzMRQ3f2JK+IBjuVOCOek1tky2IeScFDyFRRuyAn8PEqMTkzOs
DGP0QgVaVx7BYzfVyYEkVSPmzPIxt+trRiaVaOCOwTY/8zCXIP5JAGTYEBT1S6/b
2OkbuNn5d3QBY+3OD0bSGt6pcQqhPVj8O7YNz+TatQ60oyKdQN7RXfodAT0gcgVn
QGjXCF7eytByIY6TPmE3Ch63vPLYqjmsJk5xbBa9kfVm027C7CMdJYU86BVp9OGm
4nH8LWnnUtlQEzqPSzes0cJiKF7xCQR094xzwvWIuYanQ/qSORovlI3VzcNnmZlf
7DFjk0HVJxzdudhdOYxSMEAs6c8u+yQeyNFdBsFQtO40auvg2La4dPJMRqwQuowa
qS9G3Dy+NqfUp1KW1lwzJopB4dKcRo28MIrteUQjKDCh+WKq6rQsXWz+AZ2b5mmX
wlFEBmxy52s8qSrPIjBUmeSRsPK8WFTJQ8cSZGjlyQ4Zko6BNZB9AbosQk2ujU32
ojz03DmV/Q/LdAMd4nWJAR8EGAECAAkFAlDZhQICGwwACgkQb0qOQEIExto+wgf/
ckDG2M97QvF+7qFKxwFmE//SWox9UK/9pc7LLwWDvAhGWOs3nVwWpzFjbEyh3A0J
IWdhhUrAu+JwOzZ/L079lpGNTX6f6mU/eXIPAdBTUDyzrv8x1OZWQ/6CZIHNvLr9
M+wvrGjF6TZ6HXYc7RJ+yDsl60iLtfk7nFp8g2qc3jkuMbFDJPJ2M63Qo4NXW6ap
vhBFtIhWmZSE0ZHlAPeBetuw1mtxae4Prv896VLZKRZkQWGM0VIiOxxKDVJkxjdb
En4FA9W09JHeQM8tvmxOdwdCxFIzLASnCkOUh3Ii55IVPnoVa8z9QWUCOkbhdeHO
wc5G2u8LfDmn5hAKqGDvGQ==
=llev
-----END PGP PRIVATE KEY BLOCK-----

Now - let me just explain that I created this GPG public/private key pair on an older laptop (that is not able to connect to the internet) running a Live OS in which I used the following script with some not so very creative changes and a 4 character password (a random [EDIT: actually not random at all but was not hinted at as it was going to be a last resort if it wasn't cracked without it], non-dictionary with numbers and letters both upper and lower case) with the final hash of this password being used as the password for GPG...

Code:

#!/bin/bash

read -s -p "Password: " password

password="${password}+${password}=${password}${password}@L3AsT" # NOTE: this line was changed...

password=`echo $password | sha256sum`
password=`echo $password | awk -F ' ' '{ print $1 }'`

echo $password | xclip
echo Password hash is now on the clipboard...

Santa has loaded up that address with 10 BTC (and the funds won't be being moved by myself until at least until January 3rd 2013).

Happy holidays!

CIYAM Open is now ready for Contributors and Project Managers to join in creating a new kind of digital workforce.

The first 10 Project Managers to join (6 places are still left) will be able to have one Project in CIYAM Open "fee free for life".

Developers need to make a "dib" for each task that they wish to work on - understand that a dib is not to do with funds but with *time*. By submitting your dib you are committing yourself to providing a git pull request by the date and time you entered in your dib. The funds allotted will be paid out in entirety to the Contributor whose dib was accepted and whose git pull request was merged by (one of) the git repository owner(s).

Note that only the Contributor whose dib is Accepted would ever be expected to work on the task and understand also that each task includes one or more "skills" for which "skill points" will be awarded or deducted from the Contributor (depending upon whether an Accepted dib is finally Completed after a git pull request merged or is instead Rejected). Also understand that the acceptance of any particular dib is entirely up to the Project Manager (guidelines and further software will be developed to help with this down the track).

http://ciyam.org

(includes links to CIYAM Open as well as the CIYAM Safe distro which is used by the CIYAM project for 100% air-gapped offline transaction signing and the CIYAM github repository)

[mods] please delete this topic as I created another one for the project announcement due to a mix up

What is Bankcoin you ask?

It would be a very simple alt-coin whose main difference to Bitcoin would be that mining would only be permitted to occur from IP addresses that can be proven to be owned by banks (verification perhaps being perhaps via CA or something better if available).

In order for people to have faith in Bankcoin it would have a fixed coin limit and could not belong to any single bank. No coins would be pre-mined with mining beginning only after all banks that want to participate have been able to set up servers specifically for this purpose.

How would people purchase Bankcoins?

This is the part that most on this forum will hate - you will need to purchase them from your bank (so you basically end up with an extra account that holds Bankcoins).

How would banks make money?

As they always do through fees for tx's and for converting your Bankcoins to and from other currencies.

Advantages for banks?

Hugely revived reputation from being able to offer customers a truly valuable resource that can ensure that their hard-earned savings aren't going to be eroded away by inflation (and this being able to be achieved for little more than the cost of the promotional advertising).

Advantages for Governments and the Uber-Wealthy?

Governments will be able to easy trace every single tx to the account holder and the Uber-Wealthly will get to stay that way by being the "early investors" in Bankcoin.

Anyone else think that Bankcoin is a likely "government friendly" alternative to Bitcoin and a fairly cheap way to make it disappear as a (political) threat/problem?

I'm not sure how many members of this Forum use NoScript but I find it to be a pretty useful FF add-on and was thinking if they could be encouraged to accept BTC donations then I would be happy to throw at least 1 BTC their way.

Was also thinking if they could add a feature that optionally lets you see a list of SHA256 hashes for each loaded .js file then that could be a worthwhile security enhancement for users of blockchain.info and other web-wallet services that rely on keys being generated in .js.

A few weeks back I sent 1 BTC via Coinapult to my nephew and all seemed to go fine (i.e. the email was sent), however, he only got around to installing a Bitcoin client the other day and when he went to the site to try and redeem the 1 BTC it reported the balance as being 0 BTC.

He sent a support request (which hasn't been responded to in now over 48 hours) and I sent a PM to Erik (which hasn't been responded to for over 24 hours) with the relevant tx id.

Some support would be appreciated to work out what has happened to the 1 BTC (unfortunately not the greatest first experience for someone to have with Bitcoin which now makes me hesitant to recommend Coinapult for such purposes).

I have just started playing the the listunspent/createrawtransaction/signrawtransaction/sendrawtransaction RPC commands which work great, however, there are a couple of things I am wondering about.

1) Why doesn't the listunspent include a bitcoin "address" as well as the public key in the JSON output (as I can't easily tell what is what when I'm looking at that without jumping into blockchain.info to look up the tx)?

2) If I want to send to more than one output address with createrawtransaction what is the exact syntax (an example somewhere in the docco would be nice)?

There have been numerous threads discussing how to generate offline wallets and typically the problem ends up being that if your keys a) generated from a password or b) stored in clear text on a disk then they are subject to attack keyloggers or malware.

I am wondering if using GPG would provide a simple solution by having the output of vanitygen encrypted to a GPG public key (the private key not being known to the "offline" system). With this approach even if the "offline" system was stolen no generated private keys could be taken (apart from the GPG key which is actually of no consequence).

I will probably put together a small script/program to accomplish this but I guess if the GPG functionality could be built in to vanitygen itself this would be even more secure (i.e. so the private key is never output as clear text).

(see source in posts below)

From my debug.log:

Code:

************************
EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_6system12system_errorEEEEE       
close: Either the application has not called WSAStartup, or WSAStartup failed       
C:\Program Files\Bitcoin\bitcoin-qt.exe in ThreadRPCServer()       

This is occurring every time I exit.

I've created a patch here: https://github.com/ciyam/bitcoin/tree/importprivkey_rescan_opt

This would be mostly useful when importing a lot of private keys (such as you might wish to do if using vanitygen to create a set of vanity addresses) especially when you know the public addresses for the keys you are importing have not been used.

I had posted about this in another thread but I guess it wasn't noticed so just thought I'd post it here.

Unfortunately I don't have the setup or time to actually compile and test it (too busy on my own project) so if someone else could do that it would be great (and I don't need any credit so if someone does take the time to compile and test it then they are welcome to push the patch as their own).