Staking Protocol Patterns

Review the reward-per-token accumulator for precision loss and overflow, verify the first staker cannot claim all pending rewards, check lock enforcement on transfers, and confirm state updates happen before external calls. The included checklist covers reward calculation, locks, reentrancy, and edge cases.

First staker advantage occurs when rewardPerTokenStored is not updated while totalSupply is zero, letting the first staker claim all rewards accumulated since lastUpdateTime. The fix resets lastUpdateTime when the first deposit occurs.

Follow the checks-effects-interactions pattern by updating balances and reward state before transferring tokens, and apply a nonReentrant modifier to sensitive functions. Sending rewards before state updates allows attackers to re-enter and drain funds.

Precision loss happens when rewardRate multiplied by time delta is smaller than totalSupply, causing integer division to return zero. Multiplying by a high-precision factor like 1e18 before division preserves reward accuracy.

Yes, if the lock is only checked in the unstake function, users can transfer stake tokens to bypass it. Locks should be enforced in the token transfer hook or tracked per deposit.