📅 Original date posted:2017-09-29
📝 Original message:On 09/29/2017 11:07 AM, Andrew Johnson wrote:
> One consideration of exposing this in QT is that it may encourage users
> to generate paper wallets(which are generally used and recommended for
> cold storage) from online machines, rendering them moreso lukewarm
> rather than cold, since the keys weren't generated in an air-gapped
> environment.
true that. Though there's nothing stopping a diligent person from
installing bitcoin-core on a dedicated offline machine. The blockchain
wouldn't need to be synced at all for key generation purposes.
> When using bitaddress.org <http://bitaddress.org>;
> locally(we /are /all only using it locally and not directly from the
> online webpage, right? ;) ) you've at least made the effort to seek out
> the repo, clone it locally, and use it on an offline machine and not
> retain any data from that session.
yeah, so I noticed this issue about Paper Wallet generation not being
possible with bitcoin-core exactly because I was recommending to a
non-technical user to use paper wallets, but then I also had to point
out that really bitaddress code should be downloaded, audited, etc,
before use. Things that are actually impossible for a non-technical user.
So I figured that instead I would make a simple script for them that
would use bitcoin-core to generate the addresses... and that's when it
dawned on me that it won't actually work with present day RPCs that are
all tied to internal wallet.
hence, this proposal.
> I'd suggest that any UI in QT include some sort of a modal dialog that
> informs the user that this is not a secure cold storage address unless
> it was created on an offline machine and printed on a non-networked
> printer, and the prompt must be accepted and dismissed before the wallet
> will provide the requested keys.
yes, agreed.
Dan Libby [ARCHIVE] /
npub1hm…jk43d
2023-06-07 18:06:40
in reply to nevent1q…hhmh
Author Public Key
npub1hm38d5dwxdq5zxlnv2qdfk3flecptqwl7g7u62ja0tr92d0hmrusejk43dPublished at
2023-06-07 18:06:40Event JSON
{
"id": "7ae10040f23383c43330df2a1b041cb3bb747c0b8fe7c263158bc40d22852f44",
"pubkey": "bee276d1ae3341411bf36280d4da29fe701581dff23dcd2a5d7ac65535f7d8f9",
"created_at": 1686161200,
"kind": 1,
"tags": [
[
"e",
"adbe104cdeb184e2b9ee2e7441c0306f637c427dfa72914e557b36050055e79e",
"",
"root"
],
[
"e",
"491bd36aa5b2ae7bae4bab17efa9dadc05ef11fb7282858d0593faeebe0fde38",
"",
"reply"
],
[
"p",
"fa69268781de33f116b423cab175d976820851d6b074d0873c920c6983eb4713"
]
],
"content": "📅 Original date posted:2017-09-29\n📝 Original message:On 09/29/2017 11:07 AM, Andrew Johnson wrote:\n\u003e One consideration of exposing this in QT is that it may encourage users\n\u003e to generate paper wallets(which are generally used and recommended for\n\u003e cold storage) from online machines, rendering them moreso lukewarm\n\u003e rather than cold, since the keys weren't generated in an air-gapped\n\u003e environment. \n\ntrue that. Though there's nothing stopping a diligent person from\ninstalling bitcoin-core on a dedicated offline machine. The blockchain\nwouldn't need to be synced at all for key generation purposes.\n\n\u003e When using bitaddress.org \u003chttp://bitaddress.org\u003e\n\u003e locally(we /are /all only using it locally and not directly from the\n\u003e online webpage, right? ;) ) you've at least made the effort to seek out\n\u003e the repo, clone it locally, and use it on an offline machine and not\n\u003e retain any data from that session.\n\nyeah, so I noticed this issue about Paper Wallet generation not being\npossible with bitcoin-core exactly because I was recommending to a\nnon-technical user to use paper wallets, but then I also had to point\nout that really bitaddress code should be downloaded, audited, etc,\nbefore use. Things that are actually impossible for a non-technical user.\n\nSo I figured that instead I would make a simple script for them that\nwould use bitcoin-core to generate the addresses... and that's when it\ndawned on me that it won't actually work with present day RPCs that are\nall tied to internal wallet.\n\nhence, this proposal.\n\n\u003e I'd suggest that any UI in QT include some sort of a modal dialog that\n\u003e informs the user that this is not a secure cold storage address unless\n\u003e it was created on an offline machine and printed on a non-networked\n\u003e printer, and the prompt must be accepted and dismissed before the wallet\n\u003e will provide the requested keys.\n\nyes, agreed.",
"sig": "4d86e5d146ce7416dc6575e4db9ea09de0673a808281d4f1808797270cba17b3c65f50363d6a3812baad04a2ee22407e370280ffeff00035678f0707c18fef22"
}