Attacker Can Manipulate Reward Rates to Cause Other Stakers' Losses in Rewards

Incorrect Repayment Calculation (token0 vs token1) in Withdraw Function Leads to Asset Losses or Liquidation

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

Ineffective proposal threshold validation allows setting arbitrary high values

Uniform Market Rate Restriction Risks Limiting Leveraged Token Excess Gains and Bond Token Priority in Redemption

quantAMMSwapFeeTake used for both getQuantAMMSwapFeeTake and getQuantAMMUpliftFeeTake.

Users can claim more that their actual allotment

Accumulated ETH in the LamboVEthRouter will be irretrievable

update_emergency_council_7_D_0_C_1_C_58() updates nft manager instead of emergency council

Parameter Misordering in Fee Collection Function Causes Denial of Service and Fee Loss

Unnecessary balance checks and precision issues in TokenManager::_transfer

Rounding Discrepancies in Deposit Amount Calculations

Incorrect Check in closeBidOffer function

Wrong minting logic based on total token count across generations

TraitForgeNft: Generations without a golden god are possible

Single plot can be occupied by multiple renters

`Registry.sol#updateHoldingPosition` remove position logic is incorrect: should use `ownerConnector` instead of `calculatorConnector` when calculating holdingPositionId.

Liquidating positions with bounded Kerosen could be unprofitable for liquidators