12025-09-22T00:08:55 *** Cory18 <Cory18!~Cory22@user/pasha> has joined #bitcoin-core-dev
22025-09-22T00:10:10 *** jon_atack <jon_atack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
32025-09-22T00:10:45 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 245 seconds)
42025-09-22T00:12:31 *** Cory22 <Cory22!~Cory73@user/pasha> has quit IRC (Ping timeout: 250 seconds)
52025-09-22T00:21:46 *** jon_atack <jon_atack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 248 seconds)
62025-09-22T00:22:51 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
72025-09-22T00:34:39 *** aleggg <aleggg!~aleggg@177.188.150.31> has quit IRC (Ping timeout: 258 seconds)
82025-09-22T00:34:49 *** aleggg <aleggg!~aleggg@177.188.150.31> has joined #bitcoin-core-dev
92025-09-22T00:48:14 *** sliv3r__ <sliv3r__!~sliv3r__@user/sliv3r-:76883> has quit IRC (Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in)
102025-09-22T00:48:35 *** sliv3r__ <sliv3r__!~sliv3r__@user/sliv3r-:76883> has joined #bitcoin-core-dev
112025-09-22T00:53:09 *** cm <cm!~chaz@user/cm> has quit IRC (Ping timeout: 260 seconds)
122025-09-22T00:53:14 *** jon_atack <jon_atack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
132025-09-22T00:54:49 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 255 seconds)
142025-09-22T00:56:00 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
152025-09-22T00:57:12 *** cm <cm!~chaz@user/cm> has joined #bitcoin-core-dev
162025-09-22T00:59:11 *** jon_atack <jon_atack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 258 seconds)
172025-09-22T01:26:23 *** jon_atack <jon_atack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
182025-09-22T01:28:08 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 260 seconds)
192025-09-22T01:32:38 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
202025-09-22T01:34:50 *** jon_atack <jon_atack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 258 seconds)
212025-09-22T01:39:16 *** jon_atack <jon_atack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
222025-09-22T01:40:20 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Read error: Connection reset by peer)
232025-09-22T01:41:43 *** Christoph_ <Christoph_!~Christoph@ipbcc15898.dynamic.kabel-deutschland.de> has joined #bitcoin-core-dev
242025-09-22T01:44:13 *** jon_atack <jon_atack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 265 seconds)
252025-09-22T01:45:06 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
262025-09-22T02:09:09 *** Christoph_ <Christoph_!~Christoph@ipbcc15898.dynamic.kabel-deutschland.de> has quit IRC (Quit: Christoph_)
272025-09-22T02:22:53 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has quit IRC (Ping timeout: 250 seconds)
282025-09-22T02:25:48 *** jon_atack <jon_atack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
292025-09-22T02:26:28 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 260 seconds)
302025-09-22T02:47:19 *** jon_atack <jon_atack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 255 seconds)
312025-09-22T02:49:21 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has joined #bitcoin-core-dev
322025-09-22T02:56:27 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has quit IRC (Ping timeout: 248 seconds)
332025-09-22T03:10:00 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has joined #bitcoin-core-dev
342025-09-22T03:30:53 *** Cory18 <Cory18!~Cory22@user/pasha> has quit IRC (Quit: Client closed)
352025-09-22T03:31:17 *** Cory18 <Cory18!~Cory18@user/pasha> has joined #bitcoin-core-dev
362025-09-22T03:48:33 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has quit IRC (Ping timeout: 252 seconds)
372025-09-22T03:52:31 *** Cory18 <Cory18!~Cory18@user/pasha> has quit IRC (Quit: Client closed)
382025-09-22T03:52:52 *** Cory18 <Cory18!~Cory18@user/pasha> has joined #bitcoin-core-dev
392025-09-22T04:01:02 *** cmirror <cmirror!~cmirror@4.53.92.114> has quit IRC (Remote host closed the connection)
402025-09-22T04:01:21 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has joined #bitcoin-core-dev
412025-09-22T04:01:32 *** cmirror <cmirror!~cmirror@4.53.92.114> has joined #bitcoin-core-dev
422025-09-22T04:05:26 *** jerryf_ <jerryf_!~jerryf@user/jerryf> has joined #bitcoin-core-dev
432025-09-22T04:06:44 *** jerryf <jerryf!~jerryf@user/jerryf> has quit IRC (Ping timeout: 272 seconds)
442025-09-22T04:23:31 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Quit: l0rinc)
452025-09-22T04:24:19 *** conman <conman!~con@180-150-21-3.b49615.mel.static.aussiebb.net> has quit IRC (Ping timeout: 260 seconds)
462025-09-22T04:25:12 *** Cory18 <Cory18!~Cory18@user/pasha> has quit IRC (Quit: Client closed)
472025-09-22T04:25:36 *** Cory18 <Cory18!~Cory18@user/pasha> has joined #bitcoin-core-dev
482025-09-22T04:33:27 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
492025-09-22T04:34:45 *** conman <conman!~con@180-150-21-3.b49615.mel.static.aussiebb.net> has joined #bitcoin-core-dev
502025-09-22T04:42:11 *** cman <cman!~con@180-150-21-3.b49615.mel.static.aussiebb.net> has joined #bitcoin-core-dev
512025-09-22T04:42:25 *** conman <conman!~con@180-150-21-3.b49615.mel.static.aussiebb.net> has quit IRC (Ping timeout: 250 seconds)
522025-09-22T04:59:00 *** Christoph_ <Christoph_!~Christoph@2a02:810d:1399:b700:a4db:8f22:bafe:4c87> has joined #bitcoin-core-dev
532025-09-22T05:08:58 *** Guest35 <Guest35!~Guest35@host86-158-138-170.range86-158.btcentralplus.com> has joined #bitcoin-core-dev
542025-09-22T05:11:25 *** Guest35 <Guest35!~Guest35@host86-158-138-170.range86-158.btcentralplus.com> has quit IRC (Client Quit)
552025-09-22T05:11:58 *** Guest35 <Guest35!~Guest35@host86-158-138-170.range86-158.btcentralplus.com> has joined #bitcoin-core-dev
562025-09-22T05:15:30 *** Guest35 <Guest35!~Guest35@host86-158-138-170.range86-158.btcentralplus.com> has quit IRC (Client Quit)
572025-09-22T05:18:05 *** Guest35 <Guest35!~Guest35@host86-158-138-170.range86-158.btcentralplus.com> has joined #bitcoin-core-dev
582025-09-22T05:18:26 *** Guest35 <Guest35!~Guest35@host86-158-138-170.range86-158.btcentralplus.com> has quit IRC (Client Quit)
592025-09-22T06:03:48 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Quit: l0rinc)
602025-09-22T06:04:30 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has quit IRC (Ping timeout: 245 seconds)
612025-09-22T06:18:01 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has joined #bitcoin-core-dev
622025-09-22T06:42:25 *** jerryf_ <jerryf_!~jerryf@user/jerryf> has quit IRC (Remote host closed the connection)
632025-09-22T06:42:46 *** jerryf <jerryf!~jerryf@user/jerryf> has joined #bitcoin-core-dev
642025-09-22T07:01:36 *** purpleKarrot <purpleKarrot!~purpleKar@user/purpleKarrot> has joined #bitcoin-core-dev
652025-09-22T07:07:42 *** f321x <f321x!~f321x@user/f321x> has joined #bitcoin-core-dev
662025-09-22T07:20:28 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has quit IRC (Ping timeout: 260 seconds)
672025-09-22T07:24:20 *** f321x <f321x!~f321x@user/f321x> has quit IRC (Ping timeout: 272 seconds)
682025-09-22T07:26:04 *** f321x <f321x!~f321x@user/f321x> has joined #bitcoin-core-dev
692025-09-22T07:33:11 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has joined #bitcoin-core-dev
702025-09-22T07:46:05 *** Guyver2 <Guyver2!Guyver@77-174-98-73.fixed.kpn.net> has joined #bitcoin-core-dev
712025-09-22T07:51:46 *** Christoph_ <Christoph_!~Christoph@2a02:810d:1399:b700:a4db:8f22:bafe:4c87> has quit IRC (Quit: Christoph_)
722025-09-22T08:06:46 *** f321x <f321x!~f321x@user/f321x> has quit IRC (Ping timeout: 272 seconds)
732025-09-22T08:13:17 *** f321x <f321x!~f321x@user/f321x> has joined #bitcoin-core-dev
742025-09-22T08:27:02 *** f321x <f321x!~f321x@user/f321x> has quit IRC (Ping timeout: 272 seconds)
752025-09-22T08:32:48 *** f321x <f321x!~f321x@user/f321x> has joined #bitcoin-core-dev
762025-09-22T08:35:37 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has quit IRC (Ping timeout: 255 seconds)
772025-09-22T08:39:38 *** f321x <f321x!~f321x@user/f321x> has quit IRC (Remote host closed the connection)
782025-09-22T08:40:05 *** f321x <f321x!~f321x@user/f321x> has joined #bitcoin-core-dev
792025-09-22T08:41:52 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has joined #bitcoin-core-dev
802025-09-22T09:03:21 *** f321x <f321x!~f321x@user/f321x> has quit IRC (Remote host closed the connection)
812025-09-22T09:03:25 *** f321x_ <f321x_!~f321x@user/f321x> has joined #bitcoin-core-dev
822025-09-22T09:04:43 *** Guest81 <Guest81!~Guest81@154.16.27.77> has joined #bitcoin-core-dev
832025-09-22T09:13:07 *** saturday- <saturday-!~saturday7@206.83.122.4> has quit IRC (Ping timeout: 244 seconds)
842025-09-22T09:18:39 *** f321x_ <f321x_!~f321x@user/f321x> has quit IRC (Remote host closed the connection)
852025-09-22T09:18:57 *** f321x <f321x!~f321x@user/f321x> has joined #bitcoin-core-dev
862025-09-22T09:33:31 *** saturday7 <saturday7!~saturday7@206.83.105.165> has joined #bitcoin-core-dev
872025-09-22T09:39:22 *** saturday7 <saturday7!~saturday7@206.83.105.165> has quit IRC (Quit: ZNC 1.10.1 - https://znc.in)
882025-09-22T09:48:53 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Remote host closed the connection)
892025-09-22T09:49:33 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
902025-09-22T09:55:32 <sipa> _aj_: in what way does the formula i implemented differ from what you thought?
912025-09-22T09:59:01 *** saturday7 <saturday7!~saturday7@206.83.122.147> has joined #bitcoin-core-dev
922025-09-22T09:59:26 <sipa> ah, the use of time-since-send, rather than a fixed % per trickle?
932025-09-22T09:59:30 *** f321x <f321x!~f321x@user/f321x> has quit IRC (Ping timeout: 272 seconds)
942025-09-22T09:59:42 *** Guest81 <Guest81!~Guest81@154.16.27.77> has quit IRC (Quit: Client closed)
952025-09-22T10:01:10 <_aj_> sipa: i was making the drain rate proportional to the incoming rate, rather than the queue size?
962025-09-22T10:03:47 <sipa> 08:12:33 < sipa> it should just be past_avg -= to_send
972025-09-22T10:03:47 <sipa> 08:12:46 < sipa> .. and then past_avg just becomes equal to the queue size
982025-09-22T10:04:07 <sipa> i stopped using a separate variable for tracking rate here, because the queue size is an exact proxy for it
992025-09-22T10:05:04 <_aj_> hmm
1002025-09-22T10:05:22 <_aj_> well then it must just be that i was using the average time rather than the actual time?
1012025-09-22T10:06:11 <sipa> yeah
1022025-09-22T10:06:11 <_aj_> right, because we stopped scaling past_avg down by q
1032025-09-22T10:06:34 <sipa> also, you use max(target, queue_size * (1-q)) rather than (target + queue_size * (1-q))
1042025-09-22T10:06:56 <_aj_> sure, but that should be a trivial difference
1052025-09-22T10:07:37 <sipa> indeed
1062025-09-22T10:09:09 <_aj_> so this is just saying either max(70, 0.08 * inv_to_send.size()) or 70 + 0.08 * inv_to_send.size() ?
1072025-09-22T10:09:46 <_aj_> and a queue of 5000 gives a inv of size 400 or 470 or so
1082025-09-22T10:09:55 <sipa> right
1092025-09-22T10:10:30 *** WizJin_ <WizJin_!~Wizzy@2402:a00:184:8354:e543:2733:1fa1:9bc5> has joined #bitcoin-core-dev
1102025-09-22T10:10:37 <sipa> you think using actual time is worse than avg_time?
1112025-09-22T10:12:12 <_aj_> i think having a queue of only 5000 and sending a single inv with 2000 entries seems bad/unnecessary? i can't remember what it takes for us to start ignoring invs though
1122025-09-22T10:13:12 <_aj_> the more predictable the size of our invs are over some unit of time, the better for erlay, i think?
1132025-09-22T10:13:56 *** WizJin__ <WizJin__!~Wizzy@2402:a00:184:8354:e543:2733:1fa1:9bc5> has quit IRC (Ping timeout: 256 seconds)
1142025-09-22T10:15:16 <_aj_> so 0.08 there is just changing the current 5-per-1000 logic from an avg-time-in-q of ~1000 seconds to 60 seconds
1152025-09-22T10:16:39 <_aj_> or changing 5-per-1000 to ~5-per-60
1162025-09-22T10:16:44 <sipa> right
1172025-09-22T10:18:33 <sipa> i like the real-time formula better because it means the amount sent per time is less variable (because it doesn't depend on the trickle timing)
1182025-09-22T10:18:49 <sipa> but of course the amount sent per trickle is more variable
1192025-09-22T10:23:14 <_aj_> should just be "0.08 * time_since / target" without the exp() stuff in the case?
1202025-09-22T10:24:02 <_aj_> "that case". why would my fingers type "the" there, seriously.
1212025-09-22T10:26:59 <sipa> _aj_: sure, that also has the "just a function of time" property, but no longer has an average-time-in-queue that's independent of incoming rate
1222025-09-22T10:29:36 <_aj_> sipa: that property feels contradictory to the goal of smoothing out spikes -- doesn't smoothing out spikes imply that a high incoming rate should be associated with a higher aveage-time-in-queue?
1232025-09-22T10:30:47 <sipa> _aj_: at low/reasonable rate, yes; at high rate, i think a fixed avg-time-in-queue is desirable because the alternative is a possibility for a quickly growing queue
1242025-09-22T10:32:48 <sipa> the alternative is dropping transactions at the source
1252025-09-22T10:35:00 *** f321x <f321x!~f321x@user/f321x> has joined #bitcoin-core-dev
1262025-09-22T10:35:57 <sipa> the earlier quadratic formula i suggest was even more aggressive, in that it results in a decreasing time in queue with increasing rate
1272025-09-22T10:36:26 <_aj_> i guess there's a few different rates -- ~5-7 tx/s is what we see normally; < 14 tx/s is what we cope with without this; sustained <80 tx/s would give us a queue of ~5000 which seems fine; but dumping 50k or 100k txs (12MB?) in short order is possible too...
1282025-09-22T10:40:26 <sipa> should we have 3 "parameter rates", 1 for "no delay", 1 for "smooth out", 1 for "drop stuff" ?
1292025-09-22T10:42:26 <_aj_> could we rate limit in RelayTransaction? use a token bucket with an 80/s rate, and just create a global queue of transactions to relay onwards once we have tokens again if we run out?
1302025-09-22T10:43:19 <sipa> that lacks the nice quality-sorting we can do at inv time
1312025-09-22T10:43:41 <_aj_> we could quality-sort the RelayTransaction queue
1322025-09-22T10:44:41 <sipa> that would have the cpu-resource benefit of only doing the sorting oncew
1332025-09-22T10:44:48 <sipa> rather than for every peer
1342025-09-22T10:46:27 <_aj_> maybe? we'd need to go through the entire queue every now and then to drop stuff that's been removed from the mempool?
1352025-09-22T10:48:03 <_aj_> maybe as a global queue the mempool could manage it and directly remove txs from it though
1362025-09-22T10:49:15 *** Zenton_ <Zenton_!~Zenton@user/zenton> has quit IRC (Quit: Leaving)
1372025-09-22T10:49:26 <sipa> but you'd still need per-peer data to know what has been relayed to them alreasy
1382025-09-22T10:49:48 <sipa> though, the alreadyknown filter already partially has this information
1392025-09-22T10:50:16 <sipa> this is sounding a bit like dzxzg's idea earlier
1402025-09-22T10:51:02 *** Zenton <Zenton!~Zenton@user/zenton> has joined #bitcoin-core-dev
1412025-09-22T10:54:15 *** cold <cold!~cold@user/cold> has quit IRC (Ping timeout: 252 seconds)
1422025-09-22T10:54:15 *** midnight <midnight!~midnight@user/midnight> has quit IRC (Ping timeout: 252 seconds)
1432025-09-22T10:54:38 *** cold <cold!~cold@user/cold> has joined #bitcoin-core-dev
1442025-09-22T10:55:09 *** midnight <midnight!~midnight@user/midnight> has joined #bitcoin-core-dev
1452025-09-22T11:01:24 <_aj_> sipa: if you cap the RelayTransaction rate at 80/s, and do 0.08*q for inv, i think that caps the per-peer q at perhaps 5000 txs?
1462025-09-22T11:02:56 <_aj_> sipa: (ie, 1000 in the queue due to sustained load, plus a minute's worth of 80/s txs for another 4800, where a minute between invs happens maybe once every 9 days?
1472025-09-22T11:04:21 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Remote host closed the connection)
1482025-09-22T11:04:46 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
1492025-09-22T11:12:30 *** f321x <f321x!~f321x@user/f321x> has quit IRC (Remote host closed the connection)
1502025-09-22T11:12:54 *** f321x <f321x!~f321x@user/f321x> has joined #bitcoin-core-dev
1512025-09-22T11:18:45 <_aj_> sipa: maybe could have a set<txiter> of unrelayed txs managed by the mempool, sorted by quality; and use the quality lookup to remove tx from the set when they're removed from the mempool? would be removing and reinserting when the quality score changes (if chunking changes?) though
1522025-09-22T11:23:21 <sipa> _aj_: and refcounted by how many peers it still needs to be relayed to?
1532025-09-22T11:25:32 <_aj_> sipa: i think it gets relayed to everyone that's currently connected as soon as it gets a token?
1542025-09-22T11:28:36 <_aj_> sipa: i guess could track time and compare against CNode::m_connected or perhaps track VERACK time or mempool sequence?
1552025-09-22T11:33:35 <sipa> _aj_: could have a timeout, where transactions can only stay in the set of unrelayed txn for a finite amount of time, and if they reach that timeout (not evicted by better relayable ones, and not yet relayed to everyone), just blast it out
1562025-09-22T11:37:07 <_aj_> sipa: if you had a boost::multi_index instead of a set, a timeout would be easy to manage. would've gone with dropping (not relaying) rather than blasting out though. a set<txiter> is 32B per tx, so 100k txs in the queue is just 3MB, and if you've got 100k backlog dropping stuff at the bottom seems fine
1572025-09-22T11:37:25 <_aj_> sipa: oh, the other thing you could do is increase the mempool minfee when the to-relay queue gets too big
1582025-09-22T11:39:11 <_aj_> (or have a separate "min incoming fee" and increase that and apply it to feefilter)
1592025-09-22T11:48:30 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Remote host closed the connection)
1602025-09-22T11:48:50 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
1612025-09-22T11:58:25 *** f321x <f321x!~f321x@user/f321x> has quit IRC (Remote host closed the connection)
1622025-09-22T11:58:38 *** f321x <f321x!~f321x@user/f321x> has joined #bitcoin-core-dev
1632025-09-22T12:02:48 *** f321x <f321x!~f321x@user/f321x> has quit IRC (Remote host closed the connection)
1642025-09-22T12:02:59 *** f321x <f321x!~f321x@user/f321x> has joined #bitcoin-core-dev
1652025-09-22T12:10:51 *** Artea <Artea!~Lufia@artea.pt> has quit IRC (Ping timeout: 244 seconds)
1662025-09-22T12:29:17 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Quit: = "")
1672025-09-22T12:53:46 *** TheRec_ <TheRec_!~toto@84-74-100-31.dclient.hispeed.ch> has quit IRC (Read error: Connection reset by peer)
1682025-09-22T12:54:29 *** TheRec <TheRec!~toto@84-74-100-31.dclient.hispeed.ch> has joined #bitcoin-core-dev
1692025-09-22T12:57:14 *** Cory18 <Cory18!~Cory18@user/pasha> has quit IRC (Quit: Client closed)
1702025-09-22T12:57:40 *** Cory18 <Cory18!~Cory18@user/pasha> has joined #bitcoin-core-dev
1712025-09-22T13:01:26 <sipa> _aj_: i'm wondering if post-cluster-mempool, we could do something like keep per-peer an iterator into the chunk index ("mostly relayed every chunk with feerates higher than this") + a set of unrelayed transactions before that point
1722025-09-22T13:02:58 <sipa> and at inv time, first take from the unrelayed set (using the existing heapify approach, i guess), and if it empties, start advancing the iterator
1732025-09-22T13:03:56 <sipa> effectively making the entire chunk index the set of to-be-relayed transactions
1742025-09-22T13:05:21 <sipa> it doesn't even need to be an iterator; for layer separation it'd be fine to just store a per-peer chunk feerate, and a set of transactions whose chunk feerate is (or was, at some point) higher than that
1752025-09-22T13:28:39 *** PaperSword <PaperSword!~Thunderbi@securemail.qrsnap.io> has quit IRC (Remote host closed the connection)
1762025-09-22T13:28:58 *** PaperSword <PaperSword!~Thunderbi@securemail.qrsnap.io> has joined #bitcoin-core-dev
1772025-09-22T13:41:59 *** Christoph_ <Christoph_!~Christoph@2a02:810d:1399:b700:a4db:8f22:bafe:4c87> has joined #bitcoin-core-dev
1782025-09-22T14:11:14 *** f321x <f321x!~f321x@user/f321x> has quit IRC (Quit: f321x)
1792025-09-22T14:39:23 <_aj_> sipa: i don't see how that would work at all? we'll get new transactions both above and below the iterator, and need to keep track of anything not relayed in either case?
1802025-09-22T14:41:37 <sipa> well you don't need to keep track of any transaction with a feerate below the "up to this feerate" value
1812025-09-22T14:41:56 <sipa> because it's just implicitly all transactions whose feerate below that point that still need to be relayed
1822025-09-22T14:42:28 <sipa> but it may indeed not gain us much, as in the steady state, that feerate will equal the feefilter rate
1832025-09-22T14:44:55 <_aj_> sipa: if your mempool has feerates from 10sat/vb to 50sat/vb, and you've relayed everything, and your iterator is at 50sat/vb; then you get a huge mass of txs in the 20sat/vb to 120sat/vb range, your pointer will just get stuck at 20sat/vb and not do you any good?
1842025-09-22T14:45:28 <_aj_> oh, below that point, so it's stuck at 10sat/vb forever
1852025-09-22T14:47:37 <sipa> i guess the feerate i'm imagining being stored is "the lowest chunk feerate of any mempool transaction which you've relayed to this peer"
1862025-09-22T14:47:56 <sipa> anything with a lower feerate you don't need to add to the set
1872025-09-22T14:48:57 <sipa> but it sounds like a mess to keep track of, and i'm not sure it really helps with anything
1882025-09-22T14:49:37 *** Christoph_ <Christoph_!~Christoph@2a02:810d:1399:b700:a4db:8f22:bafe:4c87> has quit IRC (Quit: Christoph_)
1892025-09-22T14:50:06 <_aj_> i just can't see how this can do anything useful? you'll have relayed txs both above and below any pointer (above because that's priority, below because they're old and there was less pressure), and you'll get new txs both above and below, so you have to track the ones below (because they're less likely to be sent) and may have to track the ones above (if the rate becomes too high)?
1902025-09-22T14:51:00 *** Guyver2 <Guyver2!Guyver@77-174-98-73.fixed.kpn.net> has left #bitcoin-core-dev (Closing Window)
1912025-09-22T14:51:04 <sipa> yeah
1922025-09-22T14:51:18 <sipa> please disregard
1932025-09-22T14:51:39 <_aj_> you could invert the logic at a point -- track the ones to be relayed above a point, and track the ones already relayed below that point; but that seems fiddly and probably not useful
1942025-09-22T14:54:24 *** f321x <f321x!~f321x@user/f321x> has joined #bitcoin-core-dev
1952025-09-22T15:06:12 *** Christoph_ <Christoph_!~Christoph@2a02:810d:1399:b700:a4db:8f22:bafe:4c87> has joined #bitcoin-core-dev
1962025-09-22T15:18:56 <instagibbs> https://github.com/lightning/bolts/pull/1292 another great entry in the annals of mini*
1972025-09-22T15:24:38 *** Christoph_ <Christoph_!~Christoph@2a02:810d:1399:b700:a4db:8f22:bafe:4c87> has quit IRC (Quit: Christoph_)
1982025-09-22T15:25:00 *** Christoph_ <Christoph_!~Christoph@2a02:810d:1399:b700:a4db:8f22:bafe:4c87> has joined #bitcoin-core-dev
1992025-09-22T15:31:01 *** enochazariah <enochazariah!~enochazar@2c0f:2a80:ed:5010:718:59e9:59b3:afd9> has joined #bitcoin-core-dev
2002025-09-22T15:31:01 *** Christoph_ <Christoph_!~Christoph@2a02:810d:1399:b700:a4db:8f22:bafe:4c87> has quit IRC (Quit: Christoph_)
2012025-09-22T15:31:21 *** Christoph_ <Christoph_!~Christoph@2a02:810d:1399:b700:a4db:8f22:bafe:4c87> has joined #bitcoin-core-dev
2022025-09-22T15:31:35 *** dermoth <dermoth!~dermoth@user/dermoth> has quit IRC (Read error: Connection reset by peer)
2032025-09-22T15:34:53 *** Christoph_ <Christoph_!~Christoph@2a02:810d:1399:b700:a4db:8f22:bafe:4c87> has quit IRC (Client Quit)
2042025-09-22T15:35:46 *** dermoth <dermoth!~dermoth@user/dermoth> has joined #bitcoin-core-dev
2052025-09-22T15:54:37 *** eugenesiegel <eugenesiegel!~eugenesie@user/eugenesiegel> has joined #bitcoin-core-dev
2062025-09-22T16:01:34 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
2072025-09-22T16:07:47 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Read error: Connection reset by peer)
2082025-09-22T16:08:18 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
2092025-09-22T16:08:43 *** Cory18 <Cory18!~Cory18@user/pasha> has quit IRC (Quit: Client closed)
2102025-09-22T16:09:04 *** Cory18 <Cory18!~Cory18@user/pasha> has joined #bitcoin-core-dev
2112025-09-22T16:16:51 *** Cory50 <Cory50!~Cory18@user/pasha> has joined #bitcoin-core-dev
2122025-09-22T16:20:09 *** Cory18 <Cory18!~Cory18@user/pasha> has quit IRC (Ping timeout: 250 seconds)
2132025-09-22T16:38:33 *** jon_atack <jon_atack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
2142025-09-22T16:38:36 *** f321x <f321x!~f321x@user/f321x> has quit IRC (Quit: f321x)
2152025-09-22T16:40:39 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 258 seconds)
2162025-09-22T16:48:21 *** enochazariah <enochazariah!~enochazar@2c0f:2a80:ed:5010:718:59e9:59b3:afd9> has quit IRC (Quit: Client closed)
2172025-09-22T16:48:30 *** enochazariah <enochazariah!uid710351@id-710351.hampstead.irccloud.com> has joined #bitcoin-core-dev
2182025-09-22T16:49:14 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
2192025-09-22T16:51:00 *** jon_atack <jon_atack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 258 seconds)
2202025-09-22T16:51:03 *** jonatack1 <jonatack1!~jonatack@user/jonatack> has joined #bitcoin-core-dev
2212025-09-22T16:51:46 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Read error: Connection reset by peer)
2222025-09-22T16:52:01 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has quit IRC (Remote host closed the connection)
2232025-09-22T16:52:25 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
2242025-09-22T16:53:35 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has joined #bitcoin-core-dev
2252025-09-22T16:55:33 *** brunoerg <brunoerg!~brunoerg@189.112.73.61> has joined #bitcoin-core-dev
2262025-09-22T16:55:37 *** jonatack1 <jonatack1!~jonatack@user/jonatack> has quit IRC (Ping timeout: 250 seconds)
2272025-09-22T17:04:57 *** jon_atack <jon_atack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
2282025-09-22T17:06:43 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 258 seconds)
2292025-09-22T17:11:00 *** brunoerg <brunoerg!~brunoerg@189.112.73.61> has quit IRC (Remote host closed the connection)
2302025-09-22T17:12:12 *** Talkless <Talkless!~Talkless@138.199.6.197> has joined #bitcoin-core-dev
2312025-09-22T17:25:42 *** Guest60 <Guest60!~Guest60@141.255.164.210> has joined #bitcoin-core-dev
2322025-09-22T17:26:02 *** Guest60 <Guest60!~Guest60@141.255.164.210> has quit IRC (Client Quit)
2332025-09-22T17:26:23 *** andytoshi <andytoshi!~apoelstra@user/andytoshi> has quit IRC (Ping timeout: 250 seconds)
2342025-09-22T17:35:12 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
2352025-09-22T17:35:20 *** sliv3r__ <sliv3r__!~sliv3r__@user/sliv3r-:76883> has quit IRC (Ping timeout: 245 seconds)
2362025-09-22T17:36:30 *** sliv3r__ <sliv3r__!~sliv3r__@user/sliv3r-:76883> has joined #bitcoin-core-dev
2372025-09-22T17:37:21 *** jon_atack <jon_atack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 265 seconds)
2382025-09-22T17:40:31 *** jon_atack <jon_atack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
2392025-09-22T17:42:39 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 244 seconds)
2402025-09-22T18:06:08 *** TheRec <TheRec!~toto@user/therec> has quit IRC (Ping timeout: 258 seconds)
2412025-09-22T18:07:02 *** Cory7 <Cory7!~Cory50@user/pasha> has joined #bitcoin-core-dev
2422025-09-22T18:08:43 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
2432025-09-22T18:09:43 *** mudsip <mudsip!~mudsip@user/mudsip> has joined #bitcoin-core-dev
2442025-09-22T18:10:21 *** mudsip <mudsip!~mudsip@user/mudsip> has quit IRC (Client Quit)
2452025-09-22T18:10:39 *** Cory50 <Cory50!~Cory18@user/pasha> has quit IRC (Ping timeout: 250 seconds)
2462025-09-22T18:11:01 *** jon_atack <jon_atack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 250 seconds)
2472025-09-22T18:15:37 <darosior> hah
2482025-09-22T18:23:07 *** TheRec <TheRec!~toto@84-74-100-31.dclient.hispeed.ch> has joined #bitcoin-core-dev
2492025-09-22T18:29:40 *** TheRec <TheRec!~toto@user/therec> has quit IRC (Ping timeout: 244 seconds)
2502025-09-22T18:30:32 *** TheRec <TheRec!~toto@user/therec> has joined #bitcoin-core-dev
2512025-09-22T18:37:59 *** andytoshi <andytoshi!~apoelstra@user/andytoshi> has joined #bitcoin-core-dev
2522025-09-22T18:40:31 *** Christoph_ <Christoph_!~Christoph@2a02:810d:1399:b700:a4db:8f22:bafe:4c87> has joined #bitcoin-core-dev
2532025-09-22T18:40:39 *** Christoph_ <Christoph_!~Christoph@2a02:810d:1399:b700:a4db:8f22:bafe:4c87> has quit IRC (Client Quit)
2542025-09-22T18:48:23 *** Christoph_ <Christoph_!~Christoph@2a02:810d:1399:b700:a4db:8f22:bafe:4c87> has joined #bitcoin-core-dev
2552025-09-22T18:51:09 *** eugenesiegel <eugenesiegel!~eugenesie@user/eugenesiegel> has quit IRC (Quit: Client closed)
2562025-09-22T18:52:31 *** eugenesiegel <eugenesiegel!~eugenesie@user/eugenesiegel> has joined #bitcoin-core-dev
2572025-09-22T19:01:47 *** eugenesiegel <eugenesiegel!~eugenesie@user/eugenesiegel> has quit IRC (Ping timeout: 250 seconds)
2582025-09-22T19:13:18 *** Talkless <Talkless!~Talkless@138.199.6.197> has quit IRC (Quit: Konversation terminated!)
2592025-09-22T19:15:35 *** jon_atack <jon_atack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
2602025-09-22T19:17:12 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 244 seconds)
2612025-09-22T19:22:24 *** jespada <jespada!~jespada@2800:a4:220e:1100:7986:c3b7:972a:6739> has joined #bitcoin-core-dev
2622025-09-22T19:26:02 *** Christoph_ <Christoph_!~Christoph@2a02:810d:1399:b700:a4db:8f22:bafe:4c87> has quit IRC (Quit: Christoph_)
2632025-09-22T19:40:39 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
2642025-09-22T19:42:53 *** jon_atack <jon_atack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 250 seconds)
2652025-09-22T19:48:49 *** brunoerg <brunoerg!~brunoerg@189.112.73.61> has joined #bitcoin-core-dev
2662025-09-22T19:49:38 *** Christoph_ <Christoph_!~Christoph@2a02:810d:1399:b700:a4db:8f22:bafe:4c87> has joined #bitcoin-core-dev
2672025-09-22T19:52:01 *** Christoph_ <Christoph_!~Christoph@2a02:810d:1399:b700:a4db:8f22:bafe:4c87> has quit IRC (Client Quit)
2682025-09-22T19:56:51 *** jon_atack <jon_atack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
2692025-09-22T19:59:02 *** Cory75 <Cory75!~Cory7@user/pasha> has joined #bitcoin-core-dev
2702025-09-22T19:59:13 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 258 seconds)
2712025-09-22T20:02:27 *** Cory7 <Cory7!~Cory50@user/pasha> has quit IRC (Ping timeout: 250 seconds)
2722025-09-22T20:15:48 *** jespada <jespada!~jespada@2800:a4:220e:1100:7986:c3b7:972a:6739> has quit IRC (Quit: Textual IRC Client: www.textualapp.com)
2732025-09-22T20:31:36 *** jespada <jespada!~jespada@2800:a4:220e:1100:c085:e42:ccd1:a8e7> has joined #bitcoin-core-dev
2742025-09-22T20:42:29 *** brunoerg <brunoerg!~brunoerg@189.112.73.61> has quit IRC (Remote host closed the connection)
2752025-09-22T20:44:20 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has quit IRC (Remote host closed the connection)
2762025-09-22T20:45:50 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has joined #bitcoin-core-dev
2772025-09-22T20:53:46 *** jespada <jespada!~jespada@2800:a4:220e:1100:c085:e42:ccd1:a8e7> has quit IRC (Quit: My Mac has gone to sleep. ZZZzzzâ¦)
2782025-09-22T21:02:57 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
2792025-09-22T21:05:09 *** jon_atack <jon_atack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 258 seconds)
2802025-09-22T21:13:55 *** Christoph_ <Christoph_!~Christoph@2a02:810d:1399:b700:a4db:8f22:bafe:4c87> has joined #bitcoin-core-dev
2812025-09-22T21:22:28 *** Christoph_ <Christoph_!~Christoph@2a02:810d:1399:b700:a4db:8f22:bafe:4c87> has quit IRC (Quit: Christoph_)
2822025-09-22T21:58:07 *** enochazariah <enochazariah!uid710351@id-710351.hampstead.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)
2832025-09-22T22:11:20 *** jon_atack <jon_atack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
2842025-09-22T22:13:23 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 244 seconds)
2852025-09-22T22:17:21 *** enochazariah <enochazariah!uid710351@id-710351.hampstead.irccloud.com> has joined #bitcoin-core-dev
2862025-09-22T22:21:57 *** Guest32 <Guest32!~Guest32@41.188.115.110> has joined #bitcoin-core-dev
2872025-09-22T22:23:55 *** Guest32 <Guest32!~Guest32@41.188.115.110> has quit IRC (Client Quit)
2882025-09-22T22:26:18 *** Guest32 <Guest32!~Guest32@41.188.115.110> has joined #bitcoin-core-dev
2892025-09-22T22:27:27 *** Guest96 <Guest96!~Guest32@41.188.115.110> has joined #bitcoin-core-dev
2902025-09-22T22:39:50 *** Guest32 <Guest32!~Guest32@41.188.115.110> has quit IRC (Quit: Client closed)
2912025-09-22T22:40:52 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
2922025-09-22T22:44:17 *** l0rinc_ <l0rinc_!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
2932025-09-22T22:45:23 *** l0rinc_ <l0rinc_!~l0rinc@user/l0rinc> has quit IRC (Client Quit)
2942025-09-22T22:45:25 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Ping timeout: 244 seconds)
2952025-09-22T22:45:54 *** Christoph_ <Christoph_!~Christoph@2a02:810d:1399:b700:a4db:8f22:bafe:4c87> has joined #bitcoin-core-dev
2962025-09-22T22:47:29 *** Christoph_ <Christoph_!~Christoph@2a02:810d:1399:b700:a4db:8f22:bafe:4c87> has quit IRC (Client Quit)
2972025-09-22T22:50:06 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
2982025-09-22T22:51:42 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Client Quit)
2992025-09-22T22:53:12 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
3002025-09-22T23:00:55 *** jon_atack <jon_atack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 258 seconds)
3012025-09-22T23:02:41 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
3022025-09-22T23:10:31 *** Guest96 <Guest96!~Guest32@41.188.115.110> has quit IRC (Ping timeout: 250 seconds)
3032025-09-22T23:21:02 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Read error: Connection reset by peer)
3042025-09-22T23:21:08 *** l0rinc_ <l0rinc_!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
3052025-09-22T23:37:42 *** l0rinc_ <l0rinc_!~l0rinc@user/l0rinc> has quit IRC (Quit: l0rinc_)
3062025-09-22T23:40:05 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
3072025-09-22T23:46:37 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has quit IRC (Read error: Connection reset by peer)
3082025-09-22T23:48:23 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has joined #bitcoin-core-dev