A Readude bookPrivate review · sales off

Modern Cryptography,
taken seriously.

Move from calling cryptographic APIs to defining adversaries, reading security claims, tracing protocol assumptions, and recognizing where real implementations fail.

Free sample downloads are not published in this preview Waitlist opens after launch setup
Private review candidate v0.8.4 — public sales are intentionally disabled.
32 chapters
one learning arc
Draft cover for Modern Cryptography: A Deep Self-Study Guide, published by Readude
Serious ideas. Better reads. No shelf required. Read deep. Stay curious. Serious ideas. Better reads.
32connected chapters
7technical appendices
24tested Python examples
24 weekscomplete study path
Learning outcomes

Understand what the guarantee actually says.

The book joins mathematical definitions to protocol and engineering boundaries instead of treating cryptographic primitives as isolated names.

01 / MODEL

Define the adversary

Turn “encrypt this” into assets, trust boundaries, oracle access, winning events, and failure consequences.

threat models
02 / REASON

Read the claim

Work with indistinguishability, unforgeability, hybrid arguments, reductions, concrete loss, setup assumptions, and composition.

security games
03 / AUDIT

Find the boundary failure

Inspect nonce state, framing, canonicalization, replay, domain separation, parser ambiguity, key lifecycle, side channels, and migration.

engineering
Curriculum

From cryptanalysis to post-quantum migration.

Each part supplies prerequisites for the next. Follow the full route or use the accelerated and zero-knowledge-focused paths.

I

Adversarial thinking

Threat models, security properties, Kryptos as a verification case study, and the classical cryptanalysis workbench.

II

Mathematical and formal language

Modular arithmetic, groups, fields, probability, entropy, birthday bounds, security games, and reductions.

III

Symmetric and public-key systems

AES, ChaCha20, AEAD, hashes, MACs, KDFs, RSA, Diffie–Hellman, ECC, and signatures.

IV

Protocols and key governance

HPKE, PKI, TLS 1.3, X3DH, Double Ratchet, HSM/KMS, sharing, and threshold signatures.

V

Zero knowledge

Commitments, Sigma protocols, R1CS, sumcheck, KZG, IPA, FRI, SNARKs, STARKs, recursion, and zkVMs.

VI

Deployment and transition

Wallet security, incident analysis, cryptographic engineering, agility, and post-quantum migration.

readude note
Transparent Early Access

A review candidate—not an invented badge of authority.

The manuscript was developed and translated with AI-assisted tools. The author is responsible for selection, organization, verification, editing, and release. Automated structure tests and passing educational examples do not constitute peer review, a cryptographic audit, or production approval.

Status: PRIVATE REVIEW · SALES DISABLED

Planned Early Access

One product. One clear price.

The founding price is planned at US$9.99. After 14 days from the actual public launch, the same product moves to US$14.99. Nothing on this private-review site is a public offer.

FAQ

What this release is—and is not.

Is this a beginner book?

It rebuilds prerequisites, but it aims beyond introductory API usage. High-school algebra and basic Python are helpful; the complete route is comparable to a demanding university self-study sequence.

Is the code production-ready?

No. Examples are educational. Some intentionally expose failure modes or use toy parameters. Real systems require reviewed libraries, deployment profiles, key management, test vectors, and independent security review.

Was AI used?

Yes. AI-assisted tools contributed to drafting, organization, and English translation. Human editing, primary-source checks, and beta issue triage are tracked. Claims of fully human translation, peer review, or audit are prohibited.

What is Readude?

Readude is Kyle Wu's independent digital publishing brand for serious ideas across technical and non-technical fields. The selected primary domain is readude.com; public operation begins only after domain registration and release setup are complete.

Why are sales disabled?

This is a deployable private-review build. Domain control, live support, checkout approval, the invited beta, zero known Critical issues, and purchase/delivery QA must pass before payment is enabled.