Skip to content

Conversation

@UdjinM6
Copy link

@UdjinM6 UdjinM6 commented Jan 27, 2021

No description provided.

unordered_lru_cache should truncate it automagically
Check islock hash against both current and archived islocks
… first

Two reasons:
1. GetTransaction is a potentially much heavy one
2. Doesn't make much sense to look for a tx if we have a known islock already
… CL-ed block as conflicting and not as invalid
`!info.tx == res.second` is always `true`
Instead of sleeping only when no work has been done.
Avoids useless cycles, improves batching.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant