📅 Original date posted:2013-05-07
📝 Original message:On Tue, May 7, 2013 at 2:28 PM, Gavin Andresen <gavinandresen at gmail.com>wrote:
> "sweep private key" is the missing functionality.
>
> I agree, it would be nice to have.
>
>
> On Tue, May 7, 2013 at 8:16 AM, Adam Back <adam at cypherspace.org> wrote:
>
>> Hi
>>
>> Three minor security/other issues:
>>
>> 1. please a way to unlock the wallet without displaying wallet password in
>> console screen (console unlock wallet, to import priv key); or
>>
>> 2. a button to import a private key (and option to transfer it to another
>> key - if you are not the sole controller the private key)
>>
>> 3. a UX way to transfer BTC off a specific adress (eg choose from
>> address), rather than having to spend the entire wallet onto a new
>> address, just to get BTC off a specific address. Doing it that way has
>> problems: creates more network traffic/bigger packets, higher fees (if
>> any transactions are young/low confirmation), and generally damages
>> privacy as all your funds end up linked.
>>
>
Yes, sweep (send all the coins from this addresses to me) should certainly
be added. Maybe even a way to do it periodically, though but that would
require remembering the key.
Importing private keys into the wallet will not be added as a user-friendly
option, as it is dangerous and potentially confusing.
As for (1), I think a better solution would to add a list of commands whose
arguments are censored in the console screen and command line history. At
least `importprivkey`, `walletpassphrase`, `walletpassphrasechange` should
likely be in that list.
Wladimir
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130507/ffc4c167/attachment.html>;
Wladimir [ARCHIVE] /
npub1xq…ymc2p
2023-06-07 15:01:29
in reply to nevent1q…8d6p
Author Public Key
npub1xqshkqv2g7uea4xzqwvmgjcz7u8vfavw6aazs999v0azsv3w7u3qpymc2pPublished at
2023-06-07 15:01:29Event JSON
{
"id": "a971236334996eb899f42fd003b65cf0fb46958bb5c0999e06e66152119289ea",
"pubkey": "30217b018a47b99ed4c20399b44b02f70ec4f58ed77a2814a563fa28322ef722",
"created_at": 1686150089,
"kind": 1,
"tags": [
[
"e",
"dfebb97931ee4d94ee5311610e113ce5f0978d0922c32276827fb08b1a4adab8",
"",
"root"
],
[
"e",
"ca462a1156ee447ea7dd79d0dab5179f0dbd77180c069b44e32d5b61714e4f6a",
"",
"reply"
],
[
"p",
"857f2f78dc1639e711f5ea703a9fc978e22ebd279abdea1861b7daa833512ee4"
]
],
"content": "📅 Original date posted:2013-05-07\n📝 Original message:On Tue, May 7, 2013 at 2:28 PM, Gavin Andresen \u003cgavinandresen at gmail.com\u003ewrote:\n\n\u003e \"sweep private key\" is the missing functionality.\n\u003e\n\u003e I agree, it would be nice to have.\n\u003e\n\u003e\n\u003e On Tue, May 7, 2013 at 8:16 AM, Adam Back \u003cadam at cypherspace.org\u003e wrote:\n\u003e\n\u003e\u003e Hi\n\u003e\u003e\n\u003e\u003e Three minor security/other issues:\n\u003e\u003e\n\u003e\u003e 1. please a way to unlock the wallet without displaying wallet password in\n\u003e\u003e console screen (console unlock wallet, to import priv key); or\n\u003e\u003e\n\u003e\u003e 2. a button to import a private key (and option to transfer it to another\n\u003e\u003e key - if you are not the sole controller the private key)\n\u003e\u003e\n\u003e\u003e 3. a UX way to transfer BTC off a specific adress (eg choose from\n\u003e\u003e address), rather than having to spend the entire wallet onto a new\n\u003e\u003e address, just to get BTC off a specific address. Doing it that way has\n\u003e\u003e problems: creates more network traffic/bigger packets, higher fees (if\n\u003e\u003e any transactions are young/low confirmation), and generally damages\n\u003e\u003e privacy as all your funds end up linked.\n\u003e\u003e\n\u003e\nYes, sweep (send all the coins from this addresses to me) should certainly\nbe added. Maybe even a way to do it periodically, though but that would\nrequire remembering the key.\n\nImporting private keys into the wallet will not be added as a user-friendly\noption, as it is dangerous and potentially confusing.\n\nAs for (1), I think a better solution would to add a list of commands whose\narguments are censored in the console screen and command line history. At\nleast `importprivkey`, `walletpassphrase`, `walletpassphrasechange` should\nlikely be in that list.\n\nWladimir\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130507/ffc4c167/attachment.html\u003e",
"sig": "ee29a8216a6f2f8222cff223437d6806d6e7a9c40daaaed33646f220fe5bb2a3997cc239feb8f62e640994865ca5da0b108255a7a6a345ce49bfe06924dc3128"
}