-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rare mempool synch warnings.. not so rare for this 1 user #216
Comments
Note to anybody reading this: The first error (1) above is expected to happen occasionally. It's just because it's impossible to synch the mempool 100% correctly in an atomic fashion since it's fast changing on BTC when mempool is full. Mempool synch is, in other words, "racey" .. as you synch it can change in inconsistent ways (mainly due to RBF, but not only). The other 2 errors are rarer .. i have never seen them happen .. the fact that they happened for you successively makes me curious as to WHY they happened in such a common fashion. In all cases the errors are recoverable and Fulcrum eventually settles. I will have to examine the other 2 errors though in more detail.. because something is fishy there. |
Update on frequency. Since my comment in #214, I've seen the the "3 assert" variant 5 times and the "4 assert" variant twice (yesterday and today). However, theses last 7 asserts are not close together at all (wrt time/block#) whereas the first occurrence was within a few blocks. |
Update on 1.9.6+. Testnet has been running for 2 days w/o issue - no asserts.
I have not seen the asserts metntioned in #141 now that I updated Mainnet. But I do see these variants of Tx dropped out of the mempool.
Are these normal and expected given the state of the mempool, that is, benign. Or something else?
Thanks
Originally posted by @Francisco-DAnconia in #214 (comment)
The text was updated successfully, but these errors were encountered: