📅 Original date posted:2013-02-25
📝 Original message:We've been toying with the idea of a 'dead' button, one that issues a bunch
of pre-generated txs sending stuff out to a previously secured 'backup' set
of addresses (we don't think in terms of wallets, just keypairs).
In this scenario, you have a long-term storage address (or set of them),
and if you need to hit the panic button, previously signed transactions
send value over to your emergency storage.
If you've mucked around sending / receiving with your long-term storage,
you'd only catch some BTC, not necessarily all, but what's nice is the
panic transaction leaking has lower security requirements than your private
keys -- worst case it's out, and you've got to deal with stuff in emergency
storage, as opposed to losing all your coins.
You could pair this with a server that checks if 'safe' addresses have
'unauthorized' transactions showing up on the blockchain, and you'd have a
reasonable automated security layer. Maybe. :)
I'm interested in thoughts on this approach as well.
Jorge -- I respectfully disagree with you, there are a number of enterprise
scenarios where your method is not appropriate.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130225/c4c50ba1/attachment.html>;
Peter Vessenes [ARCHIVE] /
npub1ez…6r8pt
2023-06-07 11:33:32
in reply to nevent1q…avr0
Author Public Key
npub1ezg54d03a7unwu0fckmlugxulukrg06x7jzx4engngxfg79sfcqsn6r8ptSeen on
wss://relay.nostr.bandPublished at
2023-06-07 11:33:32Event JSON
{
"id": "2cf1ce4156337785585f841d8ead48f5463305f05ec8f93434b5a1ee8fd9edcc",
"pubkey": "c8914ab5f1efb93771e9c5b7fe20dcff2c343f46f4846ae6689a0c9478b04e01",
"created_at": 1686137612,
"kind": 1,
"tags": [
[
"e",
"cce0717a6ddfead75394fb366d13e8af3af7500dd5dffd1a3544cbd8ac0ef60c",
"",
"root"
],
[
"e",
"cd306e620d81efe07631af041124ed85b4c8a001cf9a06f43317f64da544c4a8",
"",
"reply"
],
[
"p",
"498a711971f8a0194289aee037a4c481a99e731b5151724064973cc0e0b27c84"
]
],
"content": "📅 Original date posted:2013-02-25\n📝 Original message:We've been toying with the idea of a 'dead' button, one that issues a bunch\nof pre-generated txs sending stuff out to a previously secured 'backup' set\nof addresses (we don't think in terms of wallets, just keypairs).\n\nIn this scenario, you have a long-term storage address (or set of them),\nand if you need to hit the panic button, previously signed transactions\nsend value over to your emergency storage.\n\nIf you've mucked around sending / receiving with your long-term storage,\nyou'd only catch some BTC, not necessarily all, but what's nice is the\npanic transaction leaking has lower security requirements than your private\nkeys -- worst case it's out, and you've got to deal with stuff in emergency\nstorage, as opposed to losing all your coins.\n\nYou could pair this with a server that checks if 'safe' addresses have\n'unauthorized' transactions showing up on the blockchain, and you'd have a\nreasonable automated security layer. Maybe. :)\n\nI'm interested in thoughts on this approach as well.\n\nJorge -- I respectfully disagree with you, there are a number of enterprise\nscenarios where your method is not appropriate.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130225/c4c50ba1/attachment.html\u003e",
"sig": "cbe25dc19987004e8e72ee9c188587ea9345a828b0125f138b10efbe0873e2fecc208e36b83c0124678368b3deb09adeb067af57e27701bbee6674879bd5579f"
}