Closed LLFourn closed 1 year ago
One way to do this is to use an internal TxGraph
and we add changeset transactions one by one and check for conflicts with each add.
This is already done. It doesn't do descendants eviction but that's a problem everywhere.
This is already done. It doesn't do descendants eviction but that's a problem everywhere.
When creating its changeset
inflate_changeset
checks for conflicts with its local chain but doesn't not check for conflicts within the changeset that it is inflating. This allows it to create a contradictory changeset which it should not do.