{"type":"rich","version":"1.0","author_name":"npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58","author_url":"https://nostr.ae/npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-07-15\n📝 Original message:Proxying another's idea, from CoinSummit.\n\nThe request:   It would be useful to limit the lifetime of a bitcoin\naddress.  Intentionally prevent (somehow) bitcoins being sent to a\npubkey/pkh after the key expires.\n\nYou could append \"don't [\"permit\"|confirm] after X [time|block]\"  to\nthe address I suppose.  The metadata would not be digitally signed,\nbut it would be hash-sealed.  As \"address\" is a client-side notion,\nwallet clients would be the ones enforcing such a rule.\n\nBitcoin protocol of course knows about keys, and key expiration is a\nwell known and useful concept in public key cryptography.  The best\ninsertion point in the protocol for key expiration is an open\nquestion, if it's even a good idea at that level at all.  Some flag\n\"no more TxOuts exactly like this [after X block?]\"?\n\nI readily admit I don't have good answers, but it does seem valuable IMO to\n* Prevent users from accidentally sending to an \"expired\" TxOut/pkh.\nThis happens in the field.\n* Discourage address reuse\n* Enable sites that generate lots of keys to rotate ancient keys off\ntheir core systems.  (HD wallets mitigate this)\n\n-- \nJeff Garzik\nBitcoin core developer and open source evangelist\nBitPay, Inc.      https://bitpay.com/"}