2025-05-22T21:28:25Z https://njump.cloud.vinney.xyz Murch https://njump.cloud.vinney.xyz/npub1j5mp526z5fkz9wkrk6mt5nzu43xndyrwkr8mnqngdqwytgcpc5vqcnsd5c https://image.nostr.build/df418427ee67a33f4ec3f33b953134656496f689184b964e7d9132018cdda414.jpg https://image.nostr.build/df418427ee67a33f4ec3f33b953134656496f689184b964e7d9132018cdda414.jpg https://njump.cloud.vinney.xyz/nevent1qqsf249hz0e8awt84xejg4znkzghrag9wpc87du9uw8kk57r03gt93szyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3s5xyqgv In reply to <a href='/nevent1qqs9xd3ysfanwxkmxsq9c8ucz2uafj3dna47c9eaudefen8hy5khkdss5vsfj'>nevent1q…vsfj</a><br/>_________________________<br/><br/>The account you&#39;re replying to is my personal account, or wdym? 2025-07-17T13:19:41Z https://njump.cloud.vinney.xyz/nevent1qqswtx92z84ptud3rzvz89e0fhxh52jtwrl0zctf5rj3fx57kvwvwyszyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sfr0fjn # UTXO set counts change between 2025-01-01 and 2025-07-14<br/><br/>P2A: +19<br/>P2TR: +28,167<br/>P2WPKH: -10,993,297<br/>P2WSH: +504,757<br/>P2SH: -1,892,424<br/>P2MS: +592,588<br/>P2PK: -600<br/>P2PKH: -6,881,365<br/><br/> <img src="https://image.nostr.build/4c1c84edf010fd56d42cf9f53c1d67b98b1655a7ef3fb79efb2d3fcca600cb78.jpg"> <br/><br/>## 2025-01-01<br/><br/>P2A: 1<br/>P2TR: 57,851,467<br/>P2WPKH: 56,806,770<br/>P2WSH: 1,627,820<br/>P2SH: 14,993,160<br/>P2MS: 2,016,773<br/>P2PK: 45,731<br/>P2PKH: 52,278,323<br/><br/>## 2025-07-14<br/><br/>P2A: 20<br/>P2TR: 57,879,634<br/>P2WPKH: 45,813,473<br/>P2WSH: 2,132,577<br/>P2SH: 13,100,736<br/>P2MS: 2,609,361<br/>P2PK: 45,131<br/>P2PKH: 45,396,958 2025-07-15T18:29:43Z https://njump.cloud.vinney.xyz/nevent1qqstjmqrhkwr2xefr4psptcvwhzr4e2fhfq4ctd67qs026s0vynulngzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3skn332v In reply to <a href='/nevent1qqsvn63m3y53tw3jx86nmzmpaxjk480m0l4pm83wqdunapxu8s8zhesfnftld'>nevent1q…ftld</a><br/>_________________________<br/><br/>That&#39;s too long for a vanity address. It looks like they burned the funds. 2025-06-18T14:29:26Z https://njump.cloud.vinney.xyz/nevent1qqszlplp0zkyv2urhzptpqxydg2lqdk0mjzmrc4qqp0jpxv9yyj6erqzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3srlpgsp In reply to <a href='/nevent1qqsx3m0k5kr6qg9p3saeq6wcxefyq9gyt4vh4czurwm5uv2qmjs5ttqsgwgnr'>nevent1q…wgnr</a><br/>_________________________<br/><br/>We currently have only translations to Japanese, Spanish, Czech, Hindi, Mandarin, German, and French, although not every issue of the newsletter is translated to every language. All the translations are made by volunteers separate from the people working on the English newsletter.<br/><br/>If there are some Portuguese speakers that would like to contribute to a Portuguese translation that would be welcome! 2025-06-06T19:28:17Z https://njump.cloud.vinney.xyz/nevent1qqsrfyxstyq9qdj2rcweczqgexeh82s7ahkwhne8wdzctsrj8n72mfgzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3s4aca8t In reply to <a href='/nevent1qqs2pd2y73k8ydl8xq8cxj5mlsgzrrlfwqq7geheklmq4k53elaneuq83rcnd'>nevent1q…rcnd</a><br/>_________________________<br/><br/>I can&#39;t stand the current regime, but I still support this piece of legislation. — I would prefer not to go to prison for working on the Bitcoin Core wallet. 2025-06-03T22:41:29Z https://njump.cloud.vinney.xyz/nevent1qqs0kpx8e5ha5dmeraxv5lfztyz0rxj3ylygcjty8e74l8npkehdpsqzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3s6yvl9m In reply to <a href='/nevent1qqspccwx06zsewqqefqt0amx24lz6xv3sr5cwc0lmyyypzct88ehnyquuqstt'>nevent1q…qstt</a><br/>_________________________<br/><br/>Yeah bots that repeat the same words in a weird order 2025-06-03T02:32:00Z https://njump.cloud.vinney.xyz/nevent1qqs8ecfkxq6jhecp4p46v4rqjg5csq373rpu6tc83krszvvh0xd3t0szyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sgv9enc In reply to <a href='/nevent1qqsv46rkczau5y8xe07nj5427rw7jvue4z65eqpngh7rfst2dqz9k2chphyjl'>nevent1q…hyjl</a><br/>_________________________<br/><br/>What we&#39;re doing is significantly improving the performance of Bitcoin Core with many releases.<br/><br/>Maybe you&#39;re just expecting a little much out of such a low-powered device?<br/> 2025-06-03T01:53:06Z https://njump.cloud.vinney.xyz/nevent1qqsxw8qtzxa88seftxemh43rwlr00z67yx997emmuw4d6c5qy7mqw4gzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sc2kt0s Okay, I&#39;m getting old or something, but can someone explain what people mean when they use the &#34;call me&#34; symbol: 🤙?<br/>Clearly it&#39;s not &#34;call me&#34; in the contexts that I&#39;m seeing it used. 2025-06-02T20:01:41Z https://njump.cloud.vinney.xyz/nevent1qqspzcf4qtcszsl5ygptw7r59zw5zus4uj7rdakgdndatxfl76tnvpszyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sa4ym9g In reply to <a href='/nevent1qqs24u7ah6mqakdhu9yfszjhy2st32yzpmegk76hh4sauwp89fjd77ggtrwlx'>nevent1q…rwlx</a><br/>_________________________<br/><br/>Correction, digital copy is not published yet, but coming soon 2025-06-01T01:59:54Z https://njump.cloud.vinney.xyz/nevent1qqs24u7ah6mqakdhu9yfszjhy2st32yzpmegk76hh4sauwp89fjd77gzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sdsy4v7 In reply to <a href='/nevent1qqsv7yuu7p7rateme5wv8jspccs0yawqy4qtwqhtdaqzmxs3mmtl0jq8mgq8p'>nevent1q…gq8p</a><br/>_________________________<br/><br/>It&#39;s free, you can find it on her website to print and assemble it yourself, or if you&#39;re lucky, you may get a handsown copy from Satsie herself, when you run into her at a conference or meetup 2025-05-31T23:18:04Z https://njump.cloud.vinney.xyz/nevent1qqspjsxcfvus07jz7ylpam2yew3wm5kk89nhku7z0kxq5ahqccx0y7qzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3szqqpwa <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/nprofile1qqsymaa58vaymd9enc7m444ap7zzyeexaltr4elqylu34j7erdxm5jqpp4mhxue69uhkummn9ekx7mqpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5qy8hwumn8ghj7mn0wd68ytnddaks2twca6" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>satsie</span> (<span class="italic">nprofile…wca6</span>)</a></span> made a splendid new zine! About Silent Payments this time. Check it out! <img src="https://image.nostr.build/6babb785cb90f2b0219a7c3f061e65c4558e6c0f4c8f6791fd0472ffc0b905a2.jpg"> 2025-05-31T17:16:11Z https://njump.cloud.vinney.xyz/nevent1qqsgumccnn2rpuvflxgwa4s6urp9c3t4n3z3g20znvt4u35qmaw9nmgzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3snvw2dv If you were at the Las Vegas #bitdevs today and you&#39;re owed the nitty gritty details of Pay to Anchor, TRUC transactions, 1p1c, and ephemeral dust, here is the Stack Exchange topic that was referenced:<br/><a href="https://bitcoin.stackexchange.com/q/126098/5406">https://bitcoin.stackexchange.com/q/126098/5406</a> 2025-05-29T02:14:42Z https://njump.cloud.vinney.xyz/nevent1qqsv0qu7t754c7e2z6kmuwls7dyqcyfy5tg38w5fn3fvw7fyg75qj9qzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3skvrjfl In reply to <a href='/nevent1qqsx2u8thx2y4d5slarq4chgf9r0pws76rkrj2cqtxv8293arpm8s7c4utkuc'>nevent1q…tkuc</a><br/>_________________________<br/><br/>I mostly follow your argument, but would posit that establishing a social convention can be meaningful coordination. I&#39;d also want to point out that there are a few more similar BIPs e.g., BIP176 and BIP179. 2025-05-27T14:53:37Z https://njump.cloud.vinney.xyz/nevent1qqsffkfckjxsndgteu74yf4xk8km2l7e4jr4fwx6ddn63v5fdjrzyeqzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3s7xsm9y In reply to <a href='/nevent1qqsydcxv48vdm44hrfa283n54n69ggflg7ryew6l7h2vejfssv23r4ce44uah'>nevent1q…4uah</a><br/>_________________________<br/><br/>I am not sure I get your point. There are occasionally some blocks that are completely empty, and sometimes miners accidentally include less transactions than are available, e.g. because they build a block with a recently restarted node.<br/>We also have recently cleared the mempool a few times, so at those times non-full blocks would have been expected. 2025-05-26T03:13:04Z https://njump.cloud.vinney.xyz/nevent1qqsg9pf8hgfevgh9vm8raz7v4gtn27hum5exju8p3vm3eftt7v42c9szyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3swstyxa In reply to <a href='/nevent1qqspxsd2jhszzspmzvfy7glx4lfzz3d9w9jxmwvzlgz4862pmzzrakgy0wz35'>nevent1q…wz35</a><br/>_________________________<br/><br/>There is a bit of a range between controversial and unserious. ;) 2025-05-25T16:18:17Z https://njump.cloud.vinney.xyz/nevent1qqs23yjf74yf40wcwcnqem6me8ycgedrlqmlhcede7xvxmysywxqhvgzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3s5p59yl Curious if this is an unpopular opinion:<br/>It was with too hard to get a BIP processed in the past and now people put BIPs on a pedestal. <br/><br/>But BIPs are author documents. Especially in Draft stage, they do not present community consensus — they&#39;re the authors’ personal recommendation to the Bitcoin community.<br/><br/>It seems good to me that we get a few controversial BIPs. It clears up that it&#39;s still the readers’ responsibility to make up their mind. 2025-05-25T15:49:23Z https://njump.cloud.vinney.xyz/nevent1qqsqavgqxjhn4mhmspypdvtj5ejyvkmgjkedgw57fv669ke7ldfwn4gzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3syuw9a5 In reply to <a href='/nevent1qqstqvhj2fj5gk5dege2r897geu2kuy7hzxcuawjhd9wrqfa52yvwuq29gj53'>nevent1q…gj53</a><br/>_________________________<br/><br/>It was with too hard to get a BIP processed in the past, and now people put BIPs on a pedestal. <br/><br/>But BIPs are author documents. They don&#39;t present community consensus, they&#39;re the authors’ personal recommendation to the Bitcoin community, especially in Draft status.<br/><br/>It&#39;s good that we get a few controversial BIPs. It helps to make it clear that it&#39;s still the readers’ responsibility to make up their mind. 2025-05-25T15:47:05Z https://njump.cloud.vinney.xyz/nevent1qqsymsan4v6jn8cvv6trs4g44md0c2lp2d58hfg60k4vhr4m5vsr8vgzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3s4nmcgn In reply to <a href='/nevent1qqstqvhj2fj5gk5dege2r897geu2kuy7hzxcuawjhd9wrqfa52yvwuq29gj53'>nevent1q…gj53</a><br/>_________________________<br/><br/>It was with too hard to get a BIP processed in the past, and now people put BIPs on a pedestal. <br/><br/>But BIPs are author documents. They don&#39;t present community consensus, they&#39;re the authors’ personal recommendation to the Bitcoin community, especially in Draft status.<br/><br/>It&#39;s good that we get a few controversial BIPs. It helps to make it clear that it&#39;s still the readers’ responsibility to make up their mind. 2025-05-25T15:39:12Z https://njump.cloud.vinney.xyz/nevent1qqswxkhcrp68tazpcfeluuxgncrpgyk2tvaw8huv02jedyd6uk4j53qzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sw4chl0 In reply to <a href='/nevent1qqstqvhj2fj5gk5dege2r897geu2kuy7hzxcuawjhd9wrqfa52yvwuq29gj53'>nevent1q…gj53</a><br/>_________________________<br/><br/>It was with too hard to get a BIP processed in the past, and now people put BIPs on a pedestal. <br/><br/>But BIPs are author documents. They don&#39;t present community consensus, they&#39;re the authors’ personal recommendation to the Bitcoin community, especially in Draft status.<br/><br/>It&#39;s good that we get a few controversial BIPs. It helps to make it clear that it&#39;s still the readers’ responsibility to make up their mind. 2025-05-25T15:32:53Z https://njump.cloud.vinney.xyz/nevent1qqs0dtvpg8d4q2h8tned22lryalg4l3085ksrws7ajus6hyjsddgn7czyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sv45zky In reply to <a href='/nevent1qqsdhe37yldprmc70xwqu9n2yfxkuu76qm7htje87fertc2hj3hh7jqhlupmq'>nevent1q…upmq</a><br/>_________________________<br/><br/>Not just the normies 2025-05-24T22:28:53Z https://njump.cloud.vinney.xyz/nevent1qqsgc7drt5cx6fp7u2gfr3kmszqzru2mkqkaqu26de0kcwq78am6ukqzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sw75cp5 In reply to <a href='/nevent1qqsxdlvz2vu8hrmm6mz3xurqv6a0sjwyxne0eknzp6jpqt455v9hr8qzl7wvs'>nevent1q…7wvs</a><br/>_________________________<br/><br/>So, what you&#39;re saying is that we have not been selective enough for accepting recent submissions? 2025-05-24T15:53:31Z https://njump.cloud.vinney.xyz/nevent1qqsd7dsrhzwr5lqmx3spx2m5av6e6un8veuj4hfscp6fgjvkwungsrszyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3st3pwnd In reply to <a href='/nevent1qqsg35f2jvpm8n7273a2nyrmu4nqfephfds7kthqj4mkc76tf6p68cg5qx7ut'>nevent1q…x7ut</a><br/>_________________________<br/><br/>Software update broke my desktop at work and I got stuck way later fixing it, just picking up my pizza. 😁 <img src="https://image.nostr.build/e1c3125474fe293a279641e83d6b184d1ccc17a08d77b2a0434a18394c565eb9.jpg"> 2025-05-23T03:40:49Z https://njump.cloud.vinney.xyz/nevent1qqs9nm7r3d4g768mfw89xw5p8ucza4hlvhtdnvwsklqrh7c7ktysu5szyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3spty0x8 In reply to <a href='/nevent1qqswl679rw2wd4kmwqazcp5tqv0lmn9dx6d06x7hfnqg38znhdwkxas82xff7'>nevent1q…xff7</a><br/>_________________________<br/><br/>Whatcha writin&#39; about? 2025-05-23T03:27:31Z https://njump.cloud.vinney.xyz/nevent1qqsfstdr3ymczqrhtsr3tf50z5909su2jkhc7l90pe9y3xvjtrzhrzqzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sz4x7pl In reply to <a href='/nevent1qqsx78dxt30anvdcewvtk79pscqt0zxjt2k0y20qmmmn9vdvcjk89rcu96hj9'>nevent1q…6hj9</a><br/>_________________________<br/><br/>What is the second one? I got BIP77 and I&#39;m drawing a blank for the other. You cooking something? 😉 2025-05-23T01:24:43Z https://njump.cloud.vinney.xyz/nevent1qqspgze57hns652gga9jef37rt90czavm7y99zjq7g3pmzl980f6m7gzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3s6v4tvd In reply to <a href='/nevent1qqs88dmhhfyjtp2npunvmywtcyd792rkflxp5t39a27500awvaaw0ls9jxh6v'>nevent1q…xh6v</a><br/>_________________________<br/><br/>Would that work from amethyst, or do I need to operate the wallet from the website? 2025-05-23T00:34:31Z https://njump.cloud.vinney.xyz/nevent1qqst20gf3rq306lgz2t9wj4qw3885qka44ew8mvh0e95xr2wuncxs2czyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sz2hcjh In reply to <a href='/nevent1qqs03qmtn4cj7rgs8sag990e7lhe5rhvtzuwgtj394sywue50c6px0q3a6qhe'>nevent1q…6qhe</a><br/>_________________________<br/><br/>Thanks, let&#39;s dive in, shall we? <br/><br/>What issue were you experiencing with the Pi4? <br/><br/>I&#39;m asking because there is a common misunderstanding that the entire UTXO set needs to fit into RAM, but that is not the case. The UTXO set is mostly stopped on disk. You only need a couple gigs of RAM for Bitcoin Core to run decently, although more is certainly helpful. UTXO set growth means slower IBD and generally more disk reads during validation, but it&#39;s a graceful degradation, not a cliff. 2025-05-23T00:30:12Z https://njump.cloud.vinney.xyz/nevent1qqst9snh3ht586lz4pa4tp6snsckq2dqhd0x7uz38ej290742lxrm0qzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sep433h In reply to <a href='/nevent1qqsd0qusdvcst9fyk5exa5nfdtrmk4ppef2jvhs8xtc6zv9jrzz566cqk986e'>nevent1q…986e</a><br/>_________________________<br/><br/>Mh, still ob the fence whether to bother with yet another social media platform, so I&#39;ve put little effort into seeing it up so far 2025-05-22T20:15:02Z https://njump.cloud.vinney.xyz/nevent1qqs8rvrekwdth8744ck2hsn8z3gaxuwx993yljhr0rsd360gu5v0w6gzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sva5yan It&#39;s raining BIPs, hallelujah...<br/><br/>Recently merged:<br/>BIP53<br/>BIP54<br/>BIP172<br/>BIP177<br/>BIP321<br/>BIP443<br/><br/>On the cusp:<br/>BIP77<br/><br/>Maybe a good time to remind that BIPs are author documents that represent the authors’ recommendation to the Bitcoin community. 2025-05-22T04:26:22Z https://njump.cloud.vinney.xyz/nevent1qqsv6dg2s94uv0s2ju2e26csk2ezwgxw5mqdrf38f2rug0v5frdd8ugzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sxnys9m In reply to <a href='/nevent1qqsteq8das9ugw86xs9x02gss457glcmlgesrrwrzd8uvxx229x5ucq2gsc83'>nevent1q…sc83</a><br/>_________________________<br/><br/>Ocean had only found 11,895 blocks, and that&#39;s if you count the ones found by Eligius. 2025-05-22T00:16:10Z https://njump.cloud.vinney.xyz/nevent1qqsp5fks5fq0fs6t2n4y3rqhtr2fkv46cqj8avu4xw7v733484lq75czyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3stxnx3q In reply to <a href='/nevent1qqszeywmlpgs7aqxxn63t3p2z9733gzxhrj6nt9vzqkc3hn9d25s9psz38r0m'>nevent1q…8r0m</a><br/>_________________________<br/><br/>Thanos for being open to this conversation 2025-05-22T00:08:10Z https://njump.cloud.vinney.xyz/nevent1qqstnyqu37uwmluqzeq6f4upeawu30hgv25dy66cqlmyzjhthgahzwczyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sr87gys In reply to <a href='/nevent1qqswr8dfwh4j29ful3eypxgv6n2n0r9a463kl4j8h22jgz3qlyvnfacqwn0gx'>nevent1q…n0gx</a><br/>_________________________<br/><br/>A lot to unpack here.<br/><br/>&gt; The fact they will remove the option for us node runners to decide what will go trough our nodes is shady. I want option to change OP_RETURN value in settings. <br/><br/>The latest version of the pull request only deprecates, but does not remove the configuration option.<br/><br/>&gt; Increasing the Blockchain size by allowing arbitrary data transactions. It&#39;s true they&#39;ll pay more but that won&#39;t stop them and major miners arent against that. <br/><br/>OP_RETURN data is written to output scripts. Output scripts are not subject to the witness discount. More OP_RETURN data would likely reduce blockchain growth, so as I was asking in the above post, I am not sure where this idea is coming from.<br/><br/>&gt; The cost of running a node will increase because 2TB drive will not be enough if they keep spamming the Bitcoin.<br/><br/>Blocks are limited to 4&#39;000&#39;000 weight units. OP_RETURN data bytes weigh four weight units, so a block filled with OP_RETURN outputs would come in close to 1MB, which is significantly less than the latest 30-day average of 1.64 MB. It’s unlear to me how more OP_RETURN data would increase the blockchain growth.<br/><br/>&gt; Look at the Ethereum for example. Their full archive node requires 12TB of disk space I believe. It might be even more today. And even they have OPTIONS to run 3 kinds of nodes. <br/><br/>No clue, they have made a lot of strange decisions, but I don’t see how it’s relevant as the things that lead to bloat there are completely different.<br/><br/>&gt; I&#39;m not seeing the reason why in the hell #Core devs need to remove this option. Leave it there. I&#39;ll decide how much shit I want to broadcast.<br/><br/>I think there have been several books worth of explanations written at this point, so I don’t think it’s useful to elaborate, but if you are earnestly interested, I can provide a few links.<br/><br/>&gt; I hope people won&#39;t blindly update to new core 29 release after knowing what that brings.<br/><br/>Bitcoin Core 29.0 came out in April and did not change the OP_RETURN limit. If the currently open pull request should get merged, the change would at the earliest be released with Bitcoin Core 30.0 in October. 2025-05-22T00:03:58Z https://njump.cloud.vinney.xyz/nevent1qqsyd9s2puecnued6tgelfq2g8cntdqvp8fessgyf63rryrh2cnywmgzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sk2n7y9 In reply to <a href='/nevent1qqs9gxt4n0ghsp0y8mrpuevgqknzd02lt9ufgwmu2qutp8s07w6lmvc59shrn'>nevent1q…shrn</a><br/>_________________________<br/><br/>That feels unfair, I didn&#39;t say I didn&#39;t want to talk to you because you were a &#34;normal node runner&#34;. I indicated that your answer did not match the topic I asked about.<br/><br/>I get that people don&#39;t like data in the blockchain—I&#39;m not excited about that either—but I&#39;ve already heard all about that for the past two weeks. Here, I&#39;m specifically trying to I understand why people argue that OP_RETURN transactions make nodes more expensive to run. I don&#39;t get where that is coming from or what the line of thought is. 2025-05-21T05:20:45Z https://njump.cloud.vinney.xyz/nevent1qqsg5m2zzfny60thu7ujdxmytcx45j7mf6phm33p8qrvxvpcj76h20qzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sclax8c In reply to <a href='/nevent1qqsgkkeefwv4vqjz2c4xkrv0gmh60tmq9tjm4zrx9td42nnrezet5ccn75jpz'>nevent1q…5jpz</a><br/>_________________________<br/><br/>Okay, do you also have an opinion on what I asked? 2025-05-21T00:48:01Z https://njump.cloud.vinney.xyz/nevent1qqsyw7a5ygsjdrqqj97s3zyqygjz6kqm0y9g6sznetjk4xfx6tq47zqzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3s8cr6jf In reply to <a href='/nevent1qqsyftr02gpfa4hl0df0wm7g0y0zvdu3z78w36tsqs5wfcg6hspr5ec2myk5l'>nevent1q…yk5l</a><br/>_________________________<br/><br/>&#34;Never to STFU&#34;? 2025-05-21T00:08:26Z https://njump.cloud.vinney.xyz/nevent1qqsfvk8qk5cavtm7p4wzecg5gelngwfrtcp2y8xsrd2a2gamu70zgxszyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sa5m2mg Does someone want to explain to me how OP_RETURNs increase the blockchain growth, hardware requirements, or otherwise increase the cost of running a node? I keep seeing that concern, and that seems completely counter my expectations. I&#39;d love to see a detailed explanation of how that follows. 2025-05-21T00:07:35Z https://njump.cloud.vinney.xyz/nevent1qqsz0u9s69zs7rwal8xpwx2rtctrm0qax2gx50cta54nw469u5n6tpqzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3slm7zvj In reply to <a href='/nevent1qqsr4kwdp9uyq8t7jgdh45jku56w6urd29pwctqsj7gvnw708l6fd4sqa3z27'>nevent1q…3z27</a><br/>_________________________<br/><br/>Nice strawman, hope nobody torches it 2025-05-20T23:38:54Z https://njump.cloud.vinney.xyz/nevent1qqsg6lm5qrynzfumm6cdnl8k0w66gskdvhcq9ypq4chztf6prtlg9mgzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3su2y5t3 In reply to <a href='/nevent1qqsyxlay6jh4zq3h73vnkd6ra7n5z4g77dg9n6wlxpdterajq6ek2jgklt85c'>nevent1q…t85c</a><br/>_________________________<br/><br/>For context, Bitcoin Core has something like 240&#39;000 lines of c++ code.<br/>I don&#39;t intend to take the time to go through someone of that magnitude, but if you want to take a look, here&#39;s the diff: <a href="https://github.com/bitcoin/bitcoin/compare/28.x...bitcoinknots:bitcoin:28.x-knots">https://github.com/bitcoin/bitcoin/compare/28.x...bitcoinknots:bitcoin:28.x-knots</a> 2025-05-20T23:16:25Z https://njump.cloud.vinney.xyz/nevent1qqsd9h3yau0zzev5zel30jkztvhluw9us6anhnvlqj28wxqc9runa8qzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3s5cp2ts In reply to <a href='/nevent1qqs28lq5xmm9cptv2e0njgg39mgdp0r9awl2l32xswtvxrw54s8wt3c03rpnr'>nevent1q…rpnr</a><br/>_________________________<br/><br/>Hey Leon,<br/>thanks for your reply. Given the many points you raised, I will quote for context what I’m replying to.<br/><br/>&gt; Leon wrote:<br/>&gt; What I don&#39;t understand is why the limit for op_return is being changed when filters are actually working. Yes they don&#39;t filter out everything but they do filter out most of it. <br/><br/>I am puzzled how you arrive at the conclusion that they &#34;filter out most of it&#34;. 53% of transactions over the past year had OP_RETURN outputs or inscriptions. Could you perhaps explain further what effect you perceive filters to have had?<br/><br/>&gt; Leon wrote:<br/>&gt; Then you have a couple of folks claiming that filters are useless and we should give up on them entirely because spammers could use out of bound transactions via services as slipstream by MARA to circumvent filters (which is right but also proves that filters are working pretty well since they wouldn&#39;t need to go out of bound otherwise).<br/><br/>Some miners appear to be running Libre Relay or have otherwise loosened their mempool policy. These miners accept transactions considered non-standard by default Bitcoin Core configurations in-band. They appear to track them normally in their mempools, and include them in their blocks whenever those transaction’s feerates put them in the block. The myth that non-standard transactions need to pay a multiple of other transactions appears to be based on the OP_RETURN_BOT service charging a premium and sending at a higher feerate, but if you are willing to wait, non-standard transactions appear to be getting confirmed at the same feerates as any other txs.<br/><br/>&gt; What puzzles me as well is the statement that transaction fees are enough to filter out spam. You might be right with this claim but I am not sold on it entirely.<br/><br/>Given limited blockspace, it is obvious that transaction uses that can afford to pay more for blockspace will price out transactions that can only afford to pay little for blockspace. This means especially that large value transfers have a much bigger budget to pay for blockspace than small transfers (if you are sending 10 ₿, you don’t care about paying 10&#39;000 sats in fees, but if you’re trying to send 10&#39;000 sats, paying 10&#39;000 sats is prohibitive). This isn’t a new observation, I wrote in 2016: &#34;Transaction fees are not in relation to the amount of value transferred, but in relation to the amount of block space they&#39;ll take. Therefore, it is relatively cheap to send large amounts of value in Bitcoin but uneconomical to send micro-payments.&#34; (via <a href="https://bitcoin.stackexchange.com/a/48422/5406">https://bitcoin.stackexchange.com/a/48422/5406</a>). I’m not sure what your expectation is, but any form of Bitcoin succeeding will mean that small payments will be economically infeasible on chain. In the past couple years, we saw the third hype wave of people using Bitcoin for publishing data. Just like the prior two times, the excitement eventually subsided and as the premium came down, the cost curbed the transaction volume. Even at the peak of the hype, large transfers easily price out this sort of use. If you are upset that small payments were priced out, I’m afraid that’s the expected outcome either way. I don’t see the point in lying to Bitcoin users by trying to keep transaction fees low artificially.<br/><br/>&gt; Leon wrote:<br/>&gt; As long as bitcoin evolves the way as projected and increases in global significance a lot more folks might want to spam the chain even though fees would be higher at that point the incentive for spamming and using more resources to do so would grow similarly.<br/>&gt; In general I think spam is harmful and might lead to unintended consequences so I don&#39;t think we should give non monetary transactions more room and easier ways to use the protocol.<br/><br/>OP_RETURN outputs do not grow the UTXO set, because they do not get added to the UTXO set. They are easier to validate than payment outputs, because they don’t contain signature operations. Since OP_RETURN data is in output scripts, it has no witness data that would be discounted. As far as I can tell, besides competing for blockspace, they use less resources in every way than other transactions per byte.<br/>Inscriptions also do not increase the UTXO set per se, because it takes creating an output and spending an output to publish the Inscription in the input’s witness stack. Witness data is validated once and retained with a full copy of the blockchain or discarded by pruned nodes as any other blockchain data.<br/>It seems to me that most of the UTXO set increase is due to Ordinals—the notion that satoshis have a serial number and some of those serial numbers are more valuable than others—and users splitting up UTXOs to isolate satoshis with certain Ordinals. Sometimes inscriptions are attached to Ordinals, but I’d still blame that on Ordinals more than on Inscriptions. The transactions that split UTXO amounts to isolate certain Ordinals are indistinguishable from payment transactions without out-of-band information about Ordinals, so the main UTXO set bloat is not easy to filter.<br/>So, overall I see UTXO bloat from Ordinals and blockspace demand by transactions that offer to pay more for blockspace. I don’t see a practical way of preventing Ordinals, and don’t perceive Inscriptions or OP_RETURN outputs as particularly harmful (dumb sure, but not harmful). Perhaps you could elaborate how spam is harmful, if you disagree, because I don’t see it.<br/><br/>&gt; Leon wrote:<br/>&gt; I said core seems compromised because they would not ship many &#34;controversial&#34; implementations in the past but this time when controversy is obvious as you can tell from the debate they don&#39;t care and ship anyways.<br/><br/>I don’t know which examples of controversial changes that did not get shipped you are referring to, but the ones I recall were sunk by convincing technical arguments against them. I have yet to see a convincing technical argument against raising the OP_RETURN limit. 2025-05-20T23:00:54Z https://njump.cloud.vinney.xyz/nevent1qqsw4cs5akv87jq4e9m2qf97jzt8d8hcxw9gjjd84q50ufw8etwmfyczyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sxlmzt6 In reply to <a href='/nevent1qqs8recjy8c6pfk03wsnjxqwlnx9r6fhl3u23qntrzauy3dr0uwu2zgtjlmwt'>nevent1q…lmwt</a><br/>_________________________<br/><br/>P2TR keypath inputs weigh 230 Wu (57.5 vB), so P2TR outputs with 1000 sats are economically spendable at feerates up to 17.3 sats/vB. 2025-05-20T16:10:47Z https://njump.cloud.vinney.xyz/nevent1qqszux558wvlkv5frdvfdcpx5cvgqwxuvcne5dl3295ks6c7ckp8y5czyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3su4hxma In reply to <a href='/nevent1qqsptfmrd55v7cu49q23zsnec76dhcwp5qu2jcej9j4xz34ahml9twqqn0u8h'>nevent1q…0u8h</a><br/>_________________________<br/><br/>Would you like to share your concrete concerns, so I can address them?<br/>I have not received any money or other incentives to have a specific position in this matter, not am I aware of any other participants in this discussion being paid to represent a specific position.<br/>To me the arguments for lifting the limit make sense by themselves. My skepticism to the viability of filtering transactions with significant demand aren&#39;t exactly new, I pretty much write the same thing on last year&#39;s pull request for &#34;match more data carrying&#34; which I found to be similarly poorly motivated. 2025-05-19T23:42:15Z https://njump.cloud.vinney.xyz/nevent1qqsz0dk67f0aufgmkv48uxde07u9nmxxyg4fef96ep8sqdzxzed0hkqzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3s9xjpek In reply to <a href='/nevent1qqst3q2rgzs0jc236umupyqmdykyh8le995h9jw0tldge0lz6yp586q8p5duc'>nevent1q…5duc</a><br/>_________________________<br/><br/>New major versions are only released twice a year, in April and October. Even if the PR were merged, which it has not yet, it would not be released until Bitcoin Core 30.0 is released in October. 2025-05-19T16:48:04Z https://njump.cloud.vinney.xyz/nevent1qqspkpsfs4mkgpd02ydcfrfgdlyl7a02er34cplc95qmsz8x2g257agzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3s3zq7a7 In reply to <a href='/nevent1qqstwuhsrm0uhfapyf6qvzxckd78yvjtkmdv6ju7llutkp0qsend7mgnaz3mx'>nevent1q…z3mx</a><br/>_________________________<br/><br/>If a pull request doesn&#39;t pass review, the reviewers leave feedback on what to improve until it becomes ready for merge or work on it is discontinued. When pull requests run into well-reasoned opposition they tend to get closed to curb review time spent on things that are unlikely to be merged. 2025-05-19T16:44:17Z https://njump.cloud.vinney.xyz/nevent1qqs027d6rugwaz3r6gpw0hlnx2zmz88j0a37rqgnz4a0t3x4gkjcq8szyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3s30tfnm In reply to <a href='/nevent1qqsqhzgtm9g2l8trn62wszauq50f7heug5242uxvyqlguvq7vyjnz0gkjgecd'>nevent1q…gecd</a><br/>_________________________<br/><br/>No, I did not conflate contributors and maintainers. In Bitcoin Core nothing gets merged until it has been reviewed by several regular contributors, usually several times. Sure, one of the five maintainers (who are part of the regular contributors) is usually the last reviewer and will merge a PR if it has had enough review and they&#39;re satisfied, but they don&#39;t merge things that haven&#39;t been reviewed by other knowledgeable developers, mostly from those 40 regulars. 2025-05-19T14:57:29Z https://njump.cloud.vinney.xyz/nevent1qqsrs50qp0csnf3d3vkawmfhfs0vd727e3wquz9upcqhrgq4jtyn8dqzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3s2alj02 In reply to <a href='/nevent1qqsxzx9d2l6shxhvumaljx508rwsuk0hf6ezcfaaj6m5dnqxk40lg9cf5r90s'>nevent1q…r90s</a><br/>_________________________<br/><br/>It might make more sense when you consider that neither Peter nor myself is speaking for Bitcoin Core, but that birth of us are just presenting our own opinions. 2025-05-19T14:40:44Z https://njump.cloud.vinney.xyz/nevent1qqspma0m58cgmc457r6jdcwnt6zx3ay243wunqu6pftj720muntqm9szyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3s2m9f8t In reply to <a href='/nevent1qqswt3zqrzc29w4mpvqdv7jh3ytyladmmwpg0urvakd0agv6s79hp9sfhxq9z'>nevent1q…xq9z</a><br/>_________________________<br/><br/>Murch didn&#39;t talk about the OP_RETURN limit at all in that post, he was addressing claims that Bitcoin Knots has more developers than Bitcoin Core.<br/>If you want to know my thoughts on the policy change, I&#39;ve left a comment on the PR. 2025-05-19T01:57:04Z https://njump.cloud.vinney.xyz/nevent1qqsxtjmlgsemzefr9r75xjt3cm5hc63vscgngl8u276tfu8sjrgnwlqzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3smv5lcp In reply to <a href='/nevent1qqsr3u2q08gx42dc8lqzpu9748r80zqms03dg5yjkw4cuke5hf3c5pgahndh6'>nevent1q…ndh6</a><br/>_________________________<br/><br/>About 28,000 differing lines of code across 550 files and 1400 commits 2025-05-17T16:52:05Z https://njump.cloud.vinney.xyz/nevent1qqsdy9556ffmk7klajk3nymd4rxsa88jnfcfvhc8vu0eqwfyr5vthfczyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3shkgj78 In reply to <a href='/nevent1qqstw532c6g3u36wluejwks9m6nmfrx2d76vw73vl3er9exert8yhkswt2uaw'>nevent1q…2uaw</a><br/>_________________________<br/><br/>Is that a gut feeling, wishful thinking, or did you see anything specific in that repository that indicated review activity? 2025-05-15T21:51:56Z https://njump.cloud.vinney.xyz/nevent1qqsp2x3m8g8gzhtmdvs2utrgctcesd96pg02hn24nhxjh65l8n8xjkgzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3s8kmcvd In reply to <a href='/nevent1qqszepuwwmwwaht6n9v5wgs6gxt5ma5dgjvprsuhq74fuzr0huqjrygx8nr59'>nevent1q…nr59</a><br/>_________________________<br/><br/>Yeah it isn&#39;t much, just about 28,000 lines of code difference across 550 files and 1400 commits. <img src="https://image.nostr.build/5be4acb9eb8e563bf409bad25f6594b157eb862fedce6c9411c564477979a433.jpg"> <br/> 2025-05-15T21:34:48Z https://njump.cloud.vinney.xyz/nevent1qqsgju3d5jc7c4x96z9yat2z2qzjz09vctmxfl4glv9z37jajxdyjdgzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3scntppr In reply to <a href='/nevent1qqsdqm9lluzemfd6p5rhyfxy0m9rcp4x0627lpm8jlhpestjk9lnqdguhmdl7'>nevent1q…mdl7</a><br/>_________________________<br/><br/>See <a href="https://njump.me/nevent1qqsqgqshlvle5f0ud0xvaadcytfest4mv47hr2j9fsrlpf67c7mwprspr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgsf2ds69dp2ympzhtpmdd46f3w2cnfkjphtpnaesf5xs8z95vqu2xqrqsqqqqqplc5wt9">https://njump.me/nevent1qqsqgqshlvle5f0ud0xvaadcytfest4mv47hr2j9fsrlpf67c7mwprspr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgsf2ds69dp2ympzhtpmdd46f3w2cnfkjphtpnaesf5xs8z95vqu2xqrqsqqqqqplc5wt9</a> 2025-05-15T21:17:10Z https://njump.cloud.vinney.xyz/nevent1qqsx5nj3hk6rw9rkg2km04yhhduxulvyzf8ympg2w6t22pqsjzvhwggzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sy02td2 In reply to <a href='/nevent1qqszsmdmkk6vfvepcacau6l572e94026lv2md3we733503n5kw5ygfs9eny79'>nevent1q…ny79</a><br/>_________________________<br/><br/>Witness data is discounted by a factor four not three, but yeah, OP_RETURN data takes more blockspace and is more expensive to the same degree. Either way the sender pays for whatever blockspace they win the bid on. 2025-05-15T21:12:00Z https://njump.cloud.vinney.xyz/nevent1qqs0g02zzgq8h496uvxrkz2s2umh2kllk056ygrf4c4tu835sfte2lszyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3s0tyms8 In reply to <a href='/nevent1qqswywx8g394gs0kmzm6sc96ffjqtyapanua9n0mdmwzuxwuv63ljlqyyxag6'>nevent1q…xag6</a><br/>_________________________<br/><br/>Yes, that&#39;s correct. Small data payloads get slightly cheaper. It just seems that people are much more concerned about big amounts of data and those are significantly more expensive with OP_RETURN. Either way, data occupies whatever blockspace the transaction bids the premium for. 2025-05-15T21:09:19Z https://njump.cloud.vinney.xyz/nevent1qqspm8k2kspxzfmge9v3q274uwxt7c7wfy86nmcm70glup3jhqkn52qzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3syu7qyh In reply to <a href='/nevent1qqs9uxw9n5j2nnjtjkjg3qgnd32g3ypurvnslqflzu4exslkcaap38crv95cz'>nevent1q…95cz</a><br/>_________________________<br/><br/>Theoretically you could have done the same reveal truck with p2sh, but the redeem script had to fit into a single 520 byte push. Segwit introduced the witness section and witness discount, Taproot removed the 520 byte limit for witness stack items. Altogether, you could then do big scripts for less in the witness. 2025-05-15T20:47:04Z https://njump.cloud.vinney.xyz/nevent1qqsrxal64w848a64j7x57th2hqzx5vny9lrcem8u5tjh84daflwnf4gzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3smvehu5 In reply to <a href='/nevent1qqs08z0zf3fatdfgl2t9sxm8ceejhpkt7wdma8kcgfraukzezaz6dxsjyfl3p'>nevent1q…fl3p</a><br/>_________________________<br/><br/>The main reason to do it is the same reason as 2013: it&#39;s preferable for people to write into op_return outputs than into unspendable payment outputs. Dropping the limit makes OP_RETURN a reliable replacement for the latter which is currently standard and essentially unpreventable.<br/><br/>Data in OP_RETURN is significantly more expensive than data in inscriptions, so I have a hard time understanding the concern that the overall block space occupied by data transactions would increase.<br/><br/>Whether more should have been done about inscriptions seems like a separate debate that mostly muddies the water here. 2025-05-15T18:22:01Z https://njump.cloud.vinney.xyz/nevent1qqs096cpgerfaysjrjx7hwhr82thnf0h0fzga0u6ws5nr9kfxeerfdgzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sp42scq In reply to <a href='/nevent1qqs05pfzfgcty468wmf67y3xpt33tysvtpv3fvt7mr8umd58a36qq0sngtjgz'>nevent1q…tjgz</a><br/>_________________________<br/><br/>Biometrics are user IDs, not passwords. 2025-05-15T18:13:52Z https://njump.cloud.vinney.xyz/nevent1qqsz8a672xyas6ecrewx5ztncljaug3ljealg2v6c3t443zj4m7y4dczyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3s3h8dhc In reply to <a href='/nevent1qqs0th50kva8pedhhv566d5qqxkjn5zz7jvs6m34jc85p9fdygdj6wgp9mq3l'>nevent1q…mq3l</a><br/>_________________________<br/><br/>Bitcoin Core currently estimates feerates based on the time transactions of various feerates spend in the mempool before they appear in blocks. We ignore any transactions that we have not seen in the mempool.<br/>We also have work in progress to estimate feerates based on the transactions in the mempool. <a href="https://github.com/bitcoin/bitcoin/issues/30392">https://github.com/bitcoin/bitcoin/issues/30392</a> 2025-05-15T14:55:18Z https://njump.cloud.vinney.xyz/nevent1qqsrns6t2psnz2f78pc7v7qp340jw73ctcuzqmy26rpzs6e7lvam0hqzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sgzhe60 In reply to <a href='/nevent1qqsz8a60s4044vxe9mul53vyasvafrz3q5qmcgvhrylef5mj2vg4z3qpmzvmk'>nevent1q…zvmk</a><br/>_________________________<br/><br/>1. I don&#39;t understand why people think Peter Todd is a regular contributor to Bitcoin Core. I don&#39;t think I&#39;ve seen him make that claim, I&#39;ve certainly not seen other contributors make that claim, and as far as I can tell, he has made three commits since 2016.<br/> <img src="https://image.nostr.build/c12a73d4e689ab00cfe4c16a1f0cba822f06d7467c42c2e6abf7f1e5e5272bc9.jpg"> <br/><br/>2. You will have to ask Peter why he said that and how he meant it. 2025-05-15T05:20:19Z https://njump.cloud.vinney.xyz/nevent1qqs8lmy3nwcgtyze3ueh598ptt6690q0qsm4l98e5g2z7m97lmxlc9qzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3slhpuhk In reply to <a href='/nevent1qqsq84e0gmmrsnz4lp28kd6pj97887hrq74w689j0ne5g60jx8nthpcd20hq5'>nevent1q…0hq5</a><br/>_________________________<br/><br/>*restating 2025-05-14T18:07:20Z https://njump.cloud.vinney.xyz/nevent1qqsq84e0gmmrsnz4lp28kd6pj97887hrq74w689j0ne5g60jx8nthpczyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3skesg0a In reply to <a href='/nevent1qqspc9hrt2eejcuslt5dqgxmd7vecwzsm0njk3pg49549l87r5v49ks7x06e7'>nevent1q…06e7</a><br/>_________________________<br/><br/>No, people contributing to the upstream project are part of the process in the upstream project. Their review also benefits the downstream project as their code contributions are released with the downstairs project, but they are not participating in the downstream project&#39;s process.<br/><br/>Your restarting it like this makes me think that the distinction is not clearly understood. 2025-05-14T18:06:46Z https://njump.cloud.vinney.xyz/nevent1qqs294732cl6rjn77x0gvx8afszw4yjtuezcjtd32aerqkd7f56n26gzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3shmwp4d In reply to <a href='/nevent1qqsyx9csk5a4uq4u2mwyng8cqsqgwu5rqgkmu3hez83v6wr69lygqxslcrqwn'>nevent1q…rqwn</a><br/>_________________________<br/><br/>Sjors and I chatted a bit about it in last week&#39;s Optech Recap about it, of someone wants to listen to other sources. 2025-05-14T17:06:53Z https://njump.cloud.vinney.xyz/nevent1qqs25hgf647j74xhh6kawd23g75q6fmzlhv6c0nmwl9l56fevq3gvugzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sf9j3td If you want to get more background on what the mempool is all about, Gloria and I wrote a ten week series in Optech two years ago: <a href="https://bitcoinops.org/en/blog/waiting-for-confirmation/">https://bitcoinops.org/en/blog/waiting-for-confirmation/</a><br/><br/>We also discussed each part of the series in the Optech Recap, if you prefer listening (look for the headphone symbol). 2025-05-14T17:02:31Z https://njump.cloud.vinney.xyz/nevent1qqs8e45nq9j5e3wv92fxpfpew2wlvd90nye6cwjz4r3uv3sr35zj6tczyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3s5ftma3 In reply to <a href='/nevent1qqsr980l445qelv3c3wqy7hx0guws0hejcaqv2vtwuwtuq9pakaelect4vmeh'>nevent1q…vmeh</a><br/>_________________________<br/><br/><a href="https://njump.me/nevent1qqstvvt6eddat0z5tkzmma3y7a9z3clyg7le58evm8yaz9vtnu53secpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygy4xcdzks4zds3t4sakk6aych9vf5mfqm4se7ucy6rgr3z6xqw9rqpsgqqqqqqs3ftc5h">https://njump.me/nevent1qqstvvt6eddat0z5tkzmma3y7a9z3clyg7le58evm8yaz9vtnu53secpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygy4xcdzks4zds3t4sakk6aych9vf5mfqm4se7ucy6rgr3z6xqw9rqpsgqqqqqqs3ftc5h</a> 2025-05-14T06:54:18Z https://njump.cloud.vinney.xyz/nevent1qqsgx87hqn6q3m7zplup6gpm4gdf4jppw7w2mq2stecq22er3ma62ugzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3s9etlm4 In reply to <a href='/nevent1qqsv00m92k3ahrlwksh20yrj968wtcavjx2nfz2eschqn37n2qez57sm4df43'>nevent1q…df43</a><br/>_________________________<br/><br/>I&#39;m just pointing out some facts, you do you 2025-05-14T06:53:34Z https://njump.cloud.vinney.xyz/nevent1qqspq96xpe0nwjxztrpyfnu37ax6a7atd98ve893zpurv4f786y8t2qzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sf3phxs In reply to <a href='/nevent1qqsxv9nxskwy87apt9e8d3yv82gy39k7ngrl4sywctj8fts3hamfqjgj3s6vn'>nevent1q…s6vn</a><br/>_________________________<br/><br/>The other developers work on the upstream project, Bitcoin Core. It is not clear to me why you think he&#39;s joking. Irrational takes like this are par of the course for him. 2025-05-14T06:32:14Z https://njump.cloud.vinney.xyz/nevent1qqstvvt6eddat0z5tkzmma3y7a9z3clyg7le58evm8yaz9vtnu53seczyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sxjpj8m In reply to <a href='/nevent1qqs0ztl75m0e43689zn6k003fx0nvayf74nhgy656ss06mlcv6lgqfsymjt7z'>nevent1q…jt7z</a><br/>_________________________<br/><br/><a href="https://nitter.space/LukeDashjr/status/1921234140717805769">https://nitter.space/LukeDashjr/status/1921234140717805769</a> <img src="https://image.nostr.build/72cbf2f65f8044d2ebe12ddeb1081fa5f6eb7fdc84ec64064d8a5750c8ce6972.jpg"> <img src="https://image.nostr.build/72cbf2f65f8044d2ebe12ddeb1081fa5f6eb7fdc84ec64064d8a5750c8ce6972.jpg"> <br/><br/><a href="https://www.erisian.com.au/bitcoin-core-dev/log-2024-05-02.html#l-596">https://www.erisian.com.au/bitcoin-core-dev/log-2024-05-02.html#l-596</a> 2025-05-14T05:42:56Z https://njump.cloud.vinney.xyz/nevent1qqs9xk2wxt2cxvrdvjhvdlq02t4s54ctfx8dm7v264h8grnm3vmqzsqzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sqxjhh5 In reply to <a href='/nevent1qqswq6t39cr4jtx52uwnewe9fmenyh98a48djjm9y5jvyajfrfjec7cm5ndfr'>nevent1q…ndfr</a><br/>_________________________<br/><br/>I do. What&#39;s up with the leading questions? Are you working up to my code being released in Knots? I&#39;m well aware of that, and that&#39;s an obvious possibility from most of my work being freely licensed. 2025-05-14T01:25:46Z https://njump.cloud.vinney.xyz/nevent1qqsdrwvdxdsd9rwmamdl0sjuu0gnsku4nrld9dwmmzdn5thfjdm2nsszyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sfz7zza In reply to <a href='/nevent1qqsg8eec6yg7cksjtua8ehrpcfkxrcsgwecldmquv8mmcpq4e7q9hmszvp60r'>nevent1q…p60r</a><br/>_________________________<br/><br/>No, I have zero interest to be associated with Knots in any way. 2025-05-13T23:01:26Z https://njump.cloud.vinney.xyz/nevent1qqswaa5vpsyp29258n6radga5ey0q88apnyaa9uqst7fvzcuqjzeynqzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sg6290f I have been seeing some claims that &#34;Bitcoin Knots is part of the Bitcoin Core project&#34;, that &#34;Bitcoin Knots is just another release of Bitcoin Core&#34;, and that &#34;Bitcoin Knots has more contributors than Bitcoin Core&#34;.<br/><br/>Bitcoin Core has about 40 regular contributors with over a thousand past contributors. The Bitcoin Core project releases its software on bitcoincore.org. Bitcoin Core releases are signed by several Bitcoin Core contributors and other community members. Releases are attested to by this community.<br/><br/>Bitcoin Core’s source code is released under the MIT License. The MIT License is a permissive open-source license permitting anyone to do almost anything with the licensed code.<br/>Bitcoin Knots is a project fork of Bitcoin Core. Bitcoin Knots appears to be developed by a single developer pushing directly to master without peer review. Bitcoin Knots releases are composed of Bitcoin Core’s source code modified with a patch set of about 1400 commits. The same individual unilaterally issues releases. There is no indication that anyone else has ever contributed code or review directly to Bitcoin Knots. Bitcoin Knots is not endorsed by the Bitcoin Core project.<br/><br/>Claims to the contrary appear to be based on a unique individual perception of reality. 2025-05-13T21:17:33Z https://njump.cloud.vinney.xyz/nevent1qqs8zugptpj5lquheksxa976eqvhgajvgdu7xfev49xs9s94yrrg59gzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3svnaycj Blocks have been full until end of April and even now, almost all block space is demanded.<br/><br/> <img src="https://image.nostr.build/e1cd80299a99c2382c35bc3476c25a96c59c6e1dfa5fc89a2964f4a1a7911aa3.jpg"> <br/><br/>Via: <a href="https://mainnet.observer/charts/block-weight/">https://mainnet.observer/charts/block-weight/</a> 2025-05-12T21:03:38Z https://njump.cloud.vinney.xyz/nevent1qqsxpvaywns2ghkkprwyq6szfmwhzf6yyqzz4yluqv933l8u5pu5lkszyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3s6j0466 <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/nprofile1qqs9r742wut5rt24z58w8z095pht6632g24fg99d8urxc9m09snxzkcppamhxue69uhkummnw3ezumt0d5q3gamnwvaz7tmjv4kxz7fwv3sk6atn9e5k7qgawaehxw309ahx7um5wgkhqatz9emk2mrvdaexgetj9ehx2aqk6z7et" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>miketwenty1</span> (<span class="italic">nprofile…z7et</span>)</a></span> out together a table of content for the big Q&amp;A thread on OP_RETURN: <a href="https://stacker.news/items/978404">https://stacker.news/items/978404</a> 2025-05-12T19:46:14Z https://njump.cloud.vinney.xyz/nevent1qqs28hrhq7jvxtgemrt2fg76g7tgsxgl54xzx69hwdxd25h3x68pj9gzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3s8r6srp In reply to <a href='/nevent1qqsw6lkhj8lr5slwvscc8umc77jdsyf867yag2ppef93k3ehwuhcakckj7zc9'>nevent1q…7zc9</a><br/>_________________________<br/><br/>I haven&#39;t been particularly active, so it would probably be easy to miss that I even have an account here 2025-05-12T02:16:10Z https://njump.cloud.vinney.xyz/nevent1qqsxnlxjddfmm66lmyw5tpjk7n7qwgp7dx5hwy2lxwszgeap859vlcszyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3s868dyc In reply to <a href='/nevent1qqsrj6q3w3mcdg0qq3wweug9mvvmtkc206qrap7t8cl4ff7kg4ll8xgm54xhr'>nevent1q…4xhr</a><br/>_________________________<br/><br/>Segwit limited the block weight to 4,000,000 weight units (WU). Blockspace has been almost fully demanded since Inscriptions started taking off around February 15th, 2023. Bitcoin Core reserves 4000 WU for the coinbase and block header, so I’ll count any block above 3,960,000 as full.<br/><br/>There have been 119,418 blocks since February 15th 2023. Out of those, 341 blocks were empty (below 2000 WU), 1155 blocks were non-empty up to 90% full (i.e. between 2001 and 3,600,000 WU), 292 were between 90% and 99% full (3,600,001–3,960,000 WU), and 117,630 have been full (3,960,001 or more). In the past ~27 months, 98.5% of all blocks were using at least 99% of the block weight. I have no idea what you are talking about when you say that blocks are not full. 2025-05-09T17:58:39Z https://njump.cloud.vinney.xyz/nevent1qqsq625zvntffjwletk357305vsfe4tl0fdfdh5zmf3s7fh70mnkfdszyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sgz7l90 In reply to <a href='/nevent1qqsgy0gwaeyqhmf4ypfeupe8lmyvf5nwp3wg0msf6cu6jmlkld00mpsuemxmw'>nevent1q…mxmw</a><br/>_________________________<br/><br/>Just a reminder: It&#39;s a Draft BIP. The author is working on making a recommendation to the Bitcoin community. It being published as a BIP means that it is about Bitcoin and has reached sufficient editorial quality to be published. The BIPs repository doesn&#39;t track adoption or likelihood of adoption. 2025-05-08T21:37:35Z https://njump.cloud.vinney.xyz/nevent1qqsqtsfmm7s4uj8wdzvu74qg5jfe24wmm5ex69qdm5kj9twsdm2e78qzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3ssvs4a9 In reply to <a href='/nevent1qqstfhkwtacs6hve2dulap9fpwq4ujy7zqjl4rw7h9kqd68nfel8mqgdm3dk6'>nevent1q…3dk6</a><br/>_________________________<br/><br/>Knots = we don&#39;t like that a few dozen developers discuss in public and then do what they think is best for the software project they&#39;re working on—so we ask Luke to decide everything. 🤔 2025-05-08T06:39:26Z https://njump.cloud.vinney.xyz/nevent1qqsfryf0pf5v3sc8w2p862wq6cf7zh0zmcc687mzf500wg8twq709gczyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sgh6gac In reply to <a href='/nevent1qqs8chf589mly4tcpt089k24fwzjc7vahrcrlscdfys4n6hsgz6hhncf4cd9p'>nevent1q…cd9p</a><br/>_________________________<br/><br/>I tried to explain a bit here: <a href="https://stacker.news/items/971277">https://stacker.news/items/971277</a> 2025-05-08T06:35:05Z https://njump.cloud.vinney.xyz/nevent1qqsfx3q7k5cqzms6njsyf48kg2jdvczrufgwafa6z9cush40u8tv9cczyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sphrgga In reply to <a href='/nevent1qqsgmm7lnvy7rkpknkmvxxxr83l2fgd5tplaq7p28zuve9s6e7r98hq49scvq'>nevent1q…scvq</a><br/>_________________________<br/><br/>Blocks are generally full, so this cannot increase the size of the chain. In fact, since op_return data is written to output scripts, it may displace witness data and shrink blocks in average. Either way, Satoshi wrote that a decade ago, who knows what he would think today if he had been around to see everything that happened since then. 2025-05-07T15:06:37Z https://njump.cloud.vinney.xyz/nevent1qqsv074c3t8fwpp3tkm5kfe22sg98er0mvvx7mrdsfehm98mgurhrhgzyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3skk5u7l In reply to <a href='/nevent1qqs9cgd9gt92nqge8hfjq8tra9dhamdmuqqrtw2v6cwdx29txcw4kkq98wk4w'>nevent1q…wk4w</a><br/>_________________________<br/><br/>Sorta. One of the main purposes of mempools and the gossip network is to surface the most valuable transactions to all miners. Mempool policy is a stricter than the consensus rules, though. 2025-05-07T14:40:56Z https://njump.cloud.vinney.xyz/nevent1qqsfp24cg5qpjgfmy9f6q22zqx9mrlexa9yu48cpu84e0up0vnyc03szyz2nvx3tg23xcg46cwmtdwjvtjky6d5sd6cvlwvzdp5pc3drq8z3sejzt56 Last night, the mempool shrunk to a depth of less than four blocks worth of unconfirmed transactions before it bounced back. It seems that we will soon see non-full blocks. <img src="https://image.nostr.build/e772400e34502e2647be1ca0e5c9e707934648b832c59c29752249a10568b1de.png"> <br/><br/>#mempoolreport 2025-01-31T16:18:44Z