[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AMJPXD2TM1XZRX53CTBKBQ":3,"skill-same:01M7AMJPXD2TM1XZRX53CTBKBQ":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7AMJPXD2TM1XZRX53CTBKBQ","crypto-advanced-constructions-blockchain-and-policy",null,"Use for the frontier and the context around it: advanced constructions including zero-knowledge proofs, multiparty computation, homomorphic encryption and threshold schemes with honest notes on their maturity, the cryptography specific to blockchains, and the law and policy layer of export control, lawful access debates and compliance obligations.","the-vibey-project\u002Fvibey","the-vibey-project","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F329298758?v=4","01M7AJHGZ9722CTJ4JNQZVRH0Q","the vibey project","01M7AJHGZVMG2K7TGXQ6XFHVG3",5,"MIT","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fcryptography-and-encryption\u002Fskills\u002Fcrypto-advanced-constructions-blockchain-and-policy\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: crypto-advanced-constructions-blockchain-and-policy\ndescription: \"Use for the frontier and the context around it: advanced constructions including zero-knowledge proofs, multiparty computation, homomorphic encryption and threshold schemes with honest notes on their maturity, the cryptography specific to blockchains, and the law and policy layer of export control, lawful access debates and compliance obligations.\"\n---\n\n# Cryptography: Advanced Constructions, Blockchain Cryptography, and Law and Policy\n\n> **Part 5 of 6** of the *Cryptography and Encryption* reference (plugin `cryptography-and-encryption`), covering §20–§22. Sibling skills: `crypto-what-it-solves-threat-models-randomness-hashes-and-macs` (§0–§5), `crypto-symmetric-aead-public-key-and-signatures` (§6–§10), `crypto-passwords-tls-pki-messaging-and-disk-encryption` (§11–§16), `crypto-implementation-failures-key-management-and-agility` (§17–§19), `crypto-reference` (§23–§28). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** The primitives are stable. Two migrations are actively underway. See §23 → `crypto-reference` for post-quantum cryptography, and TLS certificate lifetimes.\n\n> **⚠️ Cryptography is the part of security that mostly WORKS. The primitives are rarely\n> broken; the systems built from them fail constantly** (§17 → `crypto-implementation-failures-key-management-and-agility`). ⚠️ **Almost every real-world\n> break is a key management failure, an implementation bug, a protocol composition error,\n> or a human process — not a cryptanalytic result.**\n>\n> **⚠️ THE RULE THAT MATTERS MOST: don't build it yourself.** ⚠️ **Use a vetted,\n> well-maintained library at the highest level of abstraction that solves your problem.\n> This document is for UNDERSTANDING what those libraries do and evaluating designs —\n> not a recipe for implementing primitives.**\n>\n> **Complements an electromagnetism reference (the physical layer), and security-focused\n> material on threat modelling and application security.**\n>\n> **⚠️ GOTCHA** boxes mark the failure modes that have caused real breaches.\n>\n> **The three ideas that organize this document:**\n> 1. **⚠️ ENCRYPTION WITHOUT AUTHENTICATION IS BROKEN** (§7 → `crypto-symmetric-aead-public-key-and-signatures`). **Confidentiality alone is\n>    almost never what you want, and unauthenticated ciphertext is malleable. Use AEAD.**\n> 2. **⚠️ KEY MANAGEMENT IS THE HARD PART** (§18 → `crypto-implementation-failures-key-management-and-agility`). **The algorithm choice is usually easy\n>    and usually not where you lose. Where keys live, who can reach them, and how they\n>    rotate is where systems actually fail.**\n> 3. **⚠️ AGILITY IS A DESIGN REQUIREMENT** (§19 → `crypto-implementation-failures-key-management-and-agility`, §23 → `crypto-reference`). **Every algorithm eventually\n>    weakens. Systems that hardcoded their primitives are the ones in pain right now.**\n\n---\n\n## §20. Advanced Constructions\n\n**⚠️ Real, deployed, and frequently oversold — worth knowing what each actually gives you.**\n**⚠️ ZERO-KNOWLEDGE PROOFS**: ⚠️ **prove a statement is true without revealing why.**\n**zk-SNARKs (⚠️ succinct, often needing a trusted setup) and zk-STARKs (⚠️ no trusted setup,\nlarger proofs).** **Genuine uses in privacy and verifiable computation.**\n**⚠️ MULTI-PARTY COMPUTATION**: ⚠️ **jointly compute a function over private inputs;\npractical for specific problems (private set intersection, threshold operations) and still\nexpensive for general computation.**\n**⚠️ HOMOMORPHIC ENCRYPTION**: ⚠️ **compute on ciphertext.** ⚠️ **Partially homomorphic\nschemes are practical; FULLY homomorphic encryption is real, improving, and still orders of\nmagnitude slower than plaintext computation.** **⚠️ Treat \"we use FHE\" claims sceptically\nand ask about the performance envelope.**\n**⚠️ THRESHOLD AND SECRET SHARING**: ⚠️ **Shamir's scheme splits a secret so that k of n\nshares reconstruct it — genuinely useful for root key custody.** ⚠️ **Threshold signatures\navoid ever reconstructing the key at all.**\n**⚠️ Differential privacy** — ⚠️ **not cryptography, but frequently deployed alongside it;\nit bounds what can be learned about any individual from aggregate release.**\n\n---\n\n## §21. Blockchain Cryptography\n\n**⚠️ What it actually uses**: ⚠️ **hash functions for linking and proof-of-work, Merkle\ntrees for efficient inclusion proofs, ECDSA or Schnorr signatures for transaction\nauthorization.** **⚠️ The cryptography is standard; the novelty is the consensus mechanism\nand the incentive design, not the primitives.**\n**⚠️ Merkle trees** are independently useful — ⚠️ **certificate transparency (§13 → `crypto-passwords-tls-pki-messaging-and-disk-encryption`), git,\nand file integrity systems all use them.**\n> **⚠️ GOTCHA — \"blockchain\" is not a cryptographic property.** ⚠️ **It does not make data\n> true, only tamper-evident once recorded, and it says nothing about whether the input was\n> correct.** **⚠️ And \"your keys, your coins\" means key management (§18 → `crypto-implementation-failures-key-management-and-agility`) with no recovery\n> path — which has resulted in permanent, irreversible loss at large scale.**\n\n---\n\n## §22. Law and Policy\n\n**⚠️ Export controls**: ⚠️ **historically severe (the \"crypto wars\"), substantially\nliberalized, and still present in some jurisdictions and for some categories.**\n**⚠️ Lawful access and \"exceptional access\"** is a genuinely contested policy question\nwhere I'd rather set out the positions than pick one:\n⚠️ **the law enforcement argument is that end-to-end encryption creates spaces where lawful\nwarrants cannot reach, with real consequences for serious crime investigation.**\n⚠️ **The technical community's near-consensus counter-argument is that any mechanism\npermitting third-party access constitutes a deliberate vulnerability that cannot be limited\nto authorized users, that key escrow at scale creates an extraordinarily valuable target,\nand that the software is globally available regardless of any one country's rules.**\n⚠️ **Client-side scanning has been proposed as a middle path and criticized on the grounds\nthat it relocates rather than resolves the trust problem.**\n**⚠️ Also relevant**: ⚠️ **compelled key disclosure laws vary sharply by jurisdiction, data\nprotection regimes increasingly treat encryption as an expected safeguard, and\njurisdiction-specific rules can require specific algorithms.**\n","# Cryptography: Advanced Constructions, Blockchain Cryptography, and Law and Policy\n\n> **Part 5 of 6** of the *Cryptography and Encryption* reference (plugin `cryptography-and-encryption`), covering §20–§22. Sibling skills: `crypto-what-it-solves-threat-models-randomness-hashes-and-macs` (§0–§5), `crypto-symmetric-aead-public-key-and-signatures` (§6–§10), `crypto-passwords-tls-pki-messaging-and-disk-encryption` (§11–§16), `crypto-implementation-failures-key-management-and-agility` (§17–§19), `crypto-reference` (§23–§28). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** The primitives are stable. Two migrations are actively underway. See §23 → `crypto-reference` for post-quantum cryptography, and TLS certificate lifetimes.\n\n> **⚠️ Cryptography is the part of security that mostly WORKS. The primitives are rarely\n> broken; the systems built from them fail constantly** (§17 → `crypto-implementation-failures-key-management-and-agility`). ⚠️ **Almost every real-world\n> break is a key management failure, an implementation bug, a protocol composition error,\n> or a human process — not a cryptanalytic result.**\n>\n> **⚠️ THE RULE THAT MATTERS MOST: don't build it yourself.** ⚠️ **Use a vetted,\n> well-maintained library at the highest level of abstraction that solves your problem.\n> This document is for UNDERSTANDING what those libraries do and evaluating designs —\n> not a recipe for implementing primitives.**\n>\n> **Complements an electromagnetism reference (the physical layer), and security-focused\n> material on threat modelling and application security.**\n>\n> **⚠️ GOTCHA** boxes mark the failure modes that have caused real breaches.\n>\n> **The three ideas that organize this document:**\n> 1. **⚠️ ENCRYPTION WITHOUT AUTHENTICATION IS BROKEN** (§7 → `crypto-symmetric-aead-public-key-and-signatures`). **Confidentiality alone is\n>    almost never what you want, and unauthenticated ciphertext is malleable. Use AEAD.**\n> 2. **⚠️ KEY MANAGEMENT IS THE HARD PART** (§18 → `crypto-implementation-failures-key-management-and-agility`). **The algorithm choice is usually easy\n>    and usually not where you lose. Where keys live, who can reach them, and how they\n>    rotate is where systems actually fail.**\n> 3. **⚠️ AGILITY IS A DESIGN REQUIREMENT** (§19 → `crypto-implementation-failures-key-management-and-agility`, §23 → `crypto-reference`). **Every algorithm eventually\n>    weakens. Systems that hardcoded their primitives are the ones in pain right now.**\n\n---\n\n## §20. Advanced Constructions\n\n**⚠️ Real, deployed, and frequently oversold — worth knowing what each actually gives you.**\n**⚠️ ZERO-KNOWLEDGE PROOFS**: ⚠️ **prove a statement is true without revealing why.**\n**zk-SNARKs (⚠️ succinct, often needing a trusted setup) and zk-STARKs (⚠️ no trusted setup,\nlarger proofs).** **Genuine uses in privacy and verifiable computation.**\n**⚠️ MULTI-PARTY COMPUTATION**: ⚠️ **jointly compute a function over private inputs;\npractical for specific problems (private set intersection, threshold operations) and still\nexpensive for general computation.**\n**⚠️ HOMOMORPHIC ENCRYPTION**: ⚠️ **compute on ciphertext.** ⚠️ **Partially homomorphic\nschemes are practical; FULLY homomorphic encryption is real, improving, and still orders of\nmagnitude slower than plaintext computation.** **⚠️ Treat \"we use FHE\" claims sceptically\nand ask about the performance envelope.**\n**⚠️ THRESHOLD AND SECRET SHARING**: ⚠️ **Shamir's scheme splits a secret so that k of n\nshares reconstruct it — genuinely useful for root key custody.** ⚠️ **Threshold signatures\navoid ever reconstructing the key at all.**\n**⚠️ Differential privacy** — ⚠️ **not cryptography, but frequently deployed alongside it;\nit bounds what can be learned about any individual from aggregate release.**\n\n---\n\n## §21. Blockchain Cryptography\n\n**⚠️ What it actually uses**: ⚠️ **hash functions for linking and proof-of-work, Merkle\ntrees for efficient inclusion proofs, ECDSA or Schnorr signatures for transaction\nauthorization.** **⚠️ The cryptography is standard; the novelty is the consensus mechanism\nand the incentive design, not the primitives.**\n**⚠️ Merkle trees** are independently useful — ⚠️ **certificate transparency (§13 → `crypto-passwords-tls-pki-messaging-and-disk-encryption`), git,\nand file integrity systems all use them.**\n> **⚠️ GOTCHA — \"blockchain\" is not a cryptographic property.** ⚠️ **It does not make data\n> true, only tamper-evident once recorded, and it says nothing about whether the input was\n> correct.** **⚠️ And \"your keys, your coins\" means key management (§18 → `crypto-implementation-failures-key-management-and-agility`) with no recovery\n> path — which has resulted in permanent, irreversible loss at large scale.**\n\n---\n\n## §22. Law and Policy\n\n**⚠️ Export controls**: ⚠️ **historically severe (the \"crypto wars\"), substantially\nliberalized, and still present in some jurisdictions and for some categories.**\n**⚠️ Lawful access and \"exceptional access\"** is a genuinely contested policy question\nwhere I'd rather set out the positions than pick one:\n⚠️ **the law enforcement argument is that end-to-end encryption creates spaces where lawful\nwarrants cannot reach, with real consequences for serious crime investigation.**\n⚠️ **The technical community's near-consensus counter-argument is that any mechanism\npermitting third-party access constitutes a deliberate vulnerability that cannot be limited\nto authorized users, that key escrow at scale creates an extraordinarily valuable target,\nand that the software is globally available regardless of any one country's rules.**\n⚠️ **Client-side scanning has been proposed as a middle path and criticized on the grounds\nthat it relocates rather than resolves the trust problem.**\n**⚠️ Also relevant**: ⚠️ **compelled key disclosure laws vary sharply by jurisdiction, data\nprotection regimes increasingly treat encryption as an expected safeguard, and\njurisdiction-specific rules can require specific algorithms.**\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fcryptography-and-encryption\u002Fskills\u002Fcrypto-advanced-constructions-blockchain-and-policy",3,"https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey","https:\u002F\u002Fthe-vibey-project.github.io\u002Fvibey\u002F","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project","https:\u002F\u002Fvibewithadam.matthewsteinberger.com","freedom for software engineers","2026-11-15 05:47:42",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add the-vibey-project\u002Fvibey --skill crypto-advanced-constructions-blockchain-and-policy",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill crypto-advanced-constructions-blockchain-and-policy",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill crypto-advanced-constructions-blockchain-and-policy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fcryptography-and-encryption\u002Fskills\u002Fcrypto-advanced-constructions-blockchain-and-policy\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7AT1FQJAE1FQYAMDTF490Y4","white-paper-writing","Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks \"how should I structure this\" for a long-form document.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fwhite-paper-writing\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7AT16BJRJJKK2MASXRZS76G","prose-technical-mechanics","Use when editing or writing prose at a technical\u002Fmechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-technical-mechanics\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AT0W9HT0ZZ9Y287NW99MR3","prose-mechanics","Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate\u002FJamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix \"AI-sounding\" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-mechanics\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AT0KR635JX66X2X6F3E2CP","narrative-structure","Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or \"how should I structure this story\u002Fpitch\u002Fpresentation\" request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fnarrative-structure\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AT0AKGW09NKKZDYBT8VRDE","legal-brief-writing","Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic\u002Fneurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Flegal-brief-writing\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AT00VWPS4Q8B5VEMXX9NQT","journal-publishability-criteria","Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs\u002Fpaper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fjournal-publishability-criteria\u002FSKILL.md",[],[]]