Describe your idea, in simple words.
When using the local-tx-monitor protocol, the NextTx message will yield a NextTxResponse containing only a transaction id. While already useful in the case where transactions are all submitted locally, it may be problematic for nodes which receives transactions from peers (i.e. stake pools); transactions that they haven't seen explicitly, thus, not having any ways to link the id to something.
The idea is thus to extend the NextTx message with an optional format: "full" | "id-only" to let clients query full transactions on demand. As a result, the NextTxResponse would either contain a transaction id or a full (JSON) transaction.
Why is it a good idea?
The information is already available from the tx-monitor protocol, so it is needlessly restrictive to reduce it to the transaction id only. For clients running on top of stake pools, it is actually useful to be able to explore their mempool, including transactions which aren't coming from their local client.
Are you willing to work on it yourself?
Yes.
cc @sacrelege
Describe your idea, in simple words.
When using the local-tx-monitor protocol, the
NextTxmessage will yield aNextTxResponsecontaining only a transaction id. While already useful in the case where transactions are all submitted locally, it may be problematic for nodes which receives transactions from peers (i.e. stake pools); transactions that they haven't seen explicitly, thus, not having any ways to link the id to something.The idea is thus to extend the
NextTxmessage with an optionalformat: "full" | "id-only"to let clients query full transactions on demand. As a result, theNextTxResponsewould either contain a transaction id or a full (JSON) transaction.Why is it a good idea?
The information is already available from the tx-monitor protocol, so it is needlessly restrictive to reduce it to the transaction id only. For clients running on top of stake pools, it is actually useful to be able to explore their mempool, including transactions which aren't coming from their local client.
Are you willing to work on it yourself?
Yes.
cc @sacrelege