Antoine Riard

> Even though we don't have cluster limits, we are able to treat these transactions as having as having a maximum cluster size of 2. I don’t think adopting cluster...

> Also I think we should resurrect https://github.com/bitcoin/bitcoin/pull/27018 so that we will mine everything in the mempool, but that doesn't need to be in this PR (and probably isn't strictly...

On the first line of arguments, I think zero-conf business acceptance have the option to deploy additional full-nodes with good transaction-relay peering to obtain a reasonable view of network mempools,...

@luke-jr @petertodd As someone that can claim to be your technical peer and with experience in consensus development, I would appreciate if you can publish on the communication space of...

@psztorc > This area is for discussing the Approach/Implementation. Everything else is off-topic. There is an uncertainty on the open-source status of the technical contributions due to the apparent mode...

@psztorc > Not to me. The source code is in the pull request. Publishing the code is in the open does not minimize intellectual property hostile claims towards the project...

From my understanding of the proposal, there is an intuition of aligning mining (i.e the maximum fees in a block template) and transactions evicted from our local mempools. The proposed...

> If I'm understanding your post correctly, you're asking whether the mempool design I'm proposing is consistent with having some sort of external-to-the-mempool cache of transactions? That really sounds like...

> Mostly that STANDARD_SCRIPT_VERIFY_FLAGS violations sounds like something that acceptnonstdtxn should allow. But some particular examples: I think this is valuable for experimentation to allow non-standard scripts with `-accetnonstdtxn=1`, though...

> I think any time you want more granularity, you should just define the new standardness rule and implement it. Yes this is one policy rules design viewpoint. The pitfall...