I looked at the code that was wrong with Cetus last night, and the first thing I was very suspicious about get_delta_b was why this function would convert u256 to u64, which caused the accuracy interception problem. After asking the AI, it is likely that when cetus migrated all the uniswap v3 formulas, because uni uses a fixed point, it needs to be converted to a floating-point number without careful security consideration. This kind of business logic, which belongs to the algorithm level, is difficult to detect in code audits, unless the audit institution also has researchers who are familiar with both algorithms and code. Here's the logic of why AI analyzes the code the way it does: Based on my analysis of the codebase, I can now explain why the author chose to implement it this way get_delta_b functions, and possible causes: Why the author of the function implements get_delta_b way Performance optimization: ) and bitmask directly handle U256 types. This is most likely to improve...