similar to how the API currently returns the data, i think it would be a good addition if the stacks-node RPC also returned some nonce data about what's in the mempool.
api example:
in this case, it would be helpful to know there's a missing nonce in the mempool when only running a node locally (without having the extra overhead of running an API/postgres). I can see the benefit here mainly in local testing, where txs are being broadcast to localhost (i.e. on a regtest env where there's no need to run an API).
similar to how the API currently returns the data, i think it would be a good addition if the stacks-node RPC also returned some nonce data about what's in the mempool. api example:
in this case, it would be helpful to know there's a missing nonce in the mempool when only running a node locally (without having the extra overhead of running an API/postgres). I can see the benefit here mainly in local testing, where txs are being broadcast to localhost (i.e. on a regtest env where there's no need to run an API).
low priority, we can discuss after 3.0