Incorrect Logic in onlyOperator Modifier Leading to Denial-of-Service for Authorized Operators Across Critical Functions

Fee Recipient Shares Cannot Be Decreased When Total Fee recipients’s share is at Max Limit

Attacker can DoS in `DebitaLendOffer-Implementation::cancelOffer` Locking Users Funds

Incentive Exploit via Matching Lend and Borrow Offers

No LSTs transfer on node operator withdrawals resulting in stuck funds and loss for node operators

No way to update unbonding and claim periods

Failure to Delete Old Listings in `Listings::reserve` Allows Unauthorized Withdrawal of Reserved Items

Any user calling the `Locker::initializeCollection` function will loose both their ERC721 tokens and the ETH (WETH) they provide.

`shareBalance` bloating eventually blocks curator rewards distribution

`PhiFactory:claim` Potentially Causing Loss of Funds If `mintFee` Changed Beforehand

Refunds sent to incorrect addresses in certain cases

Incorrect Fee Handling Prevents Protocol from Updating Fees

[H-01] Incorrect Parameters in `WinnablesTicketManager::propagateRaffleWinner` Can Block Prize Claims

`mintToken()`, `mintWithBudget()`, and `forge()` in the `TraitForgeNft` Contract Will Fail Due to a Wrong Modifier Used in `EntropyGenerator.initializeAlphaIndices()`

Wrong minting logic based on total token count across generations