https://github.com/code-423n4/2024-02-althea-liquid-infrastructure/blob/bd6ee47162368e1999a0a5b8b17b701347cf9a7d/liquid-infrastructure/contracts/LiquidInfrastructureERC20.sol#L473
https://github.com/code-423n4/2024-02-althea-liquid-infrastructure/blob/bd6ee47162368e1999a0a5b8b17b701347cf9a7d/liquid-infrastructure/contracts/LiquidInfrastructureERC20.sol#L441C1-L445C6
https://github.com/code-423n4/2024-02-althea-liquid-infrastructure/blob/bd6ee47162368e1999a0a5b8b17b701347cf9a7d/liquid-infrastructure/contracts/LiquidInfrastructureNFT.sol#L108C1-L125C6
https://github.com/code-423n4/2024-02-althea-liquid-infrastructure/blob/bd6ee47162368e1999a0a5b8b17b701347cf9a7d/liquid-infrastructure/contracts/LiquidInfrastructureERC20.sol#L377
The constructor and the setDistributableERC20s allows the owner of the LiquidInfrastructureERC20 contract to set the ERC20 reward tokens to distribute. 
The owner of the LiquidInfrastructureNFT contract also has the ability to set the ERC20s as thresholds:
Which can later be withdrawn into the LiquidInfrastructureERC20 contract:
As theres no specific check, or enforcements that the withdrawERC20s are also set as parts of the distributableERC20s, these tokens being withdrawn into the LiquidInfrastructureERC20 stand the risk of being stranded if theyre not made distributable, as theres no other way to retrieve tokens from the contract.
Consider introducing a sweep function in the LiquidInfrastructureERC20 contract, or adding and using the getThresholds function, to get the array of withdrawERC20s and enforcing them as part of the distributableERC20s.
