by Λ L Ξ X / アレクサンダー.eth
"Ship it!"
We are having delays due to UBQ rewards having had gone off the rails.
Zgo & Zapaz (DeFi veterans) wrapped up the BondingV2 smart contract while Zequez (our latest engineering hire and also new to DeFi!) handled the frontend changes in parallel.
Zgo, myself, and 3commascapital (all devs) jumped in with the migration from v1 → v2 to test drive the new UI. During the initial testing we ran into several issues, including but not limited to this:
We accidentally created a scamcoin zillion percent APY farm ??
Updated claim widget with MasterChefV2 by Zequez · Pull Request #8 · pavlovcik/uad-ui-launch
At this point, we were quite certain it was the new hire who made a mistake with the calculations. After personally looking through the UI code; the horror dawned on me. The UI code was all correct. Immediately afterward, I queried the smart contract directly.
Our Solidity goose has been cooked.
And thus began the wild goose chase with the uAD protocol team.
The first action taken was that we disabled the rewards emissions for BondingV2 in case anybody else figured what happened at the same time as us. Next, the team went spelunking deep into the Solidity source code and speculated an uint underflow...
The underflow hypothesis was less favored over the realization of the use of different precisions for the division.
Zgo was eventually able to inspect more closely and identify what likely is causing the issue:
Soon after, a pull request (a proposed fix) was made.