Sandwich attacks remain one of the most exploitative patterns in decentralized finance. A malicious actor identifies a pending transaction, front-runs it with a higher gas bid to buy the same asset, then back-runs with a sell after the victim's transaction completes—all within the same block. The victim pays more for their purchase, the attacker pockets the spread, and the protocol's integrity degrades. For a bonding-curve reward token like Immute, where every buy and sell directly impacts the curve's state and every holder's dividend distribution, preventing this vector isn't optional. It's structural. This post walks through the smart contract sandwich attack prevention mechanisms built into Immute's IMT token, specifically the per-address buy-lock window that blocks front-run-buy and back-run-sell sequences within a single block. The implementation uses two complementary functions— isLocked() and lockedUntil() —to enforce temporal constraints that make same-block exploitation economically nonviable.…