Platypus attack exploited incorrect ordering of code, auditor claims

The misordered lines caused a solvency check to be performed before the user’s amount, factor, and rewardDebt had been set to zero

Read More

Share this post

Share on facebook
Share on twitter
Share on linkedin
Share on pinterest
Share on print
Share on email