← Solana theorytheory 0/100 · 0%

level 1

Curious · 0 XP

streak

perfect

badges

100 XP to Apprentice

Native Rust · hard

24. Native Rust: Security Invariants and Account Verification

Auditing checklist for native programs.

1 min read2 questionsup to 50 XPtopic 24/100

Read in another language

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

A secure native instruction must verify: 1. Expected account count (`accounts.len()`). 2. `is_signer` for all authorities. 3. `owner == program_id` for all state accounts. 4. Correct PDA derivations with canonical bumps. 5. Checked arithmetic on all balance operations.

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 is native Rust considered more prone to vulnerabilities than Anchor?
Developers must write all security, signer, and ownership checks manually without framework enforcementNative Rust cannot use cryptographyNative Rust is slowerNative Rust does not support PDAs
2. What does the canonical bump check prevent in native PDA verification?
Bump canonicalization attacks where multiple valid bumps yield alternate addressesStack overflowExcessive compute usageAccount resizing

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