Currently, EventQueue only supports 4 topics where for transaction processing, the 1st topic is added a transactionID. However in case of CCM processing, we add another default on top of transactionID which only allows 2 more custom topics to be added by events. One of them is CCMSendSuccess event where number of topics become 5 during CCM processing which will throw error and abrupt the course of CCM processing.
We need to replace transactionID as with ccmID as defaultTopic instead of adding on top of it which will bring down the topic count in the above case to 4 which is the permissible limit.
Also, since off chain services rely on the first topic as transactionID, in order to identify transactionID from ccmID we need to add some extra unique bytes for each of these IDs.
Which version(s) does this affect? (Environment, OS, etc...)
Description
Currently, EventQueue only supports 4 topics where for transaction processing, the 1st topic is added a transactionID. However in case of CCM processing, we add another default on top of transactionID which only allows 2 more custom topics to be added by events. One of them is CCMSendSuccess event where number of topics become 5 during CCM processing which will throw error and abrupt the course of CCM processing.
We need to replace transactionID as with ccmID as defaultTopic instead of adding on top of it which will bring down the topic count in the above case to 4 which is the permissible limit. Also, since off chain services rely on the first topic as transactionID, in order to identify transactionID from ccmID we need to add some extra unique bytes for each of these IDs.
Which version(s) does this affect? (Environment, OS, etc...)
6.0.0-rc.3