< 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)
< instagibbs> anyone*
< promag> what you mean with drops?
< instagibbs> mempool eviction
< promag> ah ok
< bitcoin-git> [bitcoin] sipa pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/b52e25cc1be3...abdfd2d0e3eb
< bitcoin-git> bitcoin/master b691f2d Pieter Wuille: Replace automatic bans with discouragement filter
< bitcoin-git> bitcoin/master 2ad5838 Pieter Wuille: Clean up separated ban/discourage interface
< bitcoin-git> bitcoin/master abdfd2d Pieter Wuille: Merge #19219: Replace automatic bans with discouragement filter
< bitcoin-git> [bitcoin] sipa merged pull request #19219: Replace automatic bans with discouragement filter (master...202006_discourage) https://github.com/bitcoin/bitcoin/pull/19219
< bitcoin-git> [bitcoin] ryanofsky opened pull request #19460: multiprocess: Add bitcoin-wallet -ipcconnect option (master...pr/ipc-connect) https://github.com/bitcoin/bitcoin/pull/19460
< bitcoin-git> [bitcoin] ryanofsky opened pull request #19461: multiprocess: Add bitcoin-gui -ipcconnect option (master...pr/ipc-gui) https://github.com/bitcoin/bitcoin/pull/19461
< 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?
< jeremyrubin> let me expand that...
< jeremyrubin> 'thresh(2,hash256(aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa),s:hash256(ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff),s:or_i(0,and_v(v:older(10),1)))'
< jeremyrubin> CScript([OP_SIZE, x('20'), OP_EQUALVERIFY, OP_HASH256, x('aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa'), OP_EQUAL, OP_SWAP, OP_SIZE, x('20'), OP_EQUALVERIFY, OP_HASH256, x('ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff'), OP_EQUAL, OP_ADD, OP_SWAP, OP_IF, x(''), OP_ELSE, 10, OP_CHECKSEQUENCEVERIFY, OP_VERIFY, 1, OP_ENDIF, OP_ADD, 2, OP_EQUAL])
< sipa> define "to verify" ?
< jeremyrubin> "to type check and produce a sane script"
< jeremyrubin> 'thresh(2,hash256(aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa),s:hash256(ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff),sltv:older(10))'
< jeremyrubin> That's the simpler version I guess?
< sipa> ##miniscript