<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <updated></updated>
  <generator>https://nostr.ae</generator>

  <title>Nostr notes by </title>
  <author>
    <name></name>
  </author>
  <link rel="self" type="application/atom+xml" href="https://nostr.ae/npub1f3znre4hmn4ra7kwlmeu47mhelj3vwrxqjw8dt9cnl6qhuwvdwgsgepw6v.rss" />
  <link href="https://nostr.ae/npub1f3znre4hmn4ra7kwlmeu47mhelj3vwrxqjw8dt9cnl6qhuwvdwgsgepw6v" />
  <id>https://nostr.ae/npub1f3znre4hmn4ra7kwlmeu47mhelj3vwrxqjw8dt9cnl6qhuwvdwgsgepw6v</id>
  <icon></icon>
  <logo></logo>




  <entry>
    <id>https://nostr.ae/nevent1qqspn5z5jcwxteanrx3pyn7gwesnzu7phuvcp6jydh79xayzfy6kwkczypxy2v0xklww50h6eml08jhmwl87293cvczfca4vhz0lgzl3e34ez8j3xh6</id>
    
      <title type="html">📅 Original date posted:2021-03-06 📝 Original message:Hi, ...</title>
    
    <link rel="alternate" href="https://nostr.ae/nevent1qqspn5z5jcwxteanrx3pyn7gwesnzu7phuvcp6jydh79xayzfy6kwkczypxy2v0xklww50h6eml08jhmwl87293cvczfca4vhz0lgzl3e34ez8j3xh6" />
    <content type="html">
      In reply to &lt;a href=&#39;/nevent1qqswhsqra9mlsk7pdeu2vlaw5x0vv0v5z5ejz3p0ag9ycvcqqql2lhsll99z3&#39;&gt;nevent1q…99z3&lt;/a&gt;&lt;br/&gt;_________________________&lt;br/&gt;&lt;br/&gt;📅 Original date posted:2021-03-06&lt;br/&gt;📝 Original message:Hi,&lt;br/&gt;&lt;br/&gt;Given recent discussions around possible cracks to RSA, ECDSA and even sha256 we have been looking at possible options for hardening Bitcoin against those potential attack vectors. While most consider it a low priority, IMO it is better to discuss this issue than ignore it especially given recent developments. Possible solutions may not be quick to implement, test, deploy and prevention is better than the cure.&lt;br/&gt;&lt;br/&gt;We humbly present a few seeds of ideas which might be viable defenses. These are not deeply thought out at the technical level but may inspire some useful discussion for a few new BIPs.&lt;br/&gt;&lt;br/&gt;We have discussed these ideas in private before submitting to shake out weaknesses. We are aware that the ideas are challenging and probably contentious. We are not seeking didruption. The goal is to defeat potential attacks. Apologies if these ideas are not new and have already been dismissed.&lt;br/&gt;&lt;br/&gt;Possible defense strategies:&lt;br/&gt;&lt;br/&gt;1. Alternate hashing methods. Not sha256. Exposing them sooner rather than later to enable a smooth transition.&lt;br/&gt;&lt;br/&gt;2. Per address seed phrases. In addiition to mulitisig, segwit, P2SH, schnorr, taproot.&lt;br/&gt;&lt;br/&gt;3. Removing private keys from a wallet for safe storage in a seperate location.&lt;br/&gt;&lt;br/&gt;4. Completely removing wallets from the blockchain for &amp;#39;absolute&amp;#39; cold storage*. If possible there would no longer be any trace of the wallet or associated addresses. Possibly in combination with the next suggestion.&lt;br/&gt;&lt;br/&gt;- Bonus for general maintenance.&lt;br/&gt;&lt;br/&gt;5. Burning old coins and generating &amp;#39;new&amp;#39; coins to &amp;#39;reset&amp;#39; tx history.&lt;br/&gt;&lt;br/&gt;A &amp;#39;Burn and Reissue&amp;#39; FIFO queue with set miner fees. Satoshis submitted to the queue are permanently &amp;#39;disabled and no longer in use. Replacement satoshis are added to new blocks and distributed by queue priority. Suggest a set fee to avoid excessively high processessing fees and/or getting stuck in the queue.&lt;br/&gt;&lt;br/&gt;* We realise this would require some significant changes that may not be technically possible.&lt;br/&gt;&lt;br/&gt;--&lt;br/&gt;Patrick Shirkey&lt;br/&gt;-------------- next part --------------&lt;br/&gt;An HTML attachment was scrubbed...&lt;br/&gt;URL: &amp;lt;&lt;a href=&#34;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20210306/cb59c212/attachment.html&amp;gt&#34;&gt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20210306/cb59c212/attachment.html&amp;gt&lt;/a&gt;;
    </content>
    <updated>2023-06-07T18:30:38Z</updated>
  </entry>

  <entry>
    <id>https://nostr.ae/nevent1qqsvdvhp6u3gpwdz2lxf2692vqanmf40x3mf5cdt38mrj7krg28gkzczypxy2v0xklww50h6eml08jhmwl87293cvczfca4vhz0lgzl3e34ezxnrj93</id>
    
      <title type="html">📅 Original date posted:2016-03-03 📝 Original message:On ...</title>
    
    <link rel="alternate" href="https://nostr.ae/nevent1qqsvdvhp6u3gpwdz2lxf2692vqanmf40x3mf5cdt38mrj7krg28gkzczypxy2v0xklww50h6eml08jhmwl87293cvczfca4vhz0lgzl3e34ezxnrj93" />
    <content type="html">
      In reply to &lt;a href=&#39;/nevent1qqsqmqluc85fxnxw3zqygfe4ct7zqam92um7v8wtvqgllhyvz0jzwhc0juz3h&#39;&gt;nevent1q…uz3h&lt;/a&gt;&lt;br/&gt;_________________________&lt;br/&gt;&lt;br/&gt;📅 Original date posted:2016-03-03&lt;br/&gt;📝 Original message:On Thu, March 3, 2016 10:02 am, Peter Todd via bitcoin-dev wrote:&lt;br/&gt;&amp;gt; On Wed, Mar 02, 2016 at 11:01:36AM -0800, Eric Voskuil via bitcoin-dev&lt;br/&gt;&amp;gt; wrote:&lt;br/&gt;&amp;gt;&amp;gt; &amp;gt; A 6 month investment with 3 months on the high subsidy and 3 months on&lt;br/&gt;&amp;gt;&amp;gt; low subsidy would not be madeâ€¦&lt;br/&gt;&amp;gt;&amp;gt;&lt;br/&gt;&amp;gt;&amp;gt;&lt;br/&gt;&amp;gt;&amp;gt;&lt;br/&gt;&amp;gt;&amp;gt; Yes, this is the essential point. All capital investments are made based&lt;br/&gt;&amp;gt;&amp;gt; on expectations of future returns. To the extent that futures are&lt;br/&gt;&amp;gt;&amp;gt; perfectly knowable, they can be perfectly factored in. This is why&lt;br/&gt;&amp;gt;&amp;gt; inflation in Bitcoin is not a tax, itâ€™s a cost. These step functions&lt;br/&gt;&amp;gt;&amp;gt; are made continuous by their predictability, removing that&lt;br/&gt;&amp;gt;&amp;gt; predictability will make them -- unpredictable.&lt;br/&gt;&amp;gt;&lt;br/&gt;&amp;gt; You know, I do agree with you.&lt;br/&gt;&amp;gt;&lt;br/&gt;&amp;gt; But see, this is one of the reasons why we keep reminding people that&lt;br/&gt;&amp;gt; strictly speaking a hardfork *is* an altcoin, and the altcoin can change&lt;br/&gt;&amp;gt; any rule currently in Bitcoin.&lt;br/&gt;&amp;gt;&lt;br/&gt;&amp;gt; It&amp;#39;d be perfectly reasonable to create an altcoin with a 22-million-coin&lt;br/&gt;&amp;gt; limit and an inflation schedule that had smooth, rather than abrupt,&lt;br/&gt;&amp;gt; drops. It&amp;#39;d also be reasonable to make that altcoin start with the same&lt;br/&gt;&amp;gt; UTXO set as Bitcoin as a means of initial coin distribution.&lt;br/&gt;&amp;gt;&lt;br/&gt;&amp;gt; If miners choose to start mining that altcoin en-mass on the halving,&lt;br/&gt;&amp;gt; all the more power to them. It&amp;#39;s our choice whether or not we buy those&lt;br/&gt;&amp;gt; coins. We may choose not to, but if 95% of the hashing power decides to&lt;br/&gt;&amp;gt; go mine something different we have to accept that under our current&lt;br/&gt;&amp;gt; chosen rules confirmations might take a long time.&lt;br/&gt;&amp;gt;&lt;br/&gt;&amp;gt;&lt;br/&gt;&amp;gt; Of course, personally I agree with Gregory Maxwell: this is all fairly&lt;br/&gt;&amp;gt; unlikely to happen, so the discussion is academic. But we&amp;#39;ll see.&lt;br/&gt;&amp;gt;&lt;br/&gt;&lt;br/&gt;Bitcoin is a success.&lt;br/&gt;&lt;br/&gt;The success has forced various hardfork discussions.&lt;br/&gt;&lt;br/&gt;Hard forking is contentious. If a softfork cannot be achieved the&lt;br/&gt;alternate to a hardfork is creating a new bitcoin. ex bitcoin 2.0&lt;br/&gt;&lt;br/&gt;Similar to silver, gold, palladium, etc...&lt;br/&gt;&lt;br/&gt;Bitcoins success partly stems from it&amp;#39;s brand awareness. Any new&lt;br/&gt;officially supported bitcoin will also benefit from this brand awareness.&lt;br/&gt;&lt;br/&gt;If the market values the new improved bitcoin they will put their money&lt;br/&gt;into it. This doesn&amp;#39;t require any consensus.&lt;br/&gt;&lt;br/&gt;Let the market decide which option has the most value. If everyone&lt;br/&gt;switches to the new bitcoin then the old bitcoin miners will follow.&lt;br/&gt;&lt;br/&gt;&lt;br/&gt;&lt;br/&gt;&lt;br/&gt;&lt;br/&gt;--&lt;br/&gt;Patrick Shirkey&lt;br/&gt;Boost Hardware Ltd
    </content>
    <updated>2023-06-07T17:49:31Z</updated>
  </entry>

</feed>