<?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/npub1j4q6lu9mw575kqkz46erzesmr5hyaw4runlgugz9nwr9erxg4n3s643z8m.rss" />
  <link href="https://nostr.ae/npub1j4q6lu9mw575kqkz46erzesmr5hyaw4runlgugz9nwr9erxg4n3s643z8m" />
  <id>https://nostr.ae/npub1j4q6lu9mw575kqkz46erzesmr5hyaw4runlgugz9nwr9erxg4n3s643z8m</id>
  <icon></icon>
  <logo></logo>




  <entry>
    <id>https://nostr.ae/nevent1qqsqmk2y4zeuqweq30e0gaem8lprgvhg9rwu6cwkjx8y2r9euafe5tgzyz25rtlshd6n6jczc2htyvtxrvwjun4650j0ar3qgkdcvhyvezkwx75s5q4</id>
    
      <title type="html">📅 Original date posted:2022-08-20 📝 Original message:Great ...</title>
    
    <link rel="alternate" href="https://nostr.ae/nevent1qqsqmk2y4zeuqweq30e0gaem8lprgvhg9rwu6cwkjx8y2r9euafe5tgzyz25rtlshd6n6jczc2htyvtxrvwjun4650j0ar3qgkdcvhyvezkwx75s5q4" />
    <content type="html">
      In reply to &lt;a href=&#39;/nevent1qqsw06cdvkzug73drsy4tk3l8huy449fjwz89ad6kezfr93h3znfuhgxc0qx3&#39;&gt;nevent1q…0qx3&lt;/a&gt;&lt;br/&gt;_________________________&lt;br/&gt;&lt;br/&gt;📅 Original date posted:2022-08-20&lt;br/&gt;📝 Original message:Great to see an implementation of the idea.&lt;br/&gt;&lt;br/&gt;Maybe I misunderstand, but isn&amp;#39;t there a vulnerability of denial of service here?&lt;br/&gt;&lt;br/&gt;A user who registers one input will receive the round secret identifier, and this is all the information required for output registration. However, that malicious user can now register multiple outputs, providing the same secret, and nobody can link the malicious outputs to any specific input. Therefor there cannot be a blame round where the malicious input is removed, and thus there can be a ongoing free denial of service attack without attribution or defense.&lt;br/&gt;&lt;br/&gt;Skol&lt;br/&gt;Max&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/20220820/ed6040a1/attachment.html&amp;gt&#34;&gt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20220820/ed6040a1/attachment.html&amp;gt&lt;/a&gt;;&lt;br/&gt;-------------- next part --------------&lt;br/&gt;A non-text attachment was scrubbed...&lt;br/&gt;Name: sender_key.asc&lt;br/&gt;Type: application/pgp-keys&lt;br/&gt;Size: 3910 bytes&lt;br/&gt;Desc: not available&lt;br/&gt;URL: &amp;lt;&lt;a href=&#34;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20220820/ed6040a1/attachment.bin&amp;gt&#34;&gt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20220820/ed6040a1/attachment.bin&amp;gt&lt;/a&gt;;
    </content>
    <updated>2023-06-07T23:12:56Z</updated>
  </entry>

  <entry>
    <id>https://nostr.ae/nevent1qqs2daeupav9n0n0flvnvg7qmdxxnxjzykk52c8ktkexmzfhrc9587czyz25rtlshd6n6jczc2htyvtxrvwjun4650j0ar3qgkdcvhyvezkwxdvaj55</id>
    
      <title type="html">📅 Original date posted:2022-03-01 📝 Original message:Hello ...</title>
    
    <link rel="alternate" href="https://nostr.ae/nevent1qqs2daeupav9n0n0flvnvg7qmdxxnxjzykk52c8ktkexmzfhrc9587czyz25rtlshd6n6jczc2htyvtxrvwjun4650j0ar3qgkdcvhyvezkwxdvaj55" />
    <content type="html">
      In reply to &lt;a href=&#39;/nevent1qqsv358pwmsktz2k4pg4te4nkl93y4xl6w9j5q3mk07glrn69eyy04g5djqvs&#39;&gt;nevent1q…jqvs&lt;/a&gt;&lt;br/&gt;_________________________&lt;br/&gt;&lt;br/&gt;📅 Original date posted:2022-03-01&lt;br/&gt;📝 Original message:Hello list,&lt;br/&gt;&lt;br/&gt;tl;dr: we have been working on a little something, and Wasabi 2.0 is now &lt;br/&gt;ready for your review and feedback.&lt;br/&gt;&lt;br/&gt;Wasabi Wallet 2.0 is a Bitcoin wallet providing effortless privacy for &lt;br/&gt;its users. Just like Wasabi 1.0, this is achieved by default on the &lt;br/&gt;network layer with a deep Tor integration, and on the synchronization &lt;br/&gt;layer with BIP158 block filters or the packaged Bitcoin full node. &lt;br/&gt;However, 2.0 upgrades the privacy on the blockchain layer with a new &lt;br/&gt;Wabisabi coinjoin implementation, running by default in the background.&lt;br/&gt;&lt;br/&gt;Wabisabi is a drop-in replacement for the ZeroLink coinjoin coordination &lt;br/&gt;protocol. Instead of Chaumian [or Schnorr] blind signatures, it uses &lt;br/&gt;keyed verified anonymous credentials and Pedersen commitments. This &lt;br/&gt;enables anonymous DoS protection for centrally coordinated coinjoins &lt;br/&gt;without relying on equal amount outputs. This flexibility in the &lt;br/&gt;coordination enables a more sophisticated amount decomposition, &lt;br/&gt;specifically with standard denominations of low Hamming weight, in our &lt;br/&gt;case powers of two, powers of three, and the preferred value series [1, &lt;br/&gt;2, 5]. In our simulations, this results often in &amp;#34;changeless&amp;#34; coinjoins &lt;br/&gt;[all outputs at least two anonymity set, aka count of equal value &lt;br/&gt;outputs] for transactions with more than 50 inputs. Whereas in Wasabi &lt;br/&gt;1.0 each user had to participate in the smallest standard denomination &lt;br/&gt;of 0.1 btc, now there is no mandatory output decomposition, and the &lt;br/&gt;minimum amount is 5000 sats. This is **substantial** block space &lt;br/&gt;savings, reducing the amount of mining fees paid, and the time until the &lt;br/&gt;user&amp;#39;s utxo set is private.&lt;br/&gt;&lt;br/&gt;Thanks to these efficiency improvements, we are now comformaking &lt;br/&gt;coinjoin transactions the default in Wasabi&amp;#39;s UX. As soon as bitcoin is &lt;br/&gt;received in the wallet, the client will register the confirmed coin as &lt;br/&gt;input for the PSBT with the backend coordinator. Within a couple hours, &lt;br/&gt;the user has numerous utxos which can be spent privately without &lt;br/&gt;revealing their pre-mix transaction history. The resulting UX is simple: &lt;br/&gt;receive, wait, spend. Privately. Effortless. For everyone.&lt;br/&gt;&lt;br/&gt;Whenever the user wants to spend bitcoin to an address, the wallet &lt;br/&gt;automatically selects those private coins with sufficient sats, coin &lt;br/&gt;control is displayed to the user. However, when the private balance is &lt;br/&gt;insufficient to make the payment, the user has the option to adjust the &lt;br/&gt;coin selection with the help of the previously provided contact labels. &lt;br/&gt;Since labeling is mandatory in Wasabi, we can abstract away the utxo &lt;br/&gt;concept and display only the contact labels for the users to choose &lt;br/&gt;from. Wasabi also suggests the user to slightly adjust the payment &lt;br/&gt;amount so as to avoid the creation of a change utxo, decreasing fees and &lt;br/&gt;improving future privacy.&lt;br/&gt;&lt;br/&gt;Today, we are proud to finally reveal our work in progress in a public &lt;br/&gt;preview release with coinjoin on testnet. We kindly ask for your help &lt;br/&gt;testing the completely new UI/UX, reviewing the cryptography and &lt;br/&gt;coordination protocol, and especially coinjoining to analyze the &lt;br/&gt;resulting transaction graph in the wild.&lt;br/&gt;&lt;br/&gt;Thank you to all contributors past and present!&lt;br/&gt;&lt;br/&gt;Skol&lt;br/&gt;Max Hillebrand&lt;br/&gt;&lt;br/&gt;Download the testnet release: &lt;br/&gt;&lt;a href=&#34;https://github.com/zkSNACKs/WalletWasabi/releases/tag/v1.98.0.0&#34;&gt;https://github.com/zkSNACKs/WalletWasabi/releases/tag/v1.98.0.0&lt;/a&gt;&lt;br/&gt;&lt;br/&gt;Website: &lt;a href=&#34;https://wasabiwallet.io&#34;&gt;https://wasabiwallet.io&lt;/a&gt;&lt;br/&gt;Onion: &lt;a href=&#34;http://wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion&#34;&gt;http://wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion&lt;/a&gt;&lt;br/&gt;Testnet coordinator: &lt;br/&gt;&lt;a href=&#34;http://testwnp3fugjln6vh5vpj7mvq3lkqqwjj3c2aafyu7laxz42kgwh2rad.onion&#34;&gt;http://testwnp3fugjln6vh5vpj7mvq3lkqqwjj3c2aafyu7laxz42kgwh2rad.onion&lt;/a&gt;
    </content>
    <updated>2023-06-07T23:05:06Z</updated>
  </entry>

</feed>