# Gavin Andresen
# 2011-02-20 22:49:17
# https://bitcointalk.org/index.php?topic=3638.msg52078#msg52078

@s{quotedtext}
@s{quotedtext}
 @p{brk}
CSV file with the private key and block numbers is a good idea, although for it to be a valid CSV file then it needs to have a fixed number of columns. @p{par}

I'd modify the design slightly to be just: @p{brk}
base58 encoded privkey,block number @p{brk}
... where block number is the block number of the earliest input (that'll save rescanning time@p{--} you probably always want to rescan from the earliest block number, anyway, in case more payments were sent after you exported the key). @p{par}

Also what do you mean by "export" @p{--} write and then remove the keys from the wallet?  Write a newly generated key and generate a payment-to-that-key for a given amount of coins? @p{par}

I think any code that removes keys from the wallet (or generates payments to keys that are never added to the wallet) needs to be structured as two distinct steps: @p{brk}
1. Write the keys to @p{lt}destination@s{gt} @p{brk}
2. Read @p{lt}destination@s{gt} to make sure it is valid, and, if it is, delete the corresponding keys from the wallet (or generate the send-to-self txn). @p{brk}