I’m using the Aeternal Middleware to get past events and subscribe for new ones. The following case is so confusing and annoying.
- Broadcast a transaction with
waitMinedflag set to
false- this will resolve the promise and give me as a result the transaction hash.
- Once the transaction is mined, the Aeternal emits a websocket event that the transaction is mined giving all the data, EXCEPT the one that’s needed to get the event data.
- In order to get the event data from the transaction I have to make additional request to the node to get it -
- The funny part - the node doesn’t know about the tx yet, because it’s not synced yet and the Aeternal middleware was synced first. So I receive an exception that the tx is not mined. Therefore the emiting of the event from the middleware was pointless, because you can’t get any valuable data from it.
I believe adding the log data to the webosocket event won’t be hard and won’t hurt anyone. This will bring lots of benefits - no more additional requests to the node to get the log datat, no more concurrency between the Aeternal and the node.