OrangeSurf

grassroots leambitcoin
building & writing orange.surf
accelerating mempool

Public Key

npub18h0w55nsp839ezxnggf00jd2xc6yl0ht62mf5p8wwllu8s80wdcs83ws8m

NIP-05 Address

_@orange.surf

Profile Code

nprofile1qqsrmhh22fcqncju3rf5yyhhex4rvdz0hm4a9d56qnh80l7rcrhhxugpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tc5h0suz

Publishing to

relay.damus.io

eden.nostr.land

Author Public Key

npub18h0w55nsp839ezxnggf00jd2xc6yl0ht62mf5p8wwllu8s80wdcs83ws8m

Show more details

Last Notes

2026-06-24 13:35:42

Can BIP110 lead to a chain split? What is Mandatory Signaling? What are the fork dynamics in play?
Find the answers - and simulate the outcome for any hashrate split - at http://bip110.orange.surf 👇

2026-06-10 14:35:59

What are the best ways to reliably store a small encrypted blob of data for later retrieval not on your own hardware and not on chain?

2026-06-08 12:03:00

Why does BIP110 permit runes, which are BY FAR the most used form of data embedding on bitcoin today?
https://blossom.primal.net/604a8ab702872af24221aa2b2a796ed84fecf3ef046a6130ccaebbbdd5b13a1e.png

2026-06-05 17:31:07

- reply

I assume you are showing old data and or knots data, not recent bip110 data in this image because recent bip110 data has 0.004% reduction in runes opteturns which make up more than half of tx

2026-06-05 14:45:30

- reply

If it doesn't fix 99.99% of the current spam, what's the point?

2026-06-05 14:28:42

- reply

BIP-110 does next to nothing to stop Runes, 99.99% of Rune activity would remain unaffected.
Over the last 30 days (May 7 – June 5, 2026) there were ~18.94 million total transactions. Of these, 10.88 million were valid Runes (≤ 83-byte OP_RETURN), while only 456 exceeded the limit in BIP110.

2026-06-05 14:20:17

- reply

Inscriptions are being used a negligible amount. Runes on the other hand account for most bitcoin transactions (57.5% this month by my count) and BIP110 does nothing to stop them. Is BIP110 facilitating these shitcoins?

2026-06-05 14:10:59

- reply

Everything they did, they could have done (and until recently did do) without any changes to policy from core, so I don't understand why you feel core is in any way responsible. Realistically it would not have been possible for core to stop this, even BIP110 doesn't stop this.

2026-06-05 14:02:23

- reply

Thanks that's interesting, ironically by trying to concede to core devs request to use a less 'damaging' data storage method there will no doubt be many who view this as proof that they were indeed the masterminds behind changing policy defaults.

2026-06-05 14:00:34

- reply

FWIW ottosch just pointed out that on Apr 29th citrea did start using bigger op_return output instead of 80‒byte + 2 fake pubkeys many months after they became standard.
https://x.com/ottosch_/status/2062895674916581480
https://github.com/chainwayxyz/clementine/pull/1241

2026-06-05 13:40:11

- reply

When I attended a Bitcoin++ event last year I asked a member of the Citrea team who was presenting whether they planned to switch to using the larger and he explicitly said that they weren't switching. I can't see any evidence that they switched. Can you provide any evidence?

2026-06-05 13:11:19

- reply

There was no change to bitcoin core which benefited Citrea, IIUC they haven't even implemented the change to use larger OP_RETURNs instead of fake pubkeys.

2026-06-05 12:45:40

I keep hearing BIP110 proponents describe their fork as being the safe option even with a minority of hashrate due to the "asymmetry" that the BIP110 chain can wipe out the legacy chain, but the legacy chain cannot wipe out the BIP110 chain.
This asymmetry is real for ANY soft fork, but it doesn't make a minority hashrate soft fork safe.
Softfork nodes reject legacy blocks, so they'll never reorg onto the legacy chain
Legacy nodes accept softfork blocks so they will reorg onto the softfork chain if it has more cumulative work.
Once again, If it has more cumulative work.
Nodes (including miner nodes) follow the most-work (valid) chain. A minority hashrate softfork chain accumulates work slower than the legacy chain.
With a minority of hashrate the BIP110 chain will not persist as the most-work chain, it will fall further and further behind over time.
The BIP110 chain could get lucky and get ahead temporarily, but over time the luck will run out and once it falls sufficiently far behind it won't ever catch up to the chain tip.

2026-04-01 11:23:16

There's only two charts in bitcoin that matter, and price isn't one. The first is the hashrate and the second is the number of @nprofile…jemv merchants - @nprofile…gyz0 at @nprofile…5rn6
https://blossom.primal.net/b1ca764c18d4d6843826a6ca3342ce752ec2748664f10de3a4095e58f694b0c2.png

2026-03-30 22:44:42

Glad I held off using the integrated primal wallet until now, I’m sure it was great UI but this is the way 🫡
It’s seamless, Phoenix > Primal in under 5 seconds, super clean design, and crucially zapping Just Works
#nevent1q…eq5p

2026-02-15 18:06:54

- reply

See the details at bip322, the transaction never enters the blockchain
https://github.com/bitcoin/bips/blob/master/bip-0322.mediawiki

2026-02-15 18:04:09

There's been lots of debate about Core v30 removing the OP_RETURN size/count policy defaults, so I ran the numbers for the latest mempool research report: https://research.mempool.space/opreturn-report/
There were three big waves of OP_RETURN usage: 2019, 2024, 2025. Nearly all standard transactions. The nonstandard ones are so rare you can hardly see them on the chart.
https://blossom.primal.net/e653b32fb6281c2c8f61252dbd72d1b3c2c66e57059573a06eb72d5d66812da0.png
The 2019 Veriblock wave actually put more data on-chain than anything since. People talk about recent OP_RETURN usage like it's unprecedented, but surprisingly it isn't.
https://blossom.primal.net/a21d64ede3043825d6df2f08c7c5c6109904b6f5d5b07514488c3e69ce4f405a.png
The important thing is that the spikes in nonstandard OP_RETURNs were in Mar 2024, May 2025, Aug 2025. All before v30 shipped in November 2025. The rate hasn't gone up since. At all. In fact it's come down
https://blossom.primal.net/085a690b1081921e41b84e7c2749adc66eb3ad578f4e44e8bd8135551a7384d8.png
Runes transactions were standard under the old rules and would even still be standard for #BIP110 (the proposal that's supposedly aims to curb data embedding). If these guys are serious about stopping data they should block runes.
https://blossom.primal.net/7634c6534ecbdc21a9e51468daa12ab9c989985b33a232b8e7035f22bfaff58e.png
TL;DR: v30 recognised what was already occasionally happening on-chain. Nonstandard OP_RETURNs are vanishingly rare, haven't increased post-v30, and the current wave is already cooling off. The data doesn't support the panic.
Read the full report linked below 👇
https://research.mempool.space/opreturn-report/

2026-02-12 13:28:17

- reply

(A draft PR, but you can build yourself / use the emulator)

2026-02-12 13:27:29

- reply

Fast work by @nprofile…0dst who added this within 5 hours of receiving my suggestion.
https://blossom.primal.net/295b07dcbed266df63db67a24372a060d34dc34468ea99db40d378f21ceb3764.png
https://blossom.primal.net/740248205ea47005516bfa6b9a36857d5f925f8ac9cec425c2754169141a4d75.png

2026-02-12 13:26:08

As signing device developers begin to add support for BIP322 it would be great to have on-device message viewing. I've sketched out an idea of how this could be done with QR & vis SD.
https://blossom.primal.net/859ba3fe01a6a25a2a6177fa0d15aedba0d8f15fd579c17c2117c8b1a778ac60.png
https://gist.github.com/orangesurf/0c1d0a31d3ebe7e48335a34d56788d4c

2026-02-12 11:46:15

- reply

https://lightning.engineering/posts/2026-02-11-ln-agent-tools/

2026-02-10 12:49:20

Sparrow just added address chunking which is really nice, I've made an extension to experiment with this on mempool, try it out and let me know if you have any feedback
📂 Get Extension Here:
https://github.com/orangesurf/mempool-chunker
https://blossom.primal.net/f9c9cd0aad88f0c0ff1fab2058a09e0ac2135990dace1ea37d439dc290d0cc99.png

2025-12-22 14:54:51

- reply

https://blossom.primal.net/e82c5f7538583e90be0c1ddc9216008042d67eebfc073309447824666889c55f.png

2025-12-22 14:45:32

- reply

Would you expect to know if a government was making advancements towards a CRQC?

2025-12-14 08:41:16

It’s great to see so many people learning the difference between
- Bitcoin consensus vs policy
- UTXOs in RAM vs disk
- Hard vs Soft fork (& chain split)

2025-12-14 04:12:21

Instead of copying long invoice strings, let’s use payment method cards
https://primal.net/orangesurf/bitcoin-payment-method-cards

2025-11-06 06:07:02

The much discussed bitcoin stale block rate, visualised
https://blossom.primal.net/e86a2c338807b03a1117b0060517b5ec6320b0fa0e69d2b2b896a6b9d9149959.png

2025-11-02 08:39:31

Just noticed someone taking advantage of low fees by consolidating 59000 tiny utxos at 0.2 sat/vB across 40 transactions.
That's 4 blocks worth of transactions (3.999 vB) in total!
bc1q3k0swnar7s4w3lcp4u3vys826z8vc2f2t87hu5
https://blossom.primal.net/f082c8f76a8625ef87617d72b6262a2aa804a8cb273086f4ec73bce4d3513dde.png

2025-10-31 04:39:20

wallet devs, are you ready to embrace sub-sat winter?
https://blossom.primal.net/a6070fe78f9837569b8b48e0f5fc16119a89d7aab205a80cfa257301108c62fc.png

2025-10-28 03:55:14

It's times like this that I'm glad I spent 2 minutes vibe coding a button to expand all hidden messages on the bitcoin github repo.
https://blossom.primal.net/1d159627ea79b723b5bbb61a8133b2dfa02266075aac5226a5dde8ddec275136.mov
Code: https://github.com/orangesurf/github-unmoderated

2025-10-13 02:33:03

opreturn stats for last month, you might be able to spot the previous default limit. What do you think October will look like?
https://blossom.primal.net/2dde6aa19c236642ba11afafcdfec6a5ebaaace508b83a84281336c66c077751.png

2025-10-08 09:21:55

Sub 1 sat/vB summer will be studied by generations to come
https://blossom.primal.net/49ec8b87e1d0f601fcfe9efb7dfd1a4a8d106509ccaaaa78f36ba501fd27c7e3.png

2025-10-06 08:41:14

- reply

Done, good idea
https://stacker.news/items/1249538

2025-10-06 07:53:11

Seeing a few comments asking what can be done about data embedding with unspendable UTXOs (an issue which has been around for a long time).
This is a bit long, but hopefully it will be useful as a reference to the more general question of whether you can address protocol level “problems” at the miner / policy level.
Realistically, short of a soft fork there is very little that can be done technically, and even that would have serious limitations & fallout (that’s the whole point of this gross protocol design).
The obvious first reaction is ask miners to stop mining things like this. There are a few ways, but one would be to increase their -dustrelayfee
By default it’s 0.00003 BTC/kB (3 sat/vB) resulting in a dust output limit of 330 sats for P2WSH.
For this transaction with 1859 such outputs the total locked in unspendable outputs is 1859*330‎ = 613,470 sats ($736 @$120k/BTC)
Lets say you successfully lobby the vast majority (95%) of miners to 10x this config value, the sender would have to choose between paying 6.1M sats ($7k) or sending as is and waiting until the small proportion of miners (5%) using the old default. They would probably do the latter because that’s enough hashrate to find 7 blocks/day on average, and what’s the rush?
Having failed to stop this at the miner level you may now be tempted to lobby node runners to change their default and/or change the default in core v31.
Say you were successful, and core v31 contains a higher default. The sender can just preferentially peer to try and reach miners in protocol.
So you double down and you spoof preferential peering such that it’s not sufficiently reliable.
The sender now has no choice but to pay a miner OOB - if they are to do this they might as well make each output be 0 sats. This could actually be mutually financially beneficial for the sender and miner, because instead of sats being burned as fees they would flow to the miner / be saved by the sender.
Now to be fair it would take effort to establish these direct rails to miners who are exclusively financially motivated, but this is a fixed cost, and I have no doubt it would be done, and then integrated via API to centralized minting services.
Thus, the problem would likely end up being worse than the situation we have today.

2025-09-30 10:30:09

Inscriptions & OP_RETURN transactions still make up 40% of bitcoin transactions by count, 10% by fee and 28% by weight.
https://blossom.primal.net/3996e69b2ee6c03ebd34ef4a83c1300af0be076503a1a2e1e96b1cb91f359857.png

2025-09-25 08:21:59

Everyone can agree that we need more decentralized block template construction.
Core sees private tx broadcast as a threat to that (which is fair imo), which is part of why they are widening default policy rules.
Most filter proponents are vocal ocean supporters. Ocean have already materially increased the number of entities (who are actually finding blocks) doing template construction with DATUM, currently I imagine most of these individuals are using knots, and interestingly many don’t filter out all “spam”.
Knots has (iiuc) a single individual who decides what gets merged, and no doubt eventually there will be something he does / doesn’t do that will be perceived as an artificial restriction on user choice.
Ultimately, the only way miners will have sufficient choice without restriction will be if they can construct their own policy (with ease) and we have already seen an example of this (Knots Lua Pull) and a more recent BIP draft to do the same in Core (see mailing list, not received well)
The (perceived) threat with anything like this, is that “actual censorship” is as easy as mandating the inclusion of a filter file, and template construction is sufficiently centralized currently that IMO this is a reasonable concern.
Which brings us back to the point on which we have unanimous agreement: there is a pressing need to decentralize block template production.
Any action to decentralize block template production should be celebrated.
Knots Lua Implementation
https://github.com/bitcoinknots/bitcoin/pull/119/files
JS BIP Draft
https://github.com/dr-bonez/bips/blob/mempool-policy-scripts/bip-mempool-policy-scripts.md

2025-09-19 22:34:50

We must stop people putting data on Bitcoin, it’s a payment network
Meanwhile: every lightning commitment transaction encodes a 48-bit commitment number across nLockTime & nSequence

2025-09-12 18:54:26

Someone is consolidating large batches of UTXOs at erroneously high fee rates.
In the last 7 days they have overpaid by over 5 BTC ($580k) 🤯
They could instead just use 1 sat/vB and RBF if needed (or use Mempool Accelerator Pro and avoid any complexity😉)
196 tx match the following pattern between block heights 913374 - 914379 (past 7 days).
- Minimum Input Count: 100
- Output Count: 2
- Fee Rate: Between 101.6 and 101.7 sat/vB
Total fees: 5.43388700 BTC

2025-09-11 10:12:59

1 sat/vB is clearing but someone just made a consolidation at 102 sat/vB 🫥
https://mempool.space/tx/23b87e424aa51d4900267350c1ad88995c4c132c706c0d6cb80e3cd31971e00e?mode=details
https://blossom.primal.net/4a0790a38fe7075141346589f490a740b87ddcd0a75b1b19069fa7a33a9c6104.jpg

2025-08-28 20:36:23

Sense check
Despite a dip in activity there are still 267k “legit” transactions per day.
(Average non OP_RETURN related/Inscription over the past 90 days)

2025-08-21 21:24:37

Over the past 1000 blocks, more than 30% of transactions have been below the longstanding1 sat/vB default min tx relay fee limit.
https://blossom.primal.net/23e9b2ea50fc23f31a7cf59863a331e95919a06d2a85c56383e67e342d47a416.png
If we plot the actual data, we see spikes around round feerates (1,2,3,4 sat/vB) and a (surprisingly ?) large spike in the sub 1 sat/vB fee rates on the right hand side.
https://blossom.primal.net/a18143c5598bf9fa09f54dc026bae5d750285ddc3216188a3cb89732c1e282bc.png
We can animate this graph with a 1000 block sliding window for the month of August.
https://blossom.primal.net/c69fc3f5061f620e604bb0363f8ad03ecb0d2195ab964840f3cfae57b369a17e.mp4
There is a wide range in the proportion of blocks which are < 1 sat/vB, but the 144 block rolling average has been on an uptrend in recent months (shown here is data since June, block 900000)
https://blossom.primal.net/aa1cd802fc42a8cfc8cf32b99c41d0babedf8270f9ed3b5112db05ed26ff4772.png

2025-06-15 19:25:07

grid.orange.surf
https://blossom.primal.net/92c50ef20078fd2b9df660e46b9cdbbab7f73a5e66ca666b9aa1417c92aaa574.png

2025-06-15 13:43:39

> it only takes one determined spammer to make a tool to allow the less determined to spam. - @npub1zfy…m60l
This is the asymmetry that many filter proponents seem to miss.
Most of the kind of transactions they wish to filter out are created using dedicated software (services / tools / platforms).
Developers of such software can rapidly bypass any restriction using open source software like libre relay, which will get their transactions to miners.
We already see this, with some platforms offering the ability to select broadcast method from a drop down, including direct broadcast to some miners.

2025-06-14 21:29:28

- reply

Both! Either?

2025-06-14 12:33:00

- reply

yeah, it's useful as a data source, you are not really using core as a wallet (signing, key management etc). but due to the design of core a watch only wallet file is created to track the addresses

2025-06-13 08:05:25

Did you use the bitcoin core wallet in the last year?

2025-06-13 06:17:49

gm
https://blossom.primal.net/1aa2e238ab19cb0a3c9d4468c3c6e4a67dba10f69d486aa5bacae3e616815e11.png

2025-06-10 13:41:38

@nprofile…2xpe and I are arriving early for @nprofile…py4c.
Get in touch if you are around from the 14th and want to meet up!
https://blossom.primal.net/a9b67cad3adec53c0b7ee6f88d73c1e949dff0ae8b4a2dc7e5f2f96157b87664.png

2025-06-09 15:37:28

Which filter do you think core will drop / change the default for next?
- Max Transaction Size
- Minimum Relay Fee
- Minimum Output Size

2025-06-08 22:50:09

What do I do?
Research: I publish chart filled data-driven reports on technical Bitcoin topics. Read at http://mempool.space/research
Business inquiries: I lead strategy and business development at
@nprofile…wnpf. Reach out directly for questions about Mempool Enterprise & Accelerator

2025-06-08 22:15:18

So many based bitcoiners at bcc8333 unconference.
If you are in Barcelona check out their meetup
https://www.meetup.com/bitcoin-barcelona/

2025-06-06 06:01:42

Block 900,000, had room to spare despite a celebratory meme inscription.
https://blossom.primal.net/f7c2687117af5b42eb58afea1e2d4dc4d1de665aaf879704db941fedf40bca3f.jpg
https://blossom.primal.net/06bb60cdc53624b786f6f22398af86bc1945f57b927b14cc5bb68fb42cc548c4.jpg

2025-06-04 07:13:21

- reply

This works really well

2025-05-29 19:55:43

- reply

love to see it, we should talk 🤙

2025-05-28 12:41:23

Unbelievable lack of use
https://blossom.primal.net/e77e78cfb71c4b0ee85d6b29da9dca927a872e3ecb6ed43bd6229f5591b355c3.png

2025-05-23 14:52:13

- reply

Thank you 🙏

2025-05-20 04:21:20

41.65% of the UTXO set is dust amounts precisely at the implied default core policy dust limits for various script types.
note: p2tr is the most popular 546 sat script type (68% of all 546 sat outputs). I guess degen wallets don't compute the actual dust limit?
https://blossom.primal.net/b0820294e04b9bf195d7084d033cacd0ba3e21ca8bc7b8296347fd903205ab0e.png

2025-05-19 23:12:14

Surprising facts from my new report on Bitcoin's UTXO set:
- 49% of UTXOs are sub 1000 sats
- 30% of UTXOs are inscriptions related
- 100k+ 10-year-old counterparty UTXOs store arbitrary data with fake multisig pub keys
Read it in full here:
https://research.mempool.space/utxo-set-report/

2025-05-19 05:16:36

- reply

Fee

2025-05-19 04:45:58

https://blossom.primal.net/76a21bc9a4a4e5d7123e4050a7081cbe080097e4ca17557628eeed15ffdcc7b0.png

2025-05-19 04:31:52

By popular request, here is the last years bitcoin transaction data with rune & BRC20 split out from other OP_RETURN and Inscription transactions.
Runes & BRC20 = 51% of transactions over the past 12 months
https://blossom.primal.net/745e98bf3be0796f038d8cae5dae76898f94d8f5f11ed419afaef19fce80893b.png

2025-05-19 03:02:51

https://blossom.primal.net/57f1e53e32604fe146d2268589703e1dc4c492c4827dfcc4c9f6499f3083a325.jpg

2025-05-18 16:43:42

Over the past year bitcoin there have been more data storage transactions (inscriptions & OP_RETURN) than other transactions.
https://blossom.primal.net/296f78229a504abba9e1f8f0867037065049fcc7c2a1d2a6dfe315cee1f6e8e1.png

2025-05-08 11:48:29

The most entertaining outcome is the most likely. Bookmark this.
https://blossom.primal.net/690f3e9253f872b1b5da9c0ea90a9317ab465771a23d2ce87e6273bf5b28d1c9.jpg

2025-05-08 11:32:34

Get yourself to a @npub1dwa…7c52
event, what @nprofile…dtke and the team have built is truly special.
The difference between online and IRL discussion is stark.
Online we only see differences.
IRL people celebrate similarities.

2025-05-06 01:59:21

- reply

What has changed since 2023, when pull 28130 was closed with the justification that “it's unlikely that Bitcoin Core is going to make any changes in regards to OP_RETURN”?

2025-05-06 01:47:02

I’m seeing lots of speculation around the financial motivations with regards to modifying OP_RETURN standard core policy.
In 2023 Peter Todd was transparent with his financial incentive ($1000 from Christopher Allen) for making pull request 28130, which was ultimately closed
https://github.com/bitcoin/bitcoin/pull/28130

2025-05-05 20:51:41

🎲 In 2014 Luke Dashjr described mining policies such as OP_RETURN size limits as not being a development topic, and suggested randomizing the default value.
https://gnusha.org/pi/bitcoindev/201411161724.19573.luke@dashjr.org/

2025-05-05 12:54:43

- reply

The conversation is still locked. My guess would be a push behind a new pull which doesn’t remove configuration options and only changes defaults

2025-05-05 02:22:40

The latest OP_RETURN war kicked off days prior to @npub1dwa…7c52 mempool edition. very sus. In Austin to get to the bottom of this 👀

2025-04-30 17:41:36

- reply

lol wut

2025-04-30 12:32:14

- reply

The legend didn't render correctly
https://blossom.primal.net/7c315d9b2ab8bab17e645f2737af639a067a63f28e40344acc49bef07cfbced9.png

2025-04-30 11:52:06

I've put some numbers together to help you determine whether the horse has already bolted regarding the use of bitcoin for non financial transactions.
49% the UTXO set is sub 1000 sat outputs
43% of transactions in the past 2 weeks had an OP_RETURN or were inscriptions.
https://blossom.primal.net/be33911765f6d7dc5f61fc459eb0415dc0966c9a113d33115e8b042b5b0f2612.png

2025-04-30 09:57:34

I think there is a strong argument to be made that even if you hold the opinion that bitcoin is for financial transactions, not arbitrary data storage, the figurative horse has bolted and efforts to close the stable door are currently futile. The argument looks like this.
1) There are people who want to encode arbitrary data, and are willing to pay for this. Systems are being developed which use arbitrary data pushes to enable bitcoin financial transactions to happen on sidechains/layers, blurring the line between financial transactions and the arbitrary data most people think about (jpegs on the blockchain).
2) Blocking arbitrary data at the relay layer is a sisypheancan task which nobody has succeeded to do for a prolonged period of time.
3) Even if successful the relay network can and will be trivially bypassed if block template builders wish to accept these transactions which encode arbitrary data. So you need template builders to be on board (the more the better).
4) The current block template builders are not likely to be on board, as it goes against their short-mid term financial incentives. This is because they are typically
(a) disengaged / ambivalent about bitcoin development (see radio silence regarding new soft fork discussions)
(b) In favour of any and all use of blockspace which will increase revenue (see the direct submission services, use of librerelay, prevalence of side chain mining)
(c) Of the opinion that their fiduciary responsibility is to construct blocks containing valid transactions which generate the highest possible revenue for their customers.
4) Even IF you were able to successfully persuade template builders to filter these transactions (say by decentralising template construction into the hands of more ideological lower time preference miners) there will be disagreement about what level of data encoding is acceptable, with some arguing that it is permissible in certain formats, and with hardliners arguing that all arbitrary data should be eliminated. The fragmentation will result in some arbitrary data being trivially pushed into the chain.
5) Even IF you were able to persuade the overwhelming majority of hashrate to reject arbitrary data inclusion it becomes difficult to reliably get transactions which clearly encode arbitrary data into blocks, the data would end up being encoded in a slightly less efficient manner with a 2x cost burden.
6) If 2x cost burden is sufficient to stop arbitrary data encoding then it can easily be priced out. If not, all that effort would be wasted because it wouldn't achieve the desired outcome.

2025-04-29 16:59:43

- reply

Knots does much more than a “simple” filter fix, and personally I don’t think it has enough reviewers to recommend it’s use

2025-04-29 13:21:04

A message to those on team #fixthefilters - your time would be better spent earning sats, which you can then use to fund development of a bitcoin node implementation which implements your desired configuration options. It's a cat and mouse game and the cat is currently asleep.
https://blossom.primal.net/a9c918c311720b1ce59254e5d4d592fec6638555bc5ac026b664d7c35d09f09f.png

2025-04-29 13:02:09

adding policy rules as a non mining node makes about as much difference as posting your opinion on the github pull request
both sides agree on this 😂

2025-04-29 12:20:39

- reply

Read the mailing list post here
https://groups.google.com/g/bitcoindev/c/d6ZO7gXGYbQ
Read the github pull request discussion here
https://github.com/bitcoin/bitcoin/pull/32359

2025-04-29 09:32:50

- reply

Call for transparent development
In my opinion it is critical that bitcoin developers have an opportunity to verify that these nonstandard transactions don't pose DOS risks. With that in mind, it would be great to be able to perform benchmarking on these transactions prior to them being widely deployed on chain.
If you are building systems which use nonstandard transactions, I would love to discuss this with you!
I will post more about this in the future, if anything was unclear please comment below!
Note: There is also the set of transactions using upgrade hooks, where pretty much everyone benefits from not including certain transactions. Ideally we can ensure that there is no economic demand for these, because they make upgrades much easier.

2025-04-29 09:32:33

- reply

If economic demand for these transactions grows, it is reasonable to expect that some miners will relax the policy rules on their blockmaker node to earn this extra revenue.
These transactions won't relay over the standard bitcoin core p2p relay, so they will either be submitted directly to the miner (e.g. slipstream) or over an alternate relay path (e.g. opreturn bot using libre relay). Once mined they will be downloaded by all nodes in the network.
From my perspective, it's inevitable that systems will be built to get valid transactions to miners if they can't be relayed p2p. This has already happened, and will likely continue to happen as people develop systems which require the use of nonstandard transactions.

2025-04-29 09:32:14

- reply

Ideally the standard transactions & DOS transactions sets don't intersect, that's the intention of most policy rules.
Note: There are some who believe that policy rules should be used to guide the use of the permissionless network. Personally I think this is a folly when there is an economic incentive.
It's relatively simple to ensure that the standard transactions and known DOS transactions don't intersect because they are both well defined. It's harder to know whether the standard transactions and the unknown DOS transactions don't intersect, but we can reason about how we would construct a DOS transaction and then add some policy rules. For example, we can set a limit on the total size of a transaction, which will presumably mean some unknown DOS transactions are now non standard (and our node is protected).
So to be prudent we can add in lots of policy / standardness rules to protect us from unknown DOS transactions, which makes our node less vulnerable. The tradeoff is that in doing this we also make some safe (non DOS) transactions non standard. Arguably this is what happened over the years with bitcoin core, and for good reason.
This is a key point when considering policy rules. Our understanding of what transactions potentially result in a DOS risk is undoubtedly incomplete, and the widespread adoption of current bitcoin core standardness rules might be protecting the network more than we realise. But, having strict policy rules is also making some perfectly safe transactions non standard. For miners, these non standard, known non DOS transactions represent a safe source of extra revenue.
https://m.primal.net/QhEf.jpg

2025-04-29 09:31:40

- reply

Another subset of valid transactions are Denial of Service (DOS) transactions, which for one reason or another will cause a node to have a bad time. For example a DOS transasction might crash the node, or cause it to take a very long time to validate. We know about a number of DOS transactions, but presumably there are some DOS transactions which we don't yet know about. So we can add to our diagram two circles, one for all DOS transactions, and within that a smaller circle for the known DOS transactions.
https://m.primal.net/QhEe.jpg

2025-04-29 09:31:17

- reply

Next we have standard transactions, which are the transactions permitted into the mempool of a node according to it's policy rules.
The default policy rules which come packaged with the latest bitcoin core release are generally adopted by the network within a year. Each release with new policy rules will result in different set of standard transactions, so it's a moving target, but on any given node the rules are set at any given time.
Each node can configure it's policy rules as it sees fit (in theory, more on this later) and transactions must first pass consensus rules before considering policy. This means that there is no risk that using different policy rules will break consensus. Another way to say this is that standard transactions are a subset of valid transactions.
https://m.primal.net/QhEd.jpg

2025-04-29 09:30:50

- reply

Here is a quick introduction to what bitcoin policy rules are
We start with (consensus) valid transactions. These transactions abide by the bitcoin consensus rules which all nodes on the network enforce. For example, a non coinbase transaction can't spend more than the sum of the inputs.
https://m.primal.net/QhEb.jpg

2025-04-29 09:30:20

The recent pull request to bitcoin core made by peter todd (pull 32359) removes the code to enforce a policy limit on the size and number of OP_RETURN outputs. Additionally, he proposes the removal of the configuration options to allow node runners to modify the maximum size of data carrying transactions.

2025-04-28 19:41:20

If bitcoin core doesn’t have the functionality that you want you can build it, and share it with the world.
If other people share your views they can also run that code.

2025-04-25 09:35:40

- reply

Examples of users
The High-Ticket Merchant
Sells expensive goods with incoming funds straight into cold storage. Can’t (or won’t) leave a hot key online for CPFP, and asking the customer to bump the fee is awkward. An auto-accelerator guarantees confirmation so the product can ship without delay.
The Multisig Treasury Custodian
Manages a 3-of-5 vault for a family office. Gathering three signers to recreate an RBF transaction is slow and costly; the automated bump removes that operational friction.
The Air-Gapped Solo Stacker
Signs a single-sig transaction on an offline device just before boarding a long flight or going off-grid. With no way to reconnect, the auto-accelerator acts as a safety net if the initial fee estimate was too low.
Payroll Controller
Payroll is broadcast on Friday and the finance team is away for the weekend. If the mempool spikes, the auto-accelerator silently bumps the fee so employee pay doesn’t wait until Monday.

2025-04-25 07:39:51

You are making a transaction, you check mempool and set what seems like an appropriate fee, but then a new degen mint drops and your transaction gets buried. New transactions coming in push your transaction further back, and 24 hours later it's 10 blocks deep.
Fortunately you used Mempool Auto Accelerator with a 24h Time Delay trigger, and your transaction confirms in the next block.
I have 10 beta access spots, dm me.
https://blossom.primal.net/cb304169e7a2a3f54542da15f0695a1109f21a5ed9c3ee10fb75fc137f990576.png

2025-04-24 12:26:20

- reply

I guess they REALLY wanted a 1.0 BTC utxo, and no change
https://m.primal.net/Qbdo.png

2025-04-24 12:24:30

unusual 151 sat/vB tx
https://m.primal.net/Qbde.png
https://mempool.space/tx/53a2b07caeef425198cc394df8511087b181cf0ab64ad1c42dee3231b2730804

2025-04-23 18:18:37

- reply

Thanks for the mention!

2025-04-23 08:05:48

Thanks to DATUM the @nprofile…fd7j team have increased the number of entities finding blocks who constructed their own templates by 13 entities (11 if you assume Just Fo r X is one entity). You love to see it.
https://m.primal.net/QaLi.png
#nevent1q…vm9m

2025-04-23 07:19:44

If you are building something on bitcoin and use @nprofile…wnpf every day I want to hear from you, drop me a message.

2025-04-22 21:03:33

https://zap.stream/npub1qny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysew95gx

2025-04-22 15:44:36

- reply

Also excited to see
1) A renewed interest in transaction verification. Could this be the revival of the "server as a screen" concept the team presented in 2023?
> We want to give Bitkey customers easy ways to verify transaction details and other security-critical operations. First up is a software-driven feature we’ll bring to customers mid-year.
2) Hardware verification (on screen device?) and cold wallet config (FROST? orange.surf/bitkey-notes/)
> We’re also evaluating ways to provide even stronger transaction verification with hardware, and an optional cold wallet configuration for customers who don’t mind putting in a little more effort for more security.

2025-04-22 15:40:05

Very interested to learn more about the Privacy improvements. "Predicate blind signing" was mentioned previously by the team in their Oct 2024 post.
https://bitkey.build/building-in-the-open/
# Signing privacy
Predicate blind signing combines blind Schnorr signatures with zero-knowledge proofs that make assertions about transaction attributes. This allows the server to enforce signing policies without learning any identifying information about the transaction itself.
# Vault privacy
For transactions involving funds stored in the vault, the server only signs for the funds outside the vault, adding an extra layer of protection. To preserve privacy while proving funds exist, we use a zero-knowledge proof system similar to the proof-of-solvency approach utilized by exchanges. This method allows the app to prove to the server that sufficient funds exist for a transaction without revealing any specific details about wallet balances or transaction history.
#nevent1q…vcp7

2025-04-16 12:56:27

confused about the different mining options with
@OCEAN ? I've made a table to compare STRATUM (V1) with DATUM.
Will add in STRATUM V2 & DEMAND in the future.
http://poolcompare.orange.surf

2025-04-16 12:56:10

- reply

should be poolcompare.orange.surf

2025-04-16 12:54:53

confused about the different mining options with
@nprofile…fd7j ? I've made a table to compare STRATUM (V1) with DATUM.
Will add in STRATUM V2 & DEMAND in the future.
http://poolcomparison.orange.surf

2025-04-15 06:58:55

"solo mining" is currently confusing as a term because it's being used to mean different things by different people (often with an agenda).
Sovereign Mining: You select the transactions
Lotto Mining: You get the full block reward