XDM FAQ
Since launching Crossing the Narrow Sea we are seeing a number of recurring questions. This post aims to draw them all together.
This FAQ will be edited as we go along so it will be worth checking back from time to time.
Protocol/Node
Operator node reports ERROR messages
Q: I am seeing ERROR messages such as the below in my operator logs:
ERROR Consensus: domain_message_listener: Failed to submit XDM[RelayResponseMessage((Domain(DomainId(0)), 9, 16267))] to tx pool for Chain Consensus with error: TemporarilyBanned at block: BlockId { number: 1830821, hash: 0x29c4fb6b463e3e6b5cf05e1d0b4bc6044dea43a5ba607df1adaf7212bf900668 }
ERROR Domain: domain_message_listener: Failed to submit XDM[RelayMessage((Consensus, 8, 2477))] to tx pool for Chain Domain(DomainId(0)) with error: Pool(TooLowPriority { old: 1, new: 1 }) at block: BlockId { number: 1101679, hash: 0x348c9a120419f52b1e519d8564f75da75c95f5ffb5090be77ad6e12928d3b297 }
ERROR Domain: domain_message_listener: Failed to update channel update from Consensus to Domain(DomainId(0)): MissingBlockHash
ERROR Domain: domain_message_listener: Failed to update channel update from Consensus to Domain(DomainId(0)): MissingRecieptHash
A: These are all fine to ignore and are being downgraded in Downgrade xdm message listener errors to debug by vedhavyas · Pull Request #3461 · autonomys/subspace · GitHub
Increased operator node RAM usage
Q: I am seeing increased RAM usage since when there are lots of pending XDM transactions (check XDM utilisation here).
A: This is being investigated but is likely due to the number of XDM messages in the transaction pool.