<oembed><type>rich</type><version>1.0</version><author_name>npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0n</author_name><author_url>https://nostr.ae/npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0n</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2016-08-04&#xA;📝 Original message:On Wednesday, August 03, 2016 6:16:20 PM Matthew Roberts via bitcoin-dev &#xA;wrote:&#xA;&gt; In light of the recent hack: what does everyone think of the idea of&#xA;&gt; creating a new address type that has a reversal key and settlement layer&#xA;&gt; that can be used to revoke transactions?&#xA;&#xA;This isn&#39;t something that makes sense at the address, since it represents the &#xA;recipient and not the sender. Transactions are not sent from addresses ever.&#xA;&#xA;&gt; You could specify so that transactions &#34;sent&#34; from these addresses must&#xA;&gt; receive N confirmations before they can&#39;t be revoked, after which the&#xA;&gt; transaction is &#34;settled&#34; and the coins become redeemable from their&#xA;&gt; destination output. A settlement phase would also mean that a transaction&#39;s&#xA;&gt; progress was publicly visible so transparent fraud prevention and auditing&#xA;&gt; would become possible by anyone.&#xA;&#xA;This is already possible. Just nLockTime your withdrawls for some future &#xA;block. Don&#39;t sign any transaction that isn&#39;t nLockTime&#39;d at least N blocks &#xA;beyond the present tip.&#xA;&#xA;Luke</html></oembed>