← Laravel theorytheory 0/50 · 0%

level 1

Curious · 0 XP

streak

perfect

badges

100 XP to Apprentice

Web3 · hard

39. Verifying Blockchain Webhooks

Securely receiving on-chain event notifications.

1 min read2 questionsup to 50 XPtopic 39/50

Read in another language

AI translates the explanation and quiz text while preserving code and answer scoring.

Services like Alchemy, Moralis, or QuickNode send webhooks to Laravel routes when on-chain events occur, and these payloads must be verified (typically via an HMAC signature header) before being trusted. A dedicated controller endpoint should be excluded from CSRF verification (since it's an external POST) but still validate the signature and reject unauthorized requests early. Idempotency keys or transaction hashes should be checked to avoid processing the same webhook twice.

How to study this topic

1. Read the explanation once end to end, skipping the code.
2. Re-read the code snippets and say out loud what each line does.
3. Answer the quiz without scrolling back — that is the real check.
4. Read every explanation, even for the answers you got right.

Scoring

· Up to 30 XP from quiz accuracy.
· +15 XP for a perfect first attempt.
· +5 XP while a 3-day streak is running.
· 75% or higher marks the topic complete.

Check your understanding

1. Why must blockchain webhook payloads be signature-verified?
They're always encryptedTo ensure the request truly came from the trusted provider and wasn't forgedTo speed up the responseLaravel requires it for all POST routes
2. What should be excluded for external webhook routes but not skip signature checks?
Authentication middlewareCSRF verificationRate limiting entirelyLogging

Badges

First light

Pass your first topic

Sharp shooter

3 perfect first-try quizzes

On a roll

Study 3 days in a row

Week warrior

Study 7 days in a row

Grinder

Earn 500 XP

Deep diver

Earn 1500 XP