In the current Stacks chain, transactions that remain unconfirmed for 256 blocks are automatically canceled. This can occur when a transaction has an incorrect nonce. How will this scenario be handled in the updated Nakamoto Stacks chain?
This has been updated in epoch 3.0 to evict transactions based on receive time instead of block height. See code here - stacks-core/stackslib/src/core/mempool.rs at dd2404a19235a25c2e863b0ea6cc89b7603c2407 · stacks-network/stacks-core · GitHub
Thank you Brice.