You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Test case that shows the problem: https://github.com/VeriBlock/alt-integration-cpp/blob/ffb90e4d8a2c321dc011a3b73f421f55fce67197/test/pop/mempool_test.cpp#L490
In short:
VBK8 contains VTB0 with BTC[1..(6)]
VBK9 contains VTB1 with BTC[8..(9)]
VBK10 contains VTB2 with BTC[7..(11)]
VTB1 can not be connected to active chain, because its context starts at 8, but last known is 6. It does connect only to FUTURE block, because it brings missing BTC7.
In presence of this scenario, the fix is to search for another VTB which brings BTC7, but whose containing block is <=VBK9, and likely to be >= VBK8
Similar to context gap issue, but worth noting difference between (A) initially starting new chain, (B) existing chain stops for a few days and cannot fill the gap.
Related to these other issues:
ALT-646
NCS-339
ALT-706
The text was updated successfully, but these errors were encountered:
Test case that shows the problem: https://github.com/VeriBlock/alt-integration-cpp/blob/ffb90e4d8a2c321dc011a3b73f421f55fce67197/test/pop/mempool_test.cpp#L490
In short:
VBK8 contains VTB0 with BTC[1..(6)]
VBK9 contains VTB1 with BTC[8..(9)]
VBK10 contains VTB2 with BTC[7..(11)]
VTB1 can not be connected to active chain, because its context starts at 8, but last known is 6. It does connect only to FUTURE block, because it brings missing BTC7.
In presence of this scenario, the fix is to search for another VTB which brings BTC7, but whose containing block is <=VBK9, and likely to be >= VBK8
Similar to context gap issue, but worth noting difference between (A) initially starting new chain, (B) existing chain stops for a few days and cannot fill the gap.
Related to these other issues:
ALT-646
NCS-339
ALT-706
The text was updated successfully, but these errors were encountered: