Zealynx AcademyZealynx Academy
← All free courses

Audit practice · Free study companion

Spot the Bug: Solidity Security Challenges

Ten pause-before-the-reveal Solidity challenges. Identify the broken invariant, explain the impact and propose a fix with a regression test.

12 Whop lessons · 3 study checkpoints · 10 matching quizzes

Watch the course on Whop ↗
Watch → recall → apply. Use these checkpoints alongside the course. Read the recap, answer the matching quizzes, then attempt the practical task before checking its criteria. Quizzes may appear in more than one course because the same concept applies in different settings. Video links open the original public YouTube lessons; Whop requires its own free sign-in.

Checkpoint 1

Identity, state and time

Check what a guard actually establishes. A nonzero address is not proof of the correct contract or interface. An external call can move control before your state is safe, a Merkle claim needs the right binding and consumption rules, and time comparisons need tests at the boundary.

Watch the matching lessons (4)

Check your understanding

Practical challenge

Choose one identity or state challenge and write a minimal counterexample.

Check your work

  • Name a reachable precondition.
  • Test the fix at and immediately around the boundary.

Checkpoint 2

Prices, shares and arithmetic

Arithmetic and economic assumptions interact. Spot prices may be manipulable, feeds may be stale, donations can distort share accounting and integer division can erase a small entitlement. State the asset and share invariant, then test small values and adversarial transaction order instead of only typical deposits.

Watch the matching lessons (4)

Check your understanding

Practical challenge

Create a toy share or rounding example with small integer values.

Check your work

  • Show the expected and actual entitlement.
  • Include a donation, stale input or reordered operation where relevant.

Checkpoint 3

Replay and governance

Valid authorization is not the same as safe reuse. A bridge message needs appropriate identity and one-time consumption, and a governance check must consider how voting power is obtained. Explain the attacker’s reachable sequence, then propose a regression that rejects it without blocking intended behavior.

Watch the matching lessons (2)

Check your understanding

Practical challenge

Describe a replay or borrowed-vote sequence and a regression.

Check your work

  • Specify the message identity or voting-power assumption.
  • Check legitimate one-time use still succeeds.

Explain the decision, not just the answer.

After each checkpoint, write one assumption you changed and one test you would add. Bring a sanitized example or a specific question to the free Academy community.

Find your way around the community →