Calling the binary protocol in the "cascade effect" without updating and checking the parity of the block in the previous iterations was causing the algorithm to have really big error rates.
Solution was to save the parities of past iterations and update all of them on each bit fix, then check them before calling the binary protocol (this was only checked for the first correction of the cascade effect)
Calling the binary protocol in the "cascade effect" without updating and checking the parity of the block in the previous iterations was causing the algorithm to have really big error rates.
Solution was to save the parities of past iterations and update all of them on each bit fix, then check them before calling the binary protocol (this was only checked for the first correction of the cascade effect)