2026-09-14T00:00:05Z https://yabu.me https://yabu.me/npub1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqzqujme https://yabu.me/r/relay.hodlboard.org https://yabu.me/nevent1qqs0h2n5vn4a5ucu7h9464addvq5mgxl9cnf74jlr8ye4ck38ztzm6gpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4eg0wau9y In reply to <a href='/nevent1qqsq9h0j8cmgfeztkujmv7f0m4epvmfca9fah9g8gfk6ju8paypylpgpz9mhxue69uhkummnw3ezuamfdejj7qls33c'>nevent1q…s33c</a><br/>_________________________<br/><br/>I&#39;ve been vacillating on this one. On the one hand, the push towards fear seems like it&#39;s being manufactured. On the other hand, I can easily imagine, even if a way out in the future, some very negative scenarios could play out. If agents become as much smarter than us as we are compared to, say, rodents, then it becomes nearly impossible to predict the outcome. I&#39;m just not sure. But I don&#39;t think some global &#39;disarmament agreement&#39; will work the same way it ~ did for nuclear material, since the ability to deploy this tech is so much easier and so strongly economically motivated. 2026-09-14T00:00:05Z https://yabu.me/nevent1qqsgrvaleffghzlmtegpt9egf8utdca4ugtm76p3r9w23kpkszvgxqspr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4eg64sy9z In reply to <a href='/nevent1qqsz3ae9lrq76j85hjuctel4hh3yn994ys47jsxxdk840rate9s39qcpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtc67002f'>nevent1q…002f</a><br/>_________________________<br/><br/>Yep you trade privacy off for reliability. Only partly of course, but you do. Not a panacea but way better than custodial. That&#39;s how I see it. Re: complicated to get funds back, I don&#39;t think so, but I&#39;m not sure, haven&#39;t tried it recently. There is a close channel option that presumably force closes as you&#39;d expect. 2026-09-12T21:30:28Z https://yabu.me/nevent1qqszwcycqylghfewwgafhyfu5rh32awy4yy7k3np05yvjls4gqttqlspr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4eg40aez2 Closed my Revolut account earlier this year, seems like I was a bit too late.<br/><br/>Who am I kidding, they&#39;re all exactly the same. 2026-09-14T01:26:31Z https://yabu.me/nevent1qqs86tvnaum2eww68dtpjvl5wgwu7e8u6h98e2mczer3utjxa8rgg0spr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egeruecx i did this a few years ago, but i should update it: &#34;What have you used Lightning to buy?&#34;. My answer is now: &#34;drinks at bars/events, food (dinner) including sharing the bill with other people, hotel rooms, flights, cellphone bills (both the normal type and esims), electricity bills, water bills, internet bills, taxis, takeaways, groceries (last 3 via gift cards) VPS, VPN, charity donations, trades with friends (usually for USD cash), topping up a debit card, payment for nostr relays, zaps on nostr and LLM model tokens.&#34; Probably missed a good few miscellaneous &#39;buy a thing&#39;, but that covers a lot. I have to go via bitrefill for a couple of these, especially internet and electricity bills (in El Salvador; which is also where I got the debit card I can top up with Lightning).<br/><br/>I should also say that &#39;flights and hotels&#39; being higher cost items, are almost always with btc mainchain or via some other method, but I think I used lightning once or twice here (and will always choose it if I can!). And lastly I should say that having done this for years, with a *self custodial wallet* (I used Electrum a bit but I mostly used Phoenix), I basically *never* have payment routing failures, that used to happen all the time pre-2023.<br/><br/>But apparently I&#39;m all alone because nobody uses Lightning. 2026-09-12T17:51:25Z https://yabu.me/nevent1qqsr92jyhx4agu9d4hn792dpkqyhgyqwayeq39j9cae3z95t0mfy5jqpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egxu0e4w In reply to <a href='/nevent1qqsg8uaspgrvnf8ezv2pmtd2kmx3tn8j6vdgst327tlf8khd3g9j9dccznvu5'>nevent1q…nvu5</a><br/>_________________________<br/><br/>Phoenix because it&#39;s reliable while self custodial.<br/><br/>In the last year or two I haven&#39;t even bothered to run my own LN node at home (or elsewhere). I used to, but I don&#39;t have the motivation or the organization to do it properly. Which is a shame, but shrug.<br/><br/>Also my case is not normal, I spent the last few years in El Salvador mostly. <br/><br/> 2026-09-12T19:58:18Z https://yabu.me/nevent1qqsta3eu79vz6ssey3mtd0u4wz5vuln7glspsufjegzczctynve4fzspr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4eggkwnsg In reply to <a href='/nevent1qqstg0waut0x2lcys4n34k3wa0ch5rjcc2nhuql56s3xcjytaev2nggpz9mhxue69uhkummnw3ezuamfdejj7kg9nw9'>nevent1q…9nw9</a><br/>_________________________<br/><br/>From what I heard that&#39;s pretty typical. As in the general market for mid to upper end flats in (central?) London has turned down heavily. Though I don&#39;t live there any more. 2026-09-09T13:34:24Z https://yabu.me/nevent1qqsgsv020rajmrpung5ju9h3s9y8dtgm8s39gnals76pkm7t9n8fywspr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egutxav5 Reflections on the Liquid hack.<br/><br/>Take it at different layers:<br/>1/ A central point of failure, even if distributed, holding everyone&#39;s funds makes it a brittle design. True. Obviously no nuance there, but it&#39;s the first guiding point. It&#39;s the reason it&#39;s always been way less interesting than a decentralized sidechain would be.<br/><br/>2/ Let&#39;s not forget that they *had a whitelist system for exits*. As in, you could not independently peg out, you had to go through a trusted intermediary. This is somehow a failure in 2 opposite directions: it removes reasonable claims of censorship resistance, but, when it came down to it, they also *completely failed to censor* a transaction that no reasonable human-in-the-loop would allow. It&#39;s practically a terrible failure, but the whole shape of this problem follows from 1/ so it can never be fully eradicated/corrected.<br/><br/>3/ The software bug was not actually about the cryptography/privacy feature (but wait for 4/ !). It was a logic error in the way that rangeproofs (you can think of them how you think of signatures in normal bitcoin: a little blob of data that proves the transaction is valid) were stored and accessed. it&#39;s normal to cache things in software like this that has a significant performance requirement: even simple things like hash functions that are fast. Normal, but of course, it has to be done super carefully (e.g. they have a signature cache in Bitcoin Core) to avoid accepting signatures, rangeproofs and similar, that aren&#39;t actually valid. It *was* &#34;just&#34; a software bug, a subtle and tricky one that was easy to miss.<br/><br/>4/ ... Whether 3/ is fair or not as a characterization, here&#39;s a surprising feature that *is* absolutely dependent on the cryptography/privacy feature: the *effect* of the bug. Now, it&#39;s true that there are non-crypto ways to have catastrophic balance errors, like the 2010 bug in bitcoin that allowed someone to print billions of btc. but not only are they easier if you put the balance arithmetic behind a cryptographic blinding, but they&#39;re also easier to be invisible (in Liquid&#39;s case, only until you peg out, of course). But it was the crypto structure that allowed this cache hit error to turn into a complete wipeout; if you had some egregious error in signature caching in vanilla bitcoin, I think the worst that can happen is you can steal someone else&#39;s money, *not* create bitcoin out of thin air, **because balance checking is not dependent on cryptography, only arithmetic**.<br/><br/>5/ This last one is more in the weeds: as per 3/ caching makes sense because the verifier&#39;s computation of the validity of a rangeproof is not free. In fact, this is something specific to bulletproofs as a ZKP: the efficiency of its &#39;bandwidth&#39; (what has to be sent over the wire; which is also, for a blockchain application, what has to go onchain) comes from essentially folding up the proof&#39;s multiple layers into one. the downside is that the verifier has to &#39;unroll the loop&#39;: they have a computational cost linear in the size of the statement. All that&#39;s to say, rangeproof verifications are not too efficient. In a different type of ZKP, such as a Groth16 SNARK, the cost of verification is O(1), that is, constant. But that is just not possible on Bitcoin or on bitcoin&#39;s EC curve. 2026-09-09T13:17:02Z https://yabu.me/nevent1qqst030xacw8r0yh3dhxnmz2dnqqg2rp23mcp6zjk57xxd4wyfaqu0cpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egzu8sll In reply to <a href='/nevent1qqsy62f42pnnmkqls879ntallxznkhd747dc29csl22yfmstuds8pncpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcgpq8k4'>nevent1q…q8k4</a><br/>_________________________<br/><br/>I did. I have a vague impression that it&#39;s overblown. Very vague though. The thing is, how much difference does it really make, long term? 2026-09-08T19:42:07Z https://yabu.me/nevent1qqsvj2y3hsxlqv89p3jdahxa9ms5aqcjumdaqaturkzlmcgshcnlw2cpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egvyql57 Anyone else starting to think they judged Kurzweil too harshly? Just had an AI call me about my home security, which modulated its speech when it realized my cellphone signal was bad. It got the info it needed and politely ended the call.<br/><br/> Then I opened twitter and saw that they had solved Navier Stokes. It&#39;s all a bit much. 2026-09-08T19:31:08Z https://yabu.me/nevent1qqsqs680w2tue3uxw6ffpvkfl6ug4tkt6tmly5cn05uruq8c56tzl0qpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egkjzks6 In reply to <a href='/nevent1qqs0tuh3ycakpqar6xvxakkzdngs5yjkm442apwjyj6m07gjhwfyrrcpramhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvuhkjmnzdauq89kyyv'>nevent1q…kyyv</a><br/>_________________________<br/><br/>Yeah i qualified in reply. But this is nostr, so, understandable 😄 2026-09-08T13:26:29Z https://yabu.me/nevent1qqstrg0rykjvtw8n969phu0pdt9u8ksm7f3pyz9s6l8jcjm47jnxl0spr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4eg0e8q00 In reply to <a href='/nevent1qqszv0nmdlrkk070nc75pvv502khw8klgr6u62n7jem9enjyece5jnspramhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvuhkjmnzdauqrxeg4c'>nevent1q…eg4c</a><br/>_________________________<br/><br/>I wrote that before the 15%.<br/><br/>The other two points are good. Especially the first one; since they could take anything, it&#39;s a particularly good point.<br/><br/>The third one is not as clear cut, but definitely to be considered. 2026-09-08T02:48:39Z https://yabu.me/nevent1qqsdf24nr2phdmlu23nq56va4yvmctzsyfkachhhnus53tncja70ufspr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egvmmkhs In reply to <a href='/nevent1qqsgy9jf5kum2edr44r98kc5yza4sk20l73n6d9fplp7fhzshvp3q0qpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtc97lkcw'>nevent1q…lkcw</a><br/>_________________________<br/><br/>Good qualifications but I don&#39;t see how it equates to &#34;No&#34;. I trust myself to keep a private key safe for a short period. And giving it back wasn&#39;t hard either, as has been demonstrated now. 2026-09-07T18:25:33Z https://yabu.me/nevent1qqsfn4zjqfg3f3es90ur7ecpk36j4sd8kmfh5wz85ae3tzhu3czjhtspr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4ega8ymve In reply to <a href='/nevent1qqst2hsf2s632tf4hgpwvwd2cp293x9kzkc56ewzzadgklspqs43xsczfnzvj'>nevent1q…nzvj</a><br/>_________________________<br/><br/>&#39;Wrong&#39; was oversimplified on my part, though I stand by it.<br/><br/>What I was thinking about more was the risk. Taking a big chunk (as apparently they now have done) unilaterally puts them firmly in the criminal category from a legal perspective. IANAL but I think they could have very reasonably and ethically argued that they did not steal, if they hadn&#39;t done that.. Now, they cannot. Of course if their opsec is tight, they may avoid the consequence, but that&#39;s another Q. <br/><br/> 2026-09-07T16:35:39Z https://yabu.me/nevent1qqs94gkms3fua3m9n9nlwnf44ykjm0cvfa346x70ca4jxepz09qahagpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4eg5zw39c In reply to <a href='/nevent1qqs8897w4ua97rymxe5jeqj088uaww6de78p3m4as3hmpe253e8j49spramhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvuhkjmnzdauqcjrh5n'>nevent1q…rh5n</a><br/>_________________________<br/><br/>Yes, that&#39;s what&#39;s happening. They&#39;re finding a way to return that bitcoin safely to control of the 11/15 federation multisig (if they&#39;re honest). Which they could do immediately *if* the signatories didn&#39;t have infrastructure that automatically sends it out on any &#34;valid&#34; Liquid transaction that has a peg-out.<br/><br/>So yeah if Liquid is currently 100% shutdown then it&#39;d be safe to send, even without a bugfix. Maybe that&#39;s your point.<br/><br/>I don&#39;t know if the blockchain is totally or partly shutdown right now. 2026-09-07T15:38:55Z https://yabu.me/nevent1qqsffuvk6sjaajmpdedgxq0e2rn27gzhxsg9tx805qnrd7vyqk940mspr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4eg8v6shq In reply to <a href='/nevent1qqsqqqqxvsk9vsa9p9au367a4eu07ppsjwspuz69qkdfpuk628kapqcpz9mhxue69uhkummnw3ezuamfdejj7uryhm3'>nevent1q…yhm3</a><br/>_________________________<br/><br/>Yes, people should definitely be spooked! Not saying &#34;definitely the guy has good intentions &#34;. 2026-09-07T14:37:02Z https://yabu.me/nevent1qqsgkqxrsn02tjzpnax6dy48749342puslvpw4epkzpguhv6h8ujgscpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4ege7x35h In reply to <a href='/nevent1qqsgqwdm59qj7tu3m6ad73t5fay5kw36m56rvcsvrhlgnpnsnyk9zagprfmhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvuhs6w5wcm'>nevent1q…5wcm</a><br/>_________________________<br/><br/>...But them saying &#39;I&#39;ll send *most* of it back&#39; instead of negotiating a bounty separately, is wrong. 2026-09-07T14:14:18Z https://yabu.me/nevent1qqswu7pml7gt37czjywuyspav72qe4apez779leqv3lzj6w6k2n9hrcpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egsqxfv2 In reply to <a href='/nevent1qqsqqqyxlw3m54cnfjel8rx3ee0llgd9xylfl0a43xkwnl4dwqxxmzspzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcey4x9j'>nevent1q…4x9j</a><br/>_________________________<br/><br/>I mean technically you&#39;re 100% right. But you can still argue that swiping it the second you realize you can, is the more correct choice. 2026-09-07T14:13:10Z https://yabu.me/nevent1qqsgqwdm59qj7tu3m6ad73t5fay5kw36m56rvcsvrhlgnpnsnyk9zagpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egz3k87q The &#34;Whitehat? Bullshit, that&#39;s stealing&#34; natural response isn&#39;t really justified.<br/><br/>If you see this bug and you don&#39;t want every user to lose their money, you are somewhat ethically bound to confiscate it until the devs release a fix.<br/><br/>You are thus making deployment of the fix 100x less dangerous (because the collateral is not exposed during the transition.<br/><br/>(Hot take? I don&#39;t think so?) <br/><br/> 2026-09-07T13:35:29Z https://yabu.me/nevent1qqsquvq8fvul8t2qhzzawfwt43n945ej37km7epkgh5fgqlerkdft3gpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egtfrv8g In reply to <a href='/nevent1qqsx5tkejgkd6rl8zes7xmhla6lrq634ylwsf4kyulr9qvplulwr4dceatvt4'>nevent1q…tvt4</a><br/>_________________________<br/><br/>I should really show the follow up paragraph:<br/><br/>&#34;While I&#39;m not the King of Monero, I am frustrated my approval was given to a PR on a faulty premise. I&#39;m trying to funnel this frustration into not having to worry about this anymore. Yes, serializing the entire TX is overkill. That&#39;s the point. It may be less efficient. This offers a 5x perf boost. I&#39;d rather hear we left .1x on the table than hear we had a double spend in the next release.&#34;<br/><br/>I hope more developers of bitcoin security code don&#39;t feel bad about &#34;overkill&#34;, either! <br/><br/> 2026-09-07T12:52:59Z https://yabu.me/nevent1qqsx5tkejgkd6rl8zes7xmhla6lrq634ylwsf4kyulr9qvplulwr4dcpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egl597l3 In reply to <a href='/nevent1qqspw84hw3c0u84h5ts0hted0hr0jsfmsexzpm0qyz0upqfaf6feu3gxr9ldk'>nevent1q…9ldk</a><br/>_________________________<br/><br/>A comment by Luke Parker (guy who&#39;s the main author of FCMP stuff) struck me on a PR to introduce such a verification cache:<br/><br/>&#34;We could just serialize key images, and fix that issue. I suggested in #8707. The problem is how it&#39;s been pointed out there&#39;s yet another field with this behavior. I don&#39;t want to play cat and mouse forever. The TX&#39;s entire networked value, and the mix ring (via do_serialize and as tested by @jeffro256 ) is complete. **Considering this code disables almost every single line of meaningful TX validation code**, I&#39;m not willing to settle for less anymore.&#34;<br/>(emphasis mine). <br/><br/> 2026-09-07T12:48:33Z https://yabu.me/nevent1qqspw84hw3c0u84h5ts0hted0hr0jsfmsexzpm0qyz0upqfaf6feu3gpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4eg4tkkap It&#39;s remarkable (if not surprising) that this comment exists in the Monero source, about caching the same kind of verification:<br/><br/> <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="/nevent1qqs8dxhek3h98d086mdzyz6lxerpz2vwctqkl63e5seq6xxpe4t530qzypn4hp87wh3pd2u5036r3mj3njnhw5mkmhc9mt0m5cnch5qju8tjsqcyqqqqqqgaxrwly" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">nevent1q…rwly</a></span><br/> </div> Why the heck wouldn't they belt and suspenders with the transaction hash?<br/><br/>(They could also just not cache, full stop. Better choice for Liquid specifically imo, but easy to say in retrospect). </blockquote><br/> <img src="https://blossom.primal.net/0fab5fc0fe7cb41e275cea0d129eae809be225e6e0aa33afe30f1895e4719c8d.jpg"> 2026-09-07T12:40:04Z https://yabu.me/nevent1qqszlfeaqlct3pdkzhg9ax8azaptgp9p3fawmxmtctjjnk9gd2yc34spr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egexy8fu In reply to <a href='/nevent1qqsxa2s728xnnjnr3lv6xreenhl4mlmgru7cprg3fl797mzpegystxqpramhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvuhkjmnzdauq0ff3sn'>nevent1q…f3sn</a><br/>_________________________<br/><br/>Yes, indeed. The pre-patch version didn&#39;t have length checks either, but it didn&#39;t matter with only (proof, commitment). A very well intended security patch that exposed a pre-existing flaw. Fucking hell software is hard! 2026-09-07T12:20:48Z https://yabu.me/nevent1qqs8dxhek3h98d086mdzyz6lxerpz2vwctqkl63e5seq6xxpe4t530qpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egss65mt In reply to <a href='/nevent1qqszlfeaqlct3pdkzhg9ax8azaptgp9p3fawmxmtctjjnk9gd2yc34sprfmhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvuhs8n2d7l'>nevent1q…2d7l</a><br/>_________________________<br/><br/>Why the heck wouldn&#39;t they belt and suspenders with the transaction hash?<br/><br/>(They could also just not cache, full stop. Better choice for Liquid specifically imo, but easy to say in retrospect). 2026-09-07T12:26:02Z https://yabu.me/nevent1qqs28vql4mu4llv4ragayw49qzsyhkjqp494wm45spcjunmq293y4sspr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egqgheqe In reply to <a href='/nevent1qqsffnvxncaypjm9aj8pd6q2gxj7gh2yl2ldwjtxhmh5zgfxl2s8nzcpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcygrvdm'>nevent1q…rvdm</a><br/>_________________________<br/><br/>I feel like the true root cause is this one:<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 <span itemprop="mentions" itemscope itemtype="https://schema.org/Article"><a itemprop="url" href="/nevent1qqsdfh30udag9vlvkztvlp0suntrz04svvkdlj6ad9x42a3gu2amq6gpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtczypn4hp87wh3pd2u5036r3mj3njnhw5mkmhc9mt0m5cnch5qju8tjsqcyqqqqqqgaa0nvp" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">nevent1q…0nvp</a></span><br/> </div> it seems that the bug ultimately comes down to this line: "<a href="https://github.com/ElementsProject/elements/blob/c7e856fab1b0c4d37005e25c0940184d812a26a0/src/script/sigcache.cpp#L60">https://github.com/ElementsProject/elements/blob/c7e856fab1b0c4d37005e25c0940184d812a26a0/src/script/sigcache.cpp#L60</a> " . range proofs that hit the cache that is keyed to this hash, are counted as valid without checking. the problem is that the data fed into the hash is not length checked. so you can feed different (proof, commitment, asset) tuples into it by varying the length of the proof. the proof can be totally invalid and it'll still come back as valid. and this explains why OP_RETURN is involved: you need an extra output to sort of 'consume' the invalid amount. so you make a totally valid output of 4000 btc and you shove the negative corresponding value in the OP_RETURN. Apparently the anomalous size of the proof confirms this reading (bulletproofs rangeproofs have specific sizes based on the bit range 0..2^k). The only part I don't get is why there was a consensus deviation. Did some nodes have the rangeproof caching disabled or something? </blockquote><br/>The reason I got convinced is that this theory matches the size of the &#34;garbage proof&#34;.<br/> 2026-09-07T02:21:46Z https://yabu.me/nevent1qqsdfh30udag9vlvkztvlp0suntrz04svvkdlj6ad9x42a3gu2amq6gpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egn9fda3 it seems that the bug ultimately comes down to this line: &#34;<a href="https://github.com/ElementsProject/elements/blob/c7e856fab1b0c4d37005e25c0940184d812a26a0/src/script/sigcache.cpp#L60">https://github.com/ElementsProject/elements/blob/c7e856fab1b0c4d37005e25c0940184d812a26a0/src/script/sigcache.cpp#L60</a> &#34; . range proofs that hit the cache that is keyed to this hash, are counted as valid without checking. the problem is that the data fed into the hash is not length checked. so you can feed different (proof, commitment, asset) tuples into it by varying the length of the proof. the proof can be totally invalid and it&#39;ll still come back as valid. and this explains why OP_RETURN is involved: you need an extra output to sort of &#39;consume&#39; the invalid amount. so you make a totally valid output of 4000 btc and you shove the negative corresponding value in the OP_RETURN. Apparently the anomalous size of the proof confirms this reading (bulletproofs rangeproofs have specific sizes based on the bit range 0..2^k). The only part I don&#39;t get is why there was a consensus deviation. Did some nodes have the rangeproof caching disabled or something? 2026-09-07T02:06:04Z https://yabu.me/nevent1qqsgf5jcl4fw5kcayepnh357yu4mn0g00x6p20cfp6c9lspr80h8rnqpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4eg0nsy8y In reply to <a href='/nevent1qqsvugavgz56r5343mrshcy7u3227yg7662qflggq5jt4x5lr5m3h7spzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtc0msce4'>nevent1q…sce4</a><br/>_________________________<br/><br/>So they were caching range proofs and it&#39;s a caching bug? Like in that they bypass verification of the rangeproof on a cache hit? That&#39;s what I&#39;m seeing now. If so, that&#39;s... terrible?<br/><br/>This patch seems to be the fix: <a href="https://github.com/ElementsProject/elements/commit/c26d719c29a40da280a825b25657e9c3d8bc7d99">https://github.com/ElementsProject/elements/commit/c26d719c29a40da280a825b25657e9c3d8bc7d99</a> 2026-09-06T22:55:31Z https://yabu.me/nevent1qqs0pea5glqt6fxd7j57rjfwe78k6xd3630psulckkxqfegkpc9d2zqpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4eg6375vn In reply to <a href='/nevent1qqsd32h6c3kepj82uuunxusuuxm33c8653psyy7neuw3paarvmdmzagpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtc2tzww2'>nevent1q…zww2</a><br/>_________________________<br/><br/>Oh. Double wow. 2026-09-07T00:46:54Z https://yabu.me/nevent1qqsppcqhk304zppgdmxqkktvv9fhw8ewm92dmcuemn4d7efc8f426jgpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egsjdzl2 In reply to <a href='/nevent1qqs0edm0keu7vlpfvzgzqxchw0qwjduzmsgsrksfzaznecuespdzcxqpramhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvuhkjmnzdauqwz4sud'>nevent1q…4sud</a><br/>_________________________<br/><br/>Yeah I&#39;m seeing now it&#39;s not as simple as that! Which is a relief, but then again I haven&#39;t seen the right explanation yet, so I should hold off on that relief ... 2026-09-06T22:34:45Z https://yabu.me/nevent1qqs2psfylw3e3xq6nxup9u2aln5a6ts7apaqcdnylu6vw7eav9f24lgpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4ege7j0gx I think GLM 5.2 might have found this. See Poelstra&#39;s response in this github thread: <a href="https://github.com/ElementsProject/elements/issues/1325">https://github.com/ElementsProject/elements/issues/1325</a> . What if someone created a transaction with an OP_RETURN that has a pedersen commitment that has some big negative value? If it gets included in the balance equation, that can work *only if* the range proof is not attached to that output.<br/><br/>See <a href="https://blockstream.info/liquid/tx/f24a4b179b5cc7e88b25a763911f7cbdf2bf45d1d1b5ab611e94461cef0a183f?expand">https://blockstream.info/liquid/tx/f24a4b179b5cc7e88b25a763911f7cbdf2bf45d1d1b5ab611e94461cef0a183f?expand</a> - this is the transaction at which people are saying there&#39;s a consensus split.<br/><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="/nevent1qqsty3vr0h7d94eq377s7tpu87f9qd653nydvpsx7yavgcaz0m2pe5gpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtczypn4hp87wh3pd2u5036r3mj3njnhw5mkmhc9mt0m5cnch5qju8tjsqcyqqqqqqgsymlcr" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">nevent1q…mlcr</a></span> </div> <a href="https://x.com/i/status/2096696669287178696">https://x.com/i/status/2096696669287178696</a><br/><br/>Steven Roose (who used to work on Liquid) seems to think it's a confidential transactions bug. Seeing others tend towards that conclusion too.<br/><br/>Wow.<br/><br/>Notably they're still using original flavor CT not bulletproofs afaik. </blockquote> 2026-09-06T22:11:17Z https://yabu.me/nevent1qqsvewvdl0w4lav7ts037jv6qcn94t5e62hrtg6aa99pl453zws3w9spr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egxafsqp In reply to <a href='/nevent1qqsty3vr0h7d94eq377s7tpu87f9qd653nydvpsx7yavgcaz0m2pe5gpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcgwgxd2'>nevent1q…gxd2</a><br/>_________________________<br/><br/>Oh I am wrong, they do use bulletproofs now: <a href="https://docs.liquid.net/docs/confidential-transactions">https://docs.liquid.net/docs/confidential-transactions</a> 2026-09-06T21:57:59Z https://yabu.me/nevent1qqsty3vr0h7d94eq377s7tpu87f9qd653nydvpsx7yavgcaz0m2pe5gpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egys20en <a href="https://x.com/i/status/2096696669287178696">https://x.com/i/status/2096696669287178696</a><br/><br/>Steven Roose (who used to work on Liquid) seems to think it&#39;s a confidential transactions bug. Seeing others tend towards that conclusion too.<br/><br/>Wow.<br/><br/>Notably they&#39;re still using original flavor CT not bulletproofs afaik. 2026-09-06T21:42:28Z https://yabu.me/nevent1qqs8rpclc7x748j0ct8w4ks400n6ycs3hemsqu53vymrz6pxxvnsx5spr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4eg003lme In reply to <a href='/nevent1qqsw7pcful3whupp9gyzgsvlaawrgv7l9s23udz4d43n7c047fds8fgpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtc82aeyt'>nevent1q…aeyt</a><br/>_________________________<br/><br/>They&#39;re already exceptionally good at hardcore cryptography i think. As of last few months, for sure. But it&#39;s less likely to be there. Just vague opinion, to be clear. 2026-09-06T20:50:57Z https://yabu.me/nevent1qqst6xuhg947wjkuhd5sgysqtdg72qwdc6qye5cnjuvg9hlk6xjs4hcpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egs05mjq In reply to <a href='/nevent1qqsd4pkprf449d7yjes6eygj2y0efrhtv708ednc50agymftzr0yp3qpramhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvuhkjmnzdauqn5xadl'>nevent1q…xadl</a><br/>_________________________<br/><br/>Iiuc there are some rules for automated signing by the HSMs? Maybe it&#39;s there somewhere? 2026-09-06T20:49:01Z https://yabu.me/nevent1qqsgkg73umgq7hsv6973z38aye4q823fthyywhg2nhlp6dxjy9smuygpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4eg2llp63 In reply to <a href='/nevent1qqs9rwjxcda64levr9d87xgwpl685g8gr6hv447r6c97umr3ky08kygpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtc5nrx56'>nevent1q…rx56</a><br/>_________________________<br/><br/>Yes i was joking, but jokes should be a little closer to reality to be funny. Also this maybe isn&#39;t a great topic to joke about: *some* people, even if not nany, presumably lost money. Unless white hat is true , which I guess to be fair is a pretty decent chance. 2026-09-06T19:54:53Z https://yabu.me/nevent1qqszapva3ec5zf9d30dr9wu02pvq9eu7uhh3hzxxng43mft2as6sj0cpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egm9uzdu In reply to <a href='/nevent1qqsrhj4cnp5qkddnjs46qjwvvsmv7fyfeksdkht0vuq0ygp49kvvuhqprfmhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvuhsm657rz'>nevent1q…57rz</a><br/>_________________________<br/><br/>Disclaimer: not necessarily effective 😆<br/><br/>This is genuinely crazy though. All the people telling you multisig is the right security solution, might give you pause ... 2026-09-06T19:49:56Z https://yabu.me/nevent1qqsrhj4cnp5qkddnjs46qjwvvsmv7fyfeksdkht0vuq0ygp49kvvuhqpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4eghppxge Liquid rolling back the chain in 3.. 2... 2026-09-06T19:41:06Z https://yabu.me/nevent1qqspumtkjh2tlsspj9k2w36a6cmyhlrnwtawcfznlmzml38jwhzt6ccpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4eg822fxy In reply to <a href='/nevent1qqsvwmwqdpc6maxwuaxp8v3245p974e6avtnrwc7tff9tjn0yr7p64qpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtctqevud'>nevent1q…evud</a><br/>_________________________<br/><br/>Only whitelisted addresses can peg out iirc. 2026-09-06T19:40:37Z https://yabu.me/nevent1qqst3s0t926pq7v3j50ghuq7j8608dyxnhh9r0c7pkkpq90s85wnfrgpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egt8w8jt In reply to <a href='/nevent1qqs20lywgdxvturytkah5chsc23jcc9kduvnxjgulprqy7qn6wdf0egpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtckkavfp'>nevent1q…avfp</a><br/>_________________________<br/><br/>Well sure, not only does that risk always exist but, for now, it’s actually worse with AI-powered attacks. It might actually get better, in future though, according to the above argument. 2026-09-06T19:18:14Z https://yabu.me/nevent1qqs033ejlpycrveyrp22vudglacf0tma0pjd0j6akqyf6upny6u43qcpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egpu4p5s A little anti-doomer take for those of you (like me!) getting worried about AI. It&#39;s just a small niche but maybe the same thoughts could cross-apply to other areas of life:<br/><br/>I don&#39;t think it&#39;s very likely that AI will find classical breaks (as in, poly-time algos) to ECDLP. That&#39;s just an offhand intuition, but it&#39;s a very deep mathematical problem (factoring, also, though I guess that one is a bit safer). While at the same time, consider some of the big-picture problems - not hardness problems, but things we want to do, but can&#39;t - like functional encryption, indistinguishability obfuscation, fully homomorphic encryption, post-quantum analogs that don&#39;t have horrible tradeoffs, in cryptography. It&#39;s orders of magnitude more likely that AI will find *very* good solutions to those kind of problems. If they do, it will mean that things like Bitcoin become vastly more powerful, because vastly more useful. And the one thing that really underpins Bitcoin is not susceptible to some vast intelligence changing its character: energy scarcity. if you unlock a 10x on how much energy humanity has access to, obviously that changes a ton of things, but it doesn&#39;t change that energy is scarce. it&#39;s the finiteness that matters in proof of work, not the number. so short version: much *better* cryptography meaning much better bitcoin usability, is actually a pretty likely outcome. 2026-09-06T19:09:36Z https://yabu.me/nevent1qqswgayssk34gy5swx4vw08h4u33ll2tnpa3f525xr9u3w07cwpfm2cpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egff7gc9 In reply to <a href='/nevent1qqs9ppyk7snuppyqkwfmmds6rx9fzz8thhejyjnlr2rwd4258dnde2gpramhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvuhkjmnzdauq63uky7'>nevent1q…uky7</a><br/>_________________________<br/><br/>Your 2nd Q: the ability to transact offchain in a system with extra features is massive: better privacy, speed, scale and trustless contracts like options and dexes. Not saying you just get that all easily, some of it&#39;s hard and some near impossible. To get that for bitcoin without sacrificing trust is a kind of holy grail. Lightning got a small part of that, with some tradeoffs, and it already massively changed the usability of bitcoin as money. 2026-09-06T16:23:30Z https://yabu.me/nevent1qqsfavtal36jw4e6z5szj584mkqhss0ff8l98q3zkxf263r2esfka2cpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egzjksy7 In reply to <a href='/nevent1qqs9ppyk7snuppyqkwfmmds6rx9fzz8thhejyjnlr2rwd4258dnde2gpramhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvuhkjmnzdauq63uky7'>nevent1q…uky7</a><br/>_________________________<br/><br/>Exactly, they &#39;exist&#39; as per, anyone can write and execute the code right now, but it isn&#39;t usable for existing LN. Just trying to counter the tendency to assume that that means you literally can&#39;t design a system using them; you can. 2026-09-05T15:09:26Z https://yabu.me/nevent1qqs9tt79mvz3jjlhqwhru7m4rj3k44wy9930nahrn8gw44axkck8dcspr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egyly46g Why haven&#39;t people been working on arbitrarily complex contracts *inside* a Lightning channel?<br/><br/>Think BitVM but without the ugliness of what&#39;s needed to make dispute resolution work non-interactively onchain.<br/><br/>(Oh and btw we *do* have PTLC; anyone can deploy it in their own channel.) 2026-09-05T13:20:22Z https://yabu.me/nevent1qqsvervsq0sp6hng83a2prvsgxu4fyfwxkflpr9nxhlamcz3s4crk5cpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egtmasw2 You can bet signet coins at <a href="https://thimbly.org">https://thimbly.org</a> .. implementation of babilonia . need to use a psbt supporting wallet for signing, works with Sparrow and Core and should be taproot. Though i guess you could do it non-taproot but you need the psbt co-signing feature. paper and code are linked at the top of the page. This is just for demonstration purposes, the better way of doing it is p2p via a Core node, though this is perhaps more fun :) <br/><br/> 2026-09-04T20:15:15Z https://yabu.me/nevent1qqsr9th7nxcv4hcsnje42ns5ncdnu44cnfdxkqf9m32ckw2zt9knlyqpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egs50z3n In reply to <a href='/nevent1qqsdwpxyuyucntsszz0uyu94r0qm04w6a27tmlgcgxrs5d3epdnrhxqpz9mhxue69uhkummnw3ezuamfdejj7v6dm57'>nevent1q…dm57</a><br/>_________________________<br/><br/>It&#39;d be kind of normal to be fixed size. Just like a signature has a fixed size, so does a zkp. 2026-09-04T11:18:15Z https://yabu.me/nevent1qqszqmdc9c4w2yurevwh8g23xrnyly2yzhztdytrp5v2p5djtvjfnxqpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egaau7hj blockstream.info/signet lowest priority fee: 4277 sats/vb.<br/><br/>It&#39;s been drifting up. I guess something broke their end, I&#39;m kind of curious what, though. 2026-09-04T11:16:51Z https://yabu.me/nevent1qqsfksjqneujng4mmr8smsvllzlrxmle9aqg5jnu6ft7l7qxutwrw5gpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4eggvea6f In reply to <a href='/nevent1qqsped3uh0fqnn53gpk8zhkaj9j56hwksh4nlmpqy5ppcpmadnldfugdj0afv'>nevent1q…0afv</a><br/>_________________________<br/><br/>There&#39;s also plenty of precedent for government level reserves just getting swiped, especially by the USA (France historically, Russia more recently, though that was,USD), but also the UK (Venezuela case iirc). <br/><br/> 2026-09-03T18:01:41Z https://yabu.me/nevent1qqsr542qe27v9y0chjhjfg7gxcu40t9dauw05xsq4rcx4waz4nst5hgpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4eg8xyfa3 In reply to <a href='/nevent1qqs0anup90uzyma7rjvcmm9qa20z7c4hwdgw3t5k5kj9ksllld6ptpgc5tx8j'>nevent1q…tx8j</a><br/>_________________________<br/><br/>I tend to agree. <br/><br/> 2026-09-03T17:08:55Z https://yabu.me/nevent1qqst4zw6zytx26zq6ffuuqqgnh8qrgppa8sxrj9gx6ffafmcye9qs3qpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egmumj5u In reply to <a href='/nevent1qqs0w5wzmlaemutdgdpvlnyckhy9s7wxjjs49zxdqrt2c6wry4vtqsgprfmhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvuhs6k0u2v'>nevent1q…0u2v</a><br/>_________________________<br/><br/>Uh maybe it&#39;s not exactly the antipode of CSV exactly. There&#39;s nuance there. But setting that term aside, you get the point. 2026-09-03T12:14:25Z https://yabu.me/nevent1qqs0w5wzmlaemutdgdpvlnyckhy9s7wxjjs49zxdqrt2c6wry4vtqsgpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egz8qqfz In reply to <a href='/nevent1qqsy5u3zedwrxpvc2hpxplap7fuc9ehy2m6jdhggr0cy9f8l89jr4pcpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcxpta98'>nevent1q…ta98</a><br/>_________________________<br/><br/>They want 100% recoverability for a wallet, from the blockchain itself. This is the counterargument to client side validation. Not saying I buy it myself, but the argument can be made. 2026-09-03T12:13:04Z https://yabu.me/nevent1qqs0ahal799dn9f9wcpa8fdzpwpu3qx88zk5gtvnds22qfnxzd23jxqpr9mhxue69uhhyetvv9uju6r0v3kxymmpwfjzummjvupzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egkwekc7 So suppose that some people out there were developing a protocol for private payments on bitcoin that required 800 byte OP_RETURNs per transaction.<br/><br/>How would you feel about that? 2026-09-02T19:58:12Z