If the client was reconnected to subscribeToTransactionsWithProofs or it was connected after transaction was emitted, there will be no instantLock event emitted.
What was done?
Scan mempool for new transactions
How Has This Been Tested?
Breaking Changes
No
Checklist:
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added or updated relevant unit/integration/functional/e2e tests
[x] I have made corresponding changes to the documentation
For repository code-owners and collaborators only
[x] I have assigned this pull request to a milestone
Issue being fixed or feature implemented
If the client was reconnected to
subscribeToTransactionsWithProofsor it was connected after transaction was emitted, there will be no instantLock event emitted.What was done?
Scan mempool for new transactions
How Has This Been Tested?
Breaking Changes
No
Checklist:
For repository code-owners and collaborators only