Sibling Eviction for v3 transactions

Let’s see if I understand correctly… With only 1p1c package relay and package RBF, the following v3 package replacement works:

    flowchart
         A[A: 0 sat/vB]
         B[B: 50 sat/vB]
         A'[A': 0 sat/vB]
         B'[B': 100 sat/vB]
         A --> B
         A' --> B'

And this v3 package replacement works:

    flowchart
         A[A: 0 sat/vB]
         B[B: 50 sat/vB]
         A'[A: 0 sat/vB]
         B'[B': 100 sat/vB]
         A --> B
         A' --> B'

But this v3 package replacement doesn’t?:

    flowchart
         A[A: 0 sat/vB]
         B[B: 50 sat/vB]
         A'[A: 0 sat/vB]
         C[C: 100 sat/vB]
         A --> B
         A' --> C

In that case, I say yes we definitely want sibling eviction, since that’s the most intuitive behavior. Package RBF should mean that the A-C package can replace the A-B package if A-C has better fees. Intuitively, it shouldn’t matter whether A is already in the mempool or not; the entire v3 package should be considered for RBF.

1 Like