The calculation of `totalAssets()` could be wrong if `operatorFeeAmount` > 0, this can cause potential loss for the new depositors

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

Players Claiming Refunds in Canceled Raffles Will Cause ETH to Be Stuck in the `WinnablesTicketManager` Contract

Malicious user can block prize distribution and raffle cancellation in `WinnablesTicketManager`

Malicious User Can Brick Protocol and Drain Funds by Repeatedly Canceling Raffles in `WinnablesTicketManger`

Admin Can Manipulate Raffle Outcomes by Minting Unlimited Tickets

Admin Can Exploit Raffle System to Steal Funds and Block Prize Claims

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

The maximum number of generations is infinite

Number of entities in generation can surpass the 10k number

Griefing attack on seller's airdrop benefits

Wrong minting logic based on total token count across generations

Pause and unpause functions are inaccessible

NFTs mature too slowly under default settings.

Discrepancy between nfts minted, price of nft when a generation changes & position of `_incrementGeneration()` inside `_mintInternal()` & `_mintNewEntity()`

Holders array can be manipulated by transferring or burning with amount 0, stealing rewards or bricking certain functions

Distribution can be bricked, and double claims by a few holders are possible when owner calls `LiquidInfrastructureERC20::setDistributableERC20s`

Unrestricted claiming of fees due to missing balance updates in `FeeSplitter`

Protocol and referral fee would be permanently stuck in the Curves contract when selling a token

onBalanceChange causes previously unclaimed rewards to be cleared

Withdrawing with amount = 0 will forcefully set name and symbol to default and disable some functions for token subject

If a user sets their curve token symbol as the default one plus the next token counter instance it will render the whole default naming functionality obsolete