Submitted by zzzitron
The function of the protocol could be impacted.  This proof of concept demonstrates the discarding of one of the duplicated locked splits. In the beginning it launches a project with two identical locked splits. As the owner of the project, it updates splits to only one of the two splits. Since all of original splits are locked both of them should still in the split after the update, but only one of them exists in the updated splits.
It happens because the check of the locked split is not suitable for duplicated cases.
Please see wardens original report for full details.
Either prevent duplicates in the splits or track the matches while checking the locked splits.
mejango (Juicebox) acknowledged, but disagreed with severity 
