Background
One big limitations of our current architecture is that nodes do "fire and forget" submission of transactions. This means that if transactions fail to be picked up by the blockchain for any reason (e.g. signature failure, invalid nonce etc.) the nodes are completely oblivious to this.
Unfortunately fixing this problem completely requires bigger architectural changes, but in the meantime, we should make it extremely easy to debug and track which transactions a node has submitted so an operator can manually check the status of these transactions on-chain.
User Story
As a node operator I'd like it to be easy to debug if my node's transactions are failing or missing on-chain.
Acceptance Criteria
We have a dedicated debug page that lists recently submitted transactions from the node with as much relevant info as possible (txid, nonce, signature etc.)
Resources & Additional Notes
Note: a problem a partner encountered was that when you submit several transactions from the same account in a short time period they may be processed out-of-order leading to transactions with lower nonces being rejected at times because a higher-nonce transaction was already included. This may explain some sporadic signature failures we're experiencing on-chain.
Background
One big limitations of our current architecture is that nodes do "fire and forget" submission of transactions. This means that if transactions fail to be picked up by the blockchain for any reason (e.g. signature failure, invalid nonce etc.) the nodes are completely oblivious to this.
Unfortunately fixing this problem completely requires bigger architectural changes, but in the meantime, we should make it extremely easy to debug and track which transactions a node has submitted so an operator can manually check the status of these transactions on-chain.
User Story
As a node operator I'd like it to be easy to debug if my node's transactions are failing or missing on-chain.
Acceptance Criteria
We have a dedicated debug page that lists recently submitted transactions from the node with as much relevant info as possible (txid, nonce, signature etc.)
Resources & Additional Notes
Note: a problem a partner encountered was that when you submit several transactions from the same account in a short time period they may be processed out-of-order leading to transactions with lower nonces being rejected at times because a higher-nonce transaction was already included. This may explain some sporadic signature failures we're experiencing on-chain.