2024-04-21T03:18:46Z https://njump.cloud.vinney.xyz conduition https://njump.cloud.vinney.xyz/npub1l6uy9chxyn943cmylrmukd3uqdq8h623nt2gxfh4rruhdv64zpvsx6zvtg https://m.primal.net/Hfmb.png https://m.primal.net/Hfmb.png https://njump.cloud.vinney.xyz/nevent1qqsz70vqv604jts224szk6fv4s7x6ljz8jv0whghepl6ea0z46l2rnszyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9j79yfpe Brink is funding my PQ research! <br/><br/><a href="https://conduition.io/bitcoin/my-first-grant/">https://conduition.io/bitcoin/my-first-grant/</a> 2026-06-03T20:03:44Z https://njump.cloud.vinney.xyz/nevent1qqszyc3u92gkldp52kv6cgaztj88mjmkqjy6t2cv6qmddjzn0kudvwczyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9jyda4ug If we someday want to replace quantum-vulnerable ECC, we want something compact, flexible and fast. Isogenies seem like the only candidate so far: 66 byte pubkeys, 148 byte sigs. I wrote a thing explaining isogenies, aimed at people who already know ECC.<br/><br/><a href="https://conduition.io/cryptography/isogenies-intro/">https://conduition.io/cryptography/isogenies-intro/</a> 2026-03-18T15:53:56Z https://njump.cloud.vinney.xyz/nevent1qqstjjv287m027lvc4s7rx97kshlv2gfe2em0686qqketyhvwd038tczyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9j5afy04 In reply to <a href='/nevent1qqs9xmzawgsk4m53csnrhqcs2smjvsck5rjnlvr6mhwacutzfnhq47g3du5pu'>nevent1q…u5pu</a><br/>_________________________<br/><br/>I definitely agree, taproot approach is much better. I updated my post to point to yours. DASK is neat but I don&#39;t think we need to be that fancy, and your Taproot approach is more soft-fork friendly. <br/><br/>I do still think using a lighter-weight signature scheme like WOTS for certification would be better and more future proof than committing directly to SPHINCS right now.<br/><br/>If we do end up wanting to use SPHINCS in 20-30 years, it&#39;d still be an option: Just enforce that the WOTS key must sign a SPHINCS pubkey, and verify everything else against the certified SPHINCS key. That would only add a kilobyte to the already-huge SPHINCS signature data.<br/><br/>Think of it this way: if you&#39;re correct and this is just an edgecase fallback opcode that only a few people ever end up using, then do we really want the huge kitchen-sink of bringing SPHINCS into the bitcoin consensus layer, just for it to be barely ever used? <br/><br/>On the other hand, if this PQ fallback opcode is used a LOT, then we stand to save a LOT of witness space by biding our time and seeing where the cards fall on the landscape of many-time post-quantum signatures, rather than committing to huge SPHINCS signatures today. 2024-12-17T03:35:18Z https://njump.cloud.vinney.xyz/nevent1qqspw26e2323q7dfq5px96va2wd3f6e7tq0w9dxdejmg2mpu3d9y2qczyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9j86nqwx In reply to <a href='/nevent1qqs8npvsl804k0qrzcvncdgydy3rfu2gkg4u6kfnz6qnx86jfqwrkygmepc79'>nevent1q…pc79</a><br/>_________________________<br/><br/>Hey <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub185h9z5yxn8uc7retm0n6gkm88358lejzparxms5kmy9epr236k2qcswrdp" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>matt</span> (<span class="italic">npub185h…wrdp</span>)</a></span>, I can&#39;t reply on google groups but you should check out my article on hash-based signatures and my DASK proposal, it&#39;s very similar to your idea, in the way clients can opt into future quantum resistance without any consensus changes. <br/><br/><a href="https://conduition.io/cryptography/quantum-hbs/#Upgrading-Bitcoin">https://conduition.io/cryptography/quantum-hbs/#Upgrading-Bitcoin</a><br/><br/>I chose a different mechanism for my approach. Instead of an opcode in a tapscript leaf, DASK uses a PQ signature scheme pubkey as an secp256k1 secret key, and assumes future PQ bitcoin clients will validate against that PQ pubkey.<br/><br/>I think your proposal has a major benefit over mine in that it makes soft-fork compliance way easier. My DASK idea seems like it would need a hard fork on Q-Day, but yours would seem to be fully compatible with old clients. Big props 🎉 <br/><br/>One idea from my post which I think you might want to consider copying is: Instead of committing to a SPHINCS key on-chain, commit to a hash-based certification key with shorter signatures, like WOTS.<br/><br/>Yes, it&#39;s a one-time signature scheme so we can&#39;t reuse the key, but we can be pretty sure than post-quantum cryptography will progress a long way in the coming decades, and we can use that one-time signature (which we are highly confident is secure today) to endorse a post-quantum key for a signature algorithm that might not exist yet, or that might exist today but that we don&#39;t know is secure, like Kyber. <br/><br/>Your opcode soft-fork would have to specify the exact validation semantics later, but the WOTS authentication key has already been committed to, so the coins are safe. 2024-12-16T03:02:15Z https://njump.cloud.vinney.xyz/nevent1qqs8l6wt03mxjdtcxxgd5k7mll8zfqffjva7znj46ajk7gzavwm8n9szyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9jxj2ueh What&#39;s amazing to me is that despite crossing into six figures of USD per bitcoin, median on-chain transaction fees are still at single-digit sats-per-byte rates. 2024-12-05T04:09:44Z https://njump.cloud.vinney.xyz/nevent1qqsxquu703aee8gu8tlvkpy6savgz7vkv7ytrzmrja9vdpu4r9luntgzyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9jkhfxuw $100k Bitcoin guys and girls. Inevitability makes it no less awe inspiring. Clever purposeful dev teams are the reason why it happened. When people ask me why i&#39;m so confident in Bitcoin, I say it&#39;s because i know how many brilliant minds are actively working out the kinks and making Bitcoin practical. With so much 🧠 power we can&#39;t help but succeed at least a little bit.<br/><br/>Anyways, tick tock next block, I&#39;ll see you tomorrow internet. 2024-12-05T03:55:04Z https://njump.cloud.vinney.xyz/nevent1qqs89e4eq07p65f7dpmt0w9newdl57d5h2nhku9l63krwctlzra3mnqzyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9jmnzvqn In reply to <a href='/nevent1qqsydzkd9rr3svt85n3g3gc2ayw8u9l002jvvqt0rqeqacy4vj2krvsed05fr'>nevent1q…05fr</a><br/>_________________________<br/><br/> <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub1vadcfln4ugt2h9ruwsuwu5vu5am4xaka7pw6m7axy79aqyhp6u5q9knuu7" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>waxwing</span> (<span class="italic">npub1vad…nuu7</span>)</a></span> I got the proving time for the PTLC/HTLC bridging (AKA discrete log is preimage) down to 20 seconds with RISC0. Fast enough to be viable in some real applications i think! <br/><br/>I&#39;m polishing the code up now. Would you be interested in participating in a real-world PTLC/HTLC bridge test? 2024-11-11T17:38:22Z https://njump.cloud.vinney.xyz/nevent1qqs0ddjp6vfmgpz2l2dshadzlchx9h08egcrmhle32fk8u90t54c35szyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9jkxpe3z In reply to <a href='/nevent1qqs0ep57auv4va2qzdh30q4n3vu0cqyfwtxt5cnhtjs24kr80mrhf4ch3nc79'>nevent1q…nc79</a><br/>_________________________<br/><br/>Article fixed, now I&#39;m assuming transparent setup ZKPs only (e.g. STARKs). Thanks for pointing this out 😄 2024-11-03T07:23:19Z https://njump.cloud.vinney.xyz/nevent1qqsfh43d3qhsu7jfw7rn4nj7wssl7cv5kc08pwl9ffgjxmkjf9qwplszyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9jdzuyar In reply to <a href='/nevent1qqs0qxa05eg3fq6qf0upq3ntxghdfqxey3r35hq2ec4ahyhpy7gvlgcq3fz8r'>nevent1q…fz8r</a><br/>_________________________<br/><br/>Great catch, thank you! Will fix this 2024-11-03T06:09:08Z https://njump.cloud.vinney.xyz/nevent1qqsydzkd9rr3svt85n3g3gc2ayw8u9l002jvvqt0rqeqacy4vj2krvszyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9jlvw9cw In reply to <a href='/nevent1qqs0ep57auv4va2qzdh30q4n3vu0cqyfwtxt5cnhtjs24kr80mrhf4ch3nc79'>nevent1q…nc79</a><br/>_________________________<br/><br/>ahah! I was sure someone must&#39;ve thought of this idea before me, but I didn&#39;t have the right search terms. &#34;ZKCP&#34;. This is great background reading, thank you <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub1vadcfln4ugt2h9ruwsuwu5vu5am4xaka7pw6m7axy79aqyhp6u5q9knuu7" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>waxwing</span> (<span class="italic">npub1vad…nuu7</span>)</a></span>! <br/><br/>Interesting to learn that the SNARK setup is more sensitive than I had thought. I&#39;ll be sure to correct my article to reference the original idea and fix the flaw which I unwittingly duplicated.<br/><br/>As for performance, so far I&#39;ve only tested the PTLC-bridging program here shown in this section: <a href="https://conduition.io/bitcoin/zkpreimage/#Optimizing">https://conduition.io/bitcoin/zkpreimage/#Optimizing</a><br/><br/>With that, it took 3 minutes to generate a proof with the RISC0 STARK prover. Not great but also not completely impractical. I&#39;d like to test other prover programs too 2024-11-03T06:03:00Z https://njump.cloud.vinney.xyz/nevent1qqsqac2p53vg3w3k873nxkhsn9plqydf9uuk0u0txyrzq4wdzpzrq5gzyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9j6gy5q3 &#34;Sell me this preimage.&#34;<br/><br/>You can verifiably purchase the solution to any NP-Complete problem using Bitcoin (and Lightning), combined with zero-knowledge proofs. <br/><br/>- Buy the solution to a sudoku puzzle<br/>- Buy the prime factors of an RSA key<br/>- Bridge HTLCs with PTLCs<br/>- Buy a valid proof-of-work<br/>- and more...<br/><br/><a href="https://conduition.io/bitcoin/zkpreimage/">https://conduition.io/bitcoin/zkpreimage/</a> 2024-11-02T21:59:25Z https://njump.cloud.vinney.xyz/nevent1qqszdl6n5c67sgf44jv6k7kmmlnjyp56tm9407ez2vle0n3ay8hqhsgzyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9jxy9dr5 In reply to <a href='/nevent1qqswaw52rx25ye256cvf8jn3ad3vays69xqk7pqqmhkd5qkf3z0sp0ssw705x'>nevent1q…705x</a><br/>_________________________<br/><br/>That&#39;s completely true! The transition to PQ crypto is a slow march across all digital industries. I know for sure OpenSSH is actively working on this. <a href="https://linuxiac.com/openssh-9-9-released/">https://linuxiac.com/openssh-9-9-released/</a><br/><br/>The most important part of the overall migration IMO will be TLS. Almost all TLS traffic today is basically plaintext to a quantum computer (incl passwords sent to log into online services, and access keys downloaded over TLS). Cloudflare has a good post about that here: <a href="https://blog.cloudflare.com/pq-2024/">https://blog.cloudflare.com/pq-2024/</a> 2024-10-23T14:13:28Z https://njump.cloud.vinney.xyz/nevent1qqs0enajwn5r4uzfpa0kflwuejk92k6yj46l6dh0ayzvws9wa08dkyczyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9jjyvcdc In reply to <a href='/nevent1qqsvgh78xaxsc69us0axadwgxwmrge3kpyx37anv0j2uk9ekthfn3xce5c57v'>nevent1q…c57v</a><br/>_________________________<br/><br/>First time for me hearing of Dark Skippy, but it sounds like a pretty obvious idea: Malicious firmware causes compromise of hardware wallets. That idea applies to pre and post quantum signatures of any algorithm. 2024-10-22T23:26:05Z https://njump.cloud.vinney.xyz/nevent1qqsx9hn8x95zarwefv7evvqq5vxndcx9ulquukpwe4axudutfml6g5szyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9j55lvzt I went on a deep dive into post-quantum hash-based signatures and tried to apply them to bitcoin. At the end of the article I propose a way to insure today&#39;s Bitcoin wallets with a quantum-resistant fallback key, without any consensus changes needed.<br/><br/><a href="https://conduition.io/cryptography/quantum-hbs/">https://conduition.io/cryptography/quantum-hbs/</a><br/> 2024-10-22T20:02:20Z https://njump.cloud.vinney.xyz/nevent1qqsg0zahx3ryrdq2n9ntlv5erzw2d7ankgyvu3n3gm8vgnxl0zfh8vczyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9j4pvugc In reply to <a href='/nevent1qqsg5d2m9vgdj80rtyurjqsm6mf7at0w9tnk58a5s72ms4u928e9hrqpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgn0pnpn'>nevent1q…pnpn</a><br/>_________________________<br/><br/>Just sent you a few sats to test, seems like it&#39;s working 2024-10-10T04:53:25Z https://njump.cloud.vinney.xyz/nevent1qqsy4d5gu5gg7vnsljkr5360sysclmannlmy2x39wmzzhlvhz84xjtczyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9j08e6sw In reply to <a href='/nevent1qqsg5d2m9vgdj80rtyurjqsm6mf7at0w9tnk58a5s72ms4u928e9hrqpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgn0pnpn'>nevent1q…pnpn</a><br/>_________________________<br/><br/> <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub1vwldp9k95xxe9mgnzakykpmhmazj5q2veldt6jvju2dvrfkxvlaq6dzfhz" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>fredix</span> (<span class="italic">npub1vwl…zfhz</span>)</a></span> That&#39;s because LNURL specifies that the min/max sendable fields in the LNURL response are in millisatoshis (thousands of a sat). 1000 msat = 1 sat, so everything should be working correctly for you there 😎 2024-10-10T04:39:37Z https://njump.cloud.vinney.xyz/nevent1qqsrqjs08kcwkj8k2uqutg5ufuxdnxch24xs530hmnxlh9ph0qyzknczyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9jw5trhk In reply to <a href='/nevent1qqsqzfurhax0mm7z84jwpdqampjt49aqhdz53m9ky2p0ry939t3kt3gqhju7p'>nevent1q…ju7p</a><br/>_________________________<br/><br/>I agree about the DoS and scaling risks for websockets. Publishing data about spent proofs intermittently sounds more realistic to me, but I don&#39;t see any point in using Nostr to do that. A cashu mint is itself an always-on server already. What is gained by pushing that data to other people&#39;s servers besides offloading the DoS/scaling problems onto someone else? Instead the mint should just make that data available directly to clients via a new API endpoint.<br/><br/>Publishing one data point per spent proof wouldn&#39;t scale well - the mint needs some kind of accumulator or filter which compresses the information about spent proofs while allowing client-side validation. This seems like a use-case for Golomb-Coded sets (GCS), as used in BIP158 compact filters. <br/><br/><a href="https://github.com/bitcoin/bips/blob/master/bip-0158.mediawiki">https://github.com/bitcoin/bips/blob/master/bip-0158.mediawiki</a><br/><br/>The mint computes a GCS which compresses all proofs spent recently, and updates the filter regularly. If the mint keeps the GCS hash representations sorted in memory, it could easily perform this update atomically for every single swap/melt without much of a performance hit (it&#39;d be O(log n) insertion complexity).<br/><br/>If the filter gets too big, the mint compresses and archives it, and starts building a new one from scratch, or else evicts older GCS members (spent proofs) with a FIFO queue. <br/><br/>Clients can download and check the compact GCS filter at any time to see if their proofs have been spent recently, without revealing which ecash notes they&#39;re curious about. There&#39;s a chance for false positives but no chance of false negatives, so you might think your token was spent when it wasn&#39;t, but if your token was spent you&#39;ll always know about it. 2024-10-10T04:34:51Z https://njump.cloud.vinney.xyz/nevent1qqsfh87xkd7gu3r04jpe6x49axm6pjksg2pqfvgdezuryrmvd0yvrjszyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9jldwmug I just realized my lnaddrd server was configured not to accept zaps less than 500 sats... sorry to anyone who was trying to zap me on nostr for the past few months, i&#39;m not that greedy, i swear!<br/><blockquote class="border-l-05rem border-l-strongpink border-solid"><div class="-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2">quoting <br/><span itemprop="mentions" itemscope itemtype="https://schema.org/Article"><a itemprop="url" href="/note1c4pa7a3jqzhf078msmsy7j3uyduegde967nhqr3e7nyvpj7xc3jqscwl64" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">note1c4p…wl64</a></span> </div> I made a self-hosted Lightning Address webserver, because for some reason I couldn't find any good ones out there already.<br/><br/><a href="https://github.com/conduition/lnaddrd">https://github.com/conduition/lnaddrd</a><br/><br/>This is what powers my snazzy new `conduition@conduition.io` LN address 😇 </blockquote> 2024-10-03T17:56:34Z https://njump.cloud.vinney.xyz/nevent1qqsr7gffzlnmhlma7dyysv5v020luzkmgzn8ncwl6xv57rvewq5ww5gzyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9j8l5up5 In reply to <a href='/nevent1qqsqqqyse7jzswkcgwjdsx5vtdt4flwa0kkun4q2s48lvxhfkppuz8ctg4mwh'>nevent1q…4mwh</a><br/>_________________________<br/><br/> <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub10vlhsqm4qar0g42p8g3plqyktmktd8hnprew45w638xzezgja95qapsp42" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>jimmysong</span> (<span class="italic">npub10vl…sp42</span>)</a></span>&#39;s reply below is correct, FROST with trusted dealer would solve your use-case here. <br/><br/>Of course <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub1vadcfln4ugt2h9ruwsuwu5vu5am4xaka7pw6m7axy79aqyhp6u5q9knuu7" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>waxwing</span> (<span class="italic">npub1vad…nuu7</span>)</a></span>&#39;s point is also valid: If you want true multisig security you&#39;d need to be certain that you securely erase the distributed shares on your machine afterwards, and of course erase the original secret key (except for maybe keeping a paper backup). Still, it&#39;s a valid approach if you are OK with those assumptions.<br/><br/>I&#39;m currently working on a BIP340 compatibility pull request into the ZCashFoundation&#39;s FROST implementation (Rust), I believe it should work to produce valid Nostr sigs.<br/><br/><a href="https://github.com/ZcashFoundation/frost/pull/730">https://github.com/ZcashFoundation/frost/pull/730</a><br/><br/>If you use a python stack, check out <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub1tr7ndmjkguzupvqhn9clasx4r08q2sklhal4g60844nsnnalw0tqpwnc05" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>jesseposner</span> (<span class="italic">npub1tr7…nc05</span>)</a></span>&#39;s FROST implementation here<br/><br/><a href="https://github.com/jesseposner/FROST-BIP340">https://github.com/jesseposner/FROST-BIP340</a><br/><br/> <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub160t5zfxalddaccdc7xx30sentwa5lrr3rq4rtm38x99ynf8t0vwsvzyjc9" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>average_gary</span> (<span class="italic">npub160t…yjc9</span>)</a></span> linked to my FROST BYOK article but that would only be practical if you wanted to create a joint key from existing (static) npubs. I don&#39;t think it&#39;s useful for splitting an existing key.<br/><br/> 2024-10-03T15:47:44Z https://njump.cloud.vinney.xyz/nevent1qqs09cj08smgnf8ayqzuk9a524qekepy7jcf4r3tdywnvl2m8tn74uczyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9ju2kw93 I&#39;m very happy to see these vulnerabilities fixed in a timely fashion, but Mercury went public releasing a patch and publishing my report without even asking me for a review first. The first I heard about this patch was Tom Trevethan&#39;s twitter post a few hours ago. <br/><br/>Mercury&#39;s bug bounty program offers only 800 GPB for a critical loss-of-funds vulnerability. Rather than chasing Mercury down again for another mediocre payout, after this experience i&#39;m more inclined to just hold onto any new vulns I might find and exploit them later, if mercury ever sees wider use. <br/><br/>Oh well, it&#39;s their code i suppose. To be fair, Tom made clear they treat Mercury Statechains as unsafe prototype software, and clearly tell people not to use it with mainnet funds. Vulns like these are why. <br/><br/>Remember kids, if a dev tells you not to use their own code with real money, you should listen!<br/><br/>References:<br/><blockquote class="border-l-05rem border-l-strongpink border-solid"><div class="-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2">quoting <br/><span itemprop="mentions" itemscope itemtype="https://schema.org/Article"><a itemprop="url" href="/note13jcuax3zmupdld2egn8ew9n0jru4p4fd0e82csz499ugnyrj8jvs4vhqmw" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">note13jc…hqmw</a></span><br/> </div> Mercury Layer v0.2.0: Fix for Malicious Backup Transactions Vulnerabilities<br/><br/>"This update fixes vulnerabilities related to malicious backup transactions bypassing receiver verification checks. We've revamped the way backup transaction checks are constructed to ensure robust security."<br/><br/><a href="https://www.nobsbitcoin.com/mercury-layer-v0-2-0/">https://www.nobsbitcoin.com/mercury-layer-v0-2-0/</a> </blockquote><br/><a href="https://x.com/mercurylayer/status/1832062894428545114">https://x.com/mercurylayer/status/1832062894428545114</a><br/><br/><a href="https://conduition.io/code/mercury-disclosure/">https://conduition.io/code/mercury-disclosure/</a><br/><br/><a href="https://github.com/commerceblock/mercurylayer/blob/07b2a4485187592ed24c642b7284b321aceaa8fe/disclosure.md">https://github.com/commerceblock/mercurylayer/blob/07b2a4485187592ed24c642b7284b321aceaa8fe/disclosure.md</a> 2024-09-06T20:32:31Z https://njump.cloud.vinney.xyz/nevent1qqsz7crq9579encrj2m0ku8akd9cw859y76av0vlcs2ykh9wkxk683szyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9jts75ny In reply to <a href='/nevent1qqsgevwwng3d7qklk4v5fnuhzehep72s65khun4vgp2jj7yfjperexgpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgynlw4h'>nevent1q…lw4h</a><br/>_________________________<br/><br/>The vulnerabilities are described in detail on my blog here: <a href="https://conduition.io/code/mercury-disclosure/">https://conduition.io/code/mercury-disclosure/</a> 2024-09-06T19:57:41Z https://njump.cloud.vinney.xyz/nevent1qqsv9zxkwd008lreu9g9mxnc33ud2ygkjgklu7ns986ev2g73086kmczyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9j8vwp4l In reply to <a href='/nevent1qqsq0xfndva72a7ekz5xzljdf023fdltmpdhcr8gpcmxsf96266rznqpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet579dhed'>nevent1q…dhed</a><br/>_________________________<br/><br/>Thanks! To be fair I didn&#39;t &#39;break&#39; safetix - I just figured out how they worked by reverse-engineering. They do actually use solid cryptography, but TicketMaster markets them totally wrong.<br/><br/>Ironically, ecash is an ideal candidate to replace general admission event tickets while preserving ticketholder privacy. I doubt livenation cares about that though... 2024-07-25T21:34:58Z https://njump.cloud.vinney.xyz/nevent1qqs8hyd4quqx97k6cswp046myg9cx92rez7xzsjfy0pv0p5uk9cl5jczyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9jc0x9kg I just found out... there&#39;s a NIP for publishing discreet log contract messages on Nostr?? This is a crucial step for DLCs on Bitcoin. The present bottleneck for DLCs seems to be: How do I become an oracle? How do I find trustworthy oracles? NIP-88 would let us build apps which answer those questions.<br/><br/><a href="https://github.com/nostr-protocol/nips/pull/919">https://github.com/nostr-protocol/nips/pull/919</a><br/><br/>Combine this with ECash DLCs and we could have scalable, instant, completely private micro-contracts, which are discovered over Nostr and settled in ECash.<br/><br/><a href="https://github.com/cashubtc/nuts/pull/128">https://github.com/cashubtc/nuts/pull/128</a><br/><br/>But even if you don&#39;t like ECash, this NIP is still incredibly important. Kudos <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub1u8lnhlw5usp3t9vmpz60ejpyt649z33hu82wc2hpv6m5xdqmuxhs46turz" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>benthecarman</span> (<span class="italic">npub1u8l…turz</span>)</a></span> 2024-07-14T17:36:12Z https://njump.cloud.vinney.xyz/nevent1qqsft7v7p29c4qpkjqvws6agrvsuuf7aqjm7myqvegc4xw8m8twnjqgzyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9j08cevf In reply to <a href='/nevent1qqszmq0mjkv6xv4fdjx5zuhr0u08drpnc6ydatfe8gw0kqnszwecpkgpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5p9hpuk'>nevent1q…hpuk</a><br/>_________________________<br/><br/>Articles like this are what happens when the &#34;bored cipherpunk&#34; and &#34;frustrated customer&#34; venn-diagrams overlap 🐒 <br/><br/>Journalists have recently been contacting me about this article because of the big Ticketmaster hack recently. It&#39;s silly that they need some amateur like me to fact-check the erroneous PR statements issued by a multi-billion company. 2024-07-13T17:01:11Z https://njump.cloud.vinney.xyz/nevent1qqswh6hvyqegw880r5uwxrx4xwvun3n8wy5378ek2zq9wgsaxn4q5aqzyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9jgaep6x Had an idea for scaling submarine swaps into a multi-party protocol, and got some interesting results. Have a look: <br/><br/><a href="https://conduition.io/scriptless/multi-party-submarine-swaps/">https://conduition.io/scriptless/multi-party-submarine-swaps/</a> 2024-07-12T03:24:43Z https://njump.cloud.vinney.xyz/nevent1qqsrkq2tshpyqauv3p7jvj0s2y02hnmcccpderr0jm47slscy9zgqkqzyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9jal60c2 I made a PR into electrs to improve transaction broadcasting privacy. <br/><br/><a href="https://github.com/romanz/electrs/pull/1056">https://github.com/romanz/electrs/pull/1056</a> 2024-06-20T17:28:26Z https://njump.cloud.vinney.xyz/nevent1qqs2nm9kvcshrkcv56aetlk7e694rcw27ulymacsehsp0n6794pqpnczyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9j8hvjwf I couldn&#39;t find any reliable spec-compliant DLC oracles for real-world events, so I made my own. Meet Cassandra 🕵️‍♀️ <br/><br/><a href="https://conduition.io/code/cassandra/">https://conduition.io/code/cassandra/</a> 2024-06-02T22:46:37Z https://njump.cloud.vinney.xyz/nevent1qqs9xde7tnf6pp2hmun7ur4cs2rj02y8am6qk37nmd84zh67hk370hqzyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9j7heavt I wrote a draft NUT for Discreet Log Contracts settled on Cashu<br/><br/><a href="https://github.com/cashubtc/nuts/pull/128">https://github.com/cashubtc/nuts/pull/128</a> 2024-05-27T16:20:05Z https://njump.cloud.vinney.xyz/nevent1qqsppthzcwaxx838v8c7keucs2f659vx6ka0kdx4dngvleecp20ql4qzyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9jp3w0d7 You can settle Discreet Log Contracts with Chaumian ECash!<br/><br/><a href="https://conduition.io/cryptography/ecash-dlc/">https://conduition.io/cryptography/ecash-dlc/</a><br/><br/> <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>calle</span> (<span class="italic">npub12rv…85vg</span>)</a></span> and other ecash devs: Do you think this would make a candidate NUT extension on the cashu spec?<br/><br/>Feedback appreciated 😎 <br/><br/><a href="https://github.com/conduition/conduition.io/pull/6">https://github.com/conduition/conduition.io/pull/6</a> 2024-05-19T20:33:49Z https://njump.cloud.vinney.xyz/nevent1qqs8k850tsvvz9wgy6pqpkhuxckd7gk9hsrma5h3g6p3afulq8e9k3czyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9ju6jtec In reply to <a href='/nevent1qqsrm0lhec5t3haenm996k8hpry6rmtfza5fu8cuswj0kalwesh0n5cx22wj7'>nevent1q…2wj7</a><br/>_________________________<br/><br/>I&#39;ve been working on FROST+taproot lately and the xonly nonsense easily accounts for 90% of the complexity.<br/><br/><a href="https://github.com/ZcashFoundation/frost/pull/584">https://github.com/ZcashFoundation/frost/pull/584</a><br/><br/>I&#39;d be curious if anyone has actually done the math to compute how much xonly has saved us in block space. <br/><br/>...only for the inscription meme lords to slide in and use 100x that space for jpegs. 2024-05-17T15:28:08Z https://njump.cloud.vinney.xyz/nevent1qqs0yxp49vysclm0d2vcrewh7fcnq8dswjltvy9m6stcqnuh6y0l5rszyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9jm3fgsf In reply to <a href='/nevent1qqszepfylq3g9yr8nh8wygp0dusum492trsddry6x8pdawg9ylxsm9cjerds0'>nevent1q…rds0</a><br/>_________________________<br/><br/>If you can, i would suggest running your own lightning node. Then you can use a remote access wallet like Zeus to interact with it. 2024-05-10T14:33:50Z https://njump.cloud.vinney.xyz/nevent1qqs83hlpt7n7jtc8a9m0ell3uam7ydv0u0zqtx8fr52un5vqh0l4axgzyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9jcspgcq Privacy and self-custody services with a central point-of-failure are not stable long-term. <br/><br/><a href="https://www.nobsbitcoin.com/agoradesk-localmonero-shutting-down/">https://www.nobsbitcoin.com/agoradesk-localmonero-shutting-down/</a><br/><br/><a href="https://www.nobsbitcoin.com/zksnacks-to-suspend-its-coinjoin-coordination-service-on-june-1st/">https://www.nobsbitcoin.com/zksnacks-to-suspend-its-coinjoin-coordination-service-on-june-1st/</a><br/><br/><a href="https://www.nobsbitcoin.com/samourai-dojo-v1-25-0/">https://www.nobsbitcoin.com/samourai-dojo-v1-25-0/</a><br/><br/><a href="https://www.nobsbitcoin.com/phoenix-wallet-to-be-removed-from-us-app-stores-on-may-3/">https://www.nobsbitcoin.com/phoenix-wallet-to-be-removed-from-us-app-stores-on-may-3/</a><br/><br/><a href="https://www.nobsbitcoin.com/sparrow-wallet-v1-9-0/">https://www.nobsbitcoin.com/sparrow-wallet-v1-9-0/</a><br/><br/><a href="https://www.nobsbitcoin.com/samourai-wallet-founders-arrested-and-charged-with-money-laundering/">https://www.nobsbitcoin.com/samourai-wallet-founders-arrested-and-charged-with-money-laundering/</a><br/><br/>The cull we&#39;re seeing in the past couple weeks is just the beginning, but it&#39;s a good sign: They&#39;re pushing back because we&#39;re gaining ground. <br/><br/>If you want to run a privacy business, i see 3 choices: <br/>- Decentralize your business (no single PoF)<br/>- Mask yourself (build pseudonymously)<br/>- Comply (by KYCing)<br/> 2024-05-08T15:58:00Z https://njump.cloud.vinney.xyz/nevent1qqsfjk3usvg60qk9s26wezw773m0fecugz0dg6spz9594qfz23unwngzyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9jau5kmy In reply to <a href='/nevent1qqsw2dc2lnuh3uhutxc2jcn406tg7n6k2dgvnekphgv7vmmvf5x85hqxjz03s'>nevent1q…z03s</a><br/>_________________________<br/><br/>Did they seriously upload entire xpubs? Not just addresses?<br/><br/>Can i see a source on that? 2024-04-25T17:20:15Z https://njump.cloud.vinney.xyz/nevent1qqs8qj3m8c655su2qncew6z06yslhwcx4vyjfmvnj9wlllxl4e43kcczyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9jych7zy In reply to <a href='/nevent1qqsgxwd3evfz7v4z5jmdlvpx798myuzl7m90ahckt2y8euk3fw7mf2gwahe6j'>nevent1q…he6j</a><br/>_________________________<br/><br/>This scheme doesn&#39;t scale. <br/><br/>If every TX used paypal&#39;s approach, the &#39;green miners&#39; would end up with thousands of dust UTXOs which they would need to clean up, every single block. Network throughput would drop significantly.<br/><br/>With standard bitcoin fee subsidy, all miner fees are automatically consolidated in the coinbase transaction: No dust to clean up.<br/><br/>Not to mention the fact that this approach doesn&#39;t necessarily require the miners to use green energy to mine the TX - it just incentivizes a particular arbitrary set of miners to mine the TX. Those miners could pay off a different non-green miner to mine the TX, because it is still consensus-valid.<br/><br/>Paypal&#39;s idea is just a roundabout way of reinventing the same open fee market which already exists, but with a lame attempt at green-washing. 2024-04-25T17:15:27Z https://njump.cloud.vinney.xyz/nevent1qqsv5m4x9tc8rmjntw38mtnrrekyqvs7wl5vwqd4ske385gm074k00qzyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9j44frrp <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub1hea99yd4xt5tjx8jmjvpfz2g5v7nurdqw7ydwst0ww6vw520prnq6fg9v2" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>craigraw</span> (<span class="italic">npub1hea…g9v2</span>)</a></span> How do you feel working on Sparrow Wallet, now that we&#39;re seeing the US government prosecute the Samourai devs? 2024-04-25T01:05:55Z https://njump.cloud.vinney.xyz/nevent1qqsdca367j7x0qxv423rn4njd56dm0374zkm4wy8c53rmje723rtz3qzyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9jmnx69g In reply to <a href='/nevent1qqst0hm340sdqxladdzl672gwnfqe9dvsucqvg6a0ltz2578s8zwnccvswt2v'>nevent1q…wt2v</a><br/>_________________________<br/><br/>No problem 😁 great choice 2024-04-25T00:22:11Z https://njump.cloud.vinney.xyz/nevent1qqs9xt5ztzdtjxj2kaa5nmk6rp6rrr0xv6v8ctr3s8995c7k4xsg9rqzyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9j5s67hq In reply to <a href='/nevent1qqsx7lk9t2xqem5dcl8xywully06nras74tqcm3df4cm7ucfjvyt82ggxay2e'>nevent1q…ay2e</a><br/>_________________________<br/><br/>I mean pseudonymously. 2024-04-25T00:21:16Z https://njump.cloud.vinney.xyz/nevent1qqsrvk00vxeyh4687z67060qyaa2v2lerenhd9jpcjagycvyrvthuvqzyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9jdqj3aa Develop pseudonymously, or else. <br/><blockquote class="border-l-05rem border-l-strongpink border-solid"><div class="-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2">quoting <br/><span itemprop="mentions" itemscope itemtype="https://schema.org/Article"><a itemprop="url" href="/nevent1qqspu7chsvza6s4ledz3n6y4dvjzc6q6pn8y0vey92ee37vytdu78yspp4mhxue69uhkummn9ekx7mqzyzu62d6j8wazlndws47epk98vr0y7gfee8usmxr0w37w058vp5tn6qcyqqqqqqgcf75hh" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">nevent1q…75hh</a></span> </div> BREAKING: Samourai Wallet Founders Arrested & Charged with Money Laundering, Unlicensed Money Transmitting Offenses<br/><br/>- The charges include conspiracy to commit money laundering and conspiracy to run an unlicensed money transmitting business.<br/>- The Samurai Wallet website has been confiscated, and a seizure warrant for Samurai's mobile application has been submitted to the Google Play Store.<br/><br/><a href="https://www.nobsbitcoin.com/samourai-wallet-founders-arrested-and-charged-with-money-laundering/">https://www.nobsbitcoin.com/samourai-wallet-founders-arrested-and-charged-with-money-laundering/</a> </blockquote> 2024-04-24T22:59:04Z https://njump.cloud.vinney.xyz/nevent1qqswmgm9l8ey2wt8yumxy7thypfhw2paygd7zurr76sx26fc3vuvy5czyrltsshzucjvkk8rvnu00jek8sp5q7lf2xddfqex75v0ja4n25g9j2zsm88 In reply to <a href='/nevent1qqswunzp4wnp8flv8w6f4f8e7r2ljueezwjgyjy2swc6gdw3wytwv2qhp4yfu'>nevent1q…4yfu</a><br/>_________________________<br/><br/>Responded on github about this. For your particular case, using --no-rest-tls is unsafe. However generally speaking, i should probably add a flag to allow plaintext connections as there are some cases where it is safe 2024-04-23T14:39:49Z