< instagibbs>
wumpus, any particular reason zmq notifications of mempool removal stalled out? reading some PR archaeology and am unsure https://github.com/bitcoin/bitcoin/pull/8549
< instagibbs>
"no one worked on it" is a sufficient answer I just want to make sure I have the proper background
< promag>
instagibbs: I think so
< promag>
instagibbs: feeling like picking it?
< instagibbs>
promag, perhaps
< phantomcircuit>
instagibbs, there's not many applications where zmq is acceptable from a reliability perspective and the performance difference matters
< phantomcircuit>
personally i think most of the zmq consumers should just be polling, with the exception of people building graphs
< instagibbs>
right in practice it's a mixture of polling and zmq at best
< instagibbs>
I don't know anything just using zmq(especially since it doesn't announce things like drops)
< bitcoin-git>
[bitcoin] jnewbery closed pull request #19364: net processing: Move orphan reprocessing to a global (master...2020-06-global-orphans) https://github.com/bitcoin/bitcoin/pull/19364
< bitcoin-git>
[bitcoin] instagibbs opened pull request #19462: Add zmq notifications for evicted transactions, tests (master...notify_eviction) https://github.com/bitcoin/bitcoin/pull/19462
< jeremyrubin>
Kind of struggling to understand a few of the miniscript rules. How would I get something like thresh( 2, hash256({"00"*32}), s:hash256({"00"*32}), older(10) ) to verify (I know there are a few reasons something like this can't). My intuition says you need something like: f'thresh( 2, hash256({"00"*32}), s:hash256({"00"*32}), s:or_i(0, and_v(v:older(10),1)) )', which seems to work. But seems a bit gratuitous?