[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AMJ70Q99B8YTWXKTDA8FSH":3,"skill-same:01M7AMJ70Q99B8YTWXKTDA8FSH":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},"01M7AMJ70Q99B8YTWXKTDA8FSH","blockchain-security-testing-and-ops",null,"Use when testing, auditing, securing, deploying, or operating on-chain systems. Covers the Foundry\u002FHardhat toolchain, fuzzing, invariant testing and formal verification, what to actually test, what actually loses money (access control, business logic, stolen keys) and the vulnerability canon (reentrancy, oracle manipulation, precision and rounding), security beyond the code (audits, bug bounties, incident response), deployment and verification, key management and multisigs, node and validator operations, and indexing, events, and frontend integration (viem\u002Fwagmi).","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\u002Fcryptocurrency-development\u002Fskills\u002Fblockchain-security-testing-and-ops\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: blockchain-security-testing-and-ops\ndescription: \"Use when testing, auditing, securing, deploying, or operating on-chain systems. Covers the Foundry\u002FHardhat toolchain, fuzzing, invariant testing and formal verification, what to actually test, what actually loses money (access control, business logic, stolen keys) and the vulnerability canon (reentrancy, oracle manipulation, precision and rounding), security beyond the code (audits, bug bounties, incident response), deployment and verification, key management and multisigs, node and validator operations, and indexing, events, and frontend integration (viem\u002Fwagmi).\"\n---\n\n# Blockchain Development: Testing, Security, Deployment, and Operations\n\n> **Part 3 of 4** of the *Cryptocurrency and Blockchain Development* reference (plugin `cryptocurrency-development`), covering §9–§10 and §13. Sibling skills: `blockchain-protocol-layer` (§0–§3 and §11–§12), `blockchain-smart-contract-development` (§4–§8), `blockchain-reference` (§14–§19). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Verified August 2026. See §16 → `blockchain-reference` for the currency snapshot and what goes stale first.\n\n> **How to read this.** Reference, not tutorial. Sections are independent. Three markers:\n> - **[DURABLE]** — cryptography, distributed systems, or a security lesson the industry\n>   has paid for repeatedly. Does not expire.\n> - **[VERSIONED]** — protocol state, client versions, tooling, upgrade schedules. Moving\n>   fast; verify before relying on it.\n> - **[CONTESTED]** — genuine technical or design disagreement.\n>\n> **⚠️ GOTCHA** boxes mark the mistakes that lose money irreversibly. This domain has an\n> unusually direct mapping from bug to financial loss, so those boxes carry more weight\n> here than in an ordinary engineering reference.\n>\n> **Scope note:** this is an engineering document. It covers how these systems are built\n> and how they fail. **It is not investment advice, and does not evaluate any asset as an\n> investment.**\n>\n> **The three framings that organize everything below:**\n> 1. **Deployed code is adversarial code running in public with money attached.** Every\n>    function is callable by anyone, in any order, at any time, composed with contracts\n>    that don't exist yet, by attackers who read your source and have unlimited attempts.\n>    This is a fundamentally harsher environment than ordinary software.\n> 2. **You cannot patch it.** Immutability is the point and also the problem. Upgradeability\n>    is a design decision with its own large attack surface (§6 → `blockchain-smart-contract-development`), and \"we'll fix it in the\n>    next release\" is not available to you.\n> 3. **The expensive failures are boring.** Not exotic cryptography — **access control,\n>    business logic, and stolen keys.** §10's data is unambiguous on this, and it should\n>    reorder your security priorities.\n\n---\n\n## §9. Testing\n\n### 9.1 The toolchain\n\n**[VERSIONED] The Foundry\u002FHardhat choice is no longer binary, and the 2026 answer differs\nfrom the 2022 answer.**\n\n**Foundry** — Rust-based, **tests written in Solidity**, extremely fast, with built-in\nfuzzing, invariant testing, mainnet forking, and cheatcodes (`vm.prank`, `vm.deal`,\n`vm.expectRevert`, `vm.warp`). **The default for protocol and security-sensitive work.**\n\n**Hardhat 3** — a major rewrite (new EDR engine, rebuilt config) that **added native\nSolidity tests**, multichain\u002FOP Stack simulation, and gas statistics. **This closed the two\nhistoric gaps**: reported benchmarks put Hardhat 3 **within ~2× of Foundry on equivalent\ntest suites, versus the 10–20× penalty of Hardhat 2**, and Solidity-native testing removed\nFoundry's exclusivity there.\n\n**⚠️ The practical 2026 position: they coexist.** Foundry's `foundry.toml` is parsed by\nHardhat and artifacts can be shared, so many teams use **Foundry for fast unit\u002Ffuzz\u002F\ninvariant testing of core logic and Hardhat for TypeScript integration tests, deployment\nscripts, and L2 simulation**. **Pin a shared solc version across both** to avoid\ncompiler-version drift. The genuinely wrong move is choosing Hardhat in 2026 because a 2022\ntutorial said so, then trying to retrofit Foundry-level test speed into a deeply\nHardhat-coupled codebase.\n\n### 9.2 What to actually test\n\n**[DURABLE] Unit tests are the floor, not the goal.** The techniques that find real bugs:\n\n- **Fuzzing** — random inputs against properties. `forge test` does this natively; **turn it\n  on for every function taking a numeric argument.**\n- **Invariant \u002F stateful fuzzing** — the highest-value technique available to most teams.\n  Define properties that must hold across *any sequence* of calls (\"total supply equals the\n  sum of balances,\" \"the vault is never insolvent,\" \"no user can withdraw more than they\n  deposited\"), then let the fuzzer attack them. **Echidna** and **Medusa** are the\n  specialist tools.\n- **Fork testing** — run against real mainnet state and real dependencies. Catches\n  integration assumptions that mocks hide.\n- **Formal verification** — **Certora Prover**, **Halmos**, **Kontrol**, the SMTChecker.\n  Mathematically proves properties hold under all inputs. **[VERSIONED] Increasingly a\n  standard offering from security firms rather than an exotic add-on**, and it's the gold\n  standard for high-value protocols.\n- **Static analysis** — **Slither** (run it; it's fast and catches real things),\n  **Mythril**, **Aderyn**.\n- **Differential testing** against a reference implementation.\n- **Coverage** — necessary, wildly insufficient. 100% line coverage tells you nothing about\n  whether you tested the *adversarial* path.\n\n---\n\n## §10. Security\n\n### 10.1 What actually loses money — start here\n\n**[VERSIONED, and it should reorder your priorities.]** The empirical picture from 2025–2026\nincident data is unambiguous and does not match where most developer attention goes.\n\n**By loss category** (OWASP Smart Contract Top 10 for 2026, built from 2025 incident data\nacross 149 documented incidents totalling ~$1.42B):\n```\nAccess control vulnerabilities   $953.2M   ← the overwhelming majority\nLogic errors                      $63.8M\nReentrancy                        $35.7M\nFlash loan exploits               $33.8M\n```\n**⚠️ Read that again. Access control is roughly fifteen times the loss of logic errors and\ntwenty-seven times reentrancy.** The most devastating attacks don't exploit exotic\ncryptography — **they exploit mundane permission mistakes.** Hacken's 2025 data agrees:\naccess-control exploits drove ~59% of total losses, smart-contract vulnerabilities ~8%.\n\n**And the bigger shift [VERSIONED]:** **smart contract exploit losses fell ~89%\nyear-over-year in Q1 2026** per DefiLlama — audits and architecture are working — **and it\ndidn't reduce total losses, because attackers moved to the humans.** Q1 2026 saw ~$450M lost\nacross 145 incidents, of which **phishing and social engineering accounted for ~$306M,\nnearly two-thirds**. A single January social-engineering attack drained **$282M without\ntouching a line of code.** Six audited protocols were breached in that quarter; **one had\npassed 18 prior audits.**\n\n**⚠️ The operational consequence: your security budget is probably misallocated.** Code\naudits address code vulnerabilities. They would not have prevented the largest 2026\nincidents. **Key management, operational security, insider risk, and social-engineering\nresistance now deserve first-class attention alongside the audit** — and note that\n**Chainalysis attributes roughly 76% of 2026 crypto hack losses to state-backed actors\nlinked to Lazarus Group**, whose approach includes six-month social-engineering campaigns\nand embedding operatives as IT workers. That is a different threat model than \"did we\ncheck-effects-interactions correctly.\"\n\n### 10.2 The vulnerability canon\n\n**[DURABLE] Know these cold. Most exploits are known classes hitting code that skipped\nreview, not zero-days.**\n\n| Class | Mechanism | Defense |\n|---|---|---|\n| **Broken access control** | Missing\u002Fincorrect modifier; unprotected initializer or upgrade | §6.2 → `blockchain-smart-contract-development`. **Audit every privileged path** |\n| **Reentrancy** | External call before state update; also **cross-function** and **read-only** (view function returns stale mid-transaction state) | **Checks-Effects-Interactions**; `nonReentrant`; transient storage |\n| **Oracle manipulation** | Spot price from a manipulable source | §8.2 → `blockchain-smart-contract-development` |\n| **Integer issues** | Overflow on pre-0.8 or in `unchecked`; **precision loss from division-before-multiplication**; rounding in the protocol's favour | 0.8+; order operations carefully; round deliberately |\n| **Unchecked return values** | `call`\u002F`send`\u002Fnon-standard ERC-20 silently failing | Check returns; `SafeERC20` |\n| **DoS** | Unbounded loops; a reverting recipient blocking a queue; gas griefing | Bound loops; **pull over push** |\n| **Front-running \u002F MEV** | Ordering | Slippage limits, deadlines, commit-reveal (§8.4 → `blockchain-smart-contract-development`) |\n| **Signature issues** | Replay across chains\u002Fcontracts, missing nonce, **`ecrecover` malleability**, signatures for the zero address | EIP-712 with full domain; nonces; OZ `ECDSA` |\n| **Weak randomness** | `block.timestamp`, `blockhash`, `block.prevrandao` | **On-chain randomness is not private.** Use a VRF |\n| **Delegatecall to untrusted code** | Attacker controls your storage | Never delegatecall to user input |\n| **Uninitialized proxies** | §6.1 → `blockchain-smart-contract-development` | `_disableInitializers()` |\n| **First-depositor \u002F donation** | Share-price manipulation in vaults | Virtual shares; seed the vault |\n| **Price\u002Fliquidity assumptions** | Assuming deep liquidity, or a pool that can't be drained | Model the adversarial case |\n\n### 10.3 Beyond the code\n\n**⚠️ Verify your contracts on the block explorer.** Chainalysis documented five protocols\nin six months where the **exploited contract was the protocol's own and was unverified**,\ntotalling ~$36.7M — and noted that in an era of easy decompilation, unverified code buys you\nnothing while destroying user trust and third-party review.\n\n**Bug bounties** (Immunefi is the venue) are cheap relative to an exploit. **Monitoring and\nincident response** — Forta, OpenZeppelin Defender, custom watchers — plus a **rehearsed\npause procedure**. **Timelocks** give users an exit window. And **[VERSIONED] the rise of\nAI-assisted exploit development is likely accelerating**, per Chainalysis — the attacker's\ncost of finding a bug in public bytecode is falling.\n\n**Audit reality check**: costs range from roughly $3,000 for a simple contract to $100,000+\nfor complex multi-contract systems. **⚠️ An audit is a snapshot of specific code at a\nspecific commit by fallible humans under time pressure. It is not a guarantee**, as the\nprotocol with 18 prior audits demonstrated. Get multiple audits for high value, fix\nfindings *and* their root causes, and re-audit after changes.\n\n---\n\n## §13. Deployment and Operations\n\n### 13.1 Deployment\n\n**Checklist**: audited and findings resolved · deployed to a testnet and exercised ·\n**exact compiler version pinned** · optimizer settings recorded · **deterministic build\nreproducible** · constructor arguments verified · **source verified on the explorer** (§10.3)\n· ownership transferred to a multisig\u002Ftimelock, **not an EOA** · initializers called and\nlocked · pause mechanism tested · monitoring live · **incident runbook written before\nlaunch**.\n\n**CREATE2** gives deterministic addresses across chains — useful, and note that a\ncounterfactual address can receive funds before the contract exists.\n\n### 13.2 Key management\n\n**[DURABLE] This is now a first-order security concern rather than an afterthought (§10.1).**\nHardware wallets for anything meaningful. **Multisig (Safe) for protocol control** — and\n**verify what you're signing**, since blind signing is how multisig holders get drained.\nTimelocks. Separate deploy keys from admin keys from operational keys. **Never put a\nprivate key or mnemonic in a repo, an env file that gets committed, or a CI log** — key\ncompromise produced the *largest single losses* in 2026's incident data.\n\n### 13.3 Node and validator ops\n\nClient updates on fork deadlines (§3.1 → `blockchain-protocol-layer`) — **fork weeks are when self-managed infrastructure\nhurts most**. Run a minority client (§1.3 → `blockchain-protocol-layer`). Monitor sync status, peer count, attestation\neffectiveness, and disk headroom. Test on testnets before mainnet forks. **Slashing\nprotection databases must never be lost or duplicated across machines** — running the same\nvalidator key in two places is the classic self-inflicted slashing.\n\n### 13.4 Indexing and frontends\n\n**[DURABLE] Events are your API to the off-chain world**, and under-emitting is a design\nerror you'll regret. **Indexers**: The Graph, Ponder, Subsquid, or a custom\n`eth_getLogs` + reorg-handling pipeline. **⚠️ Handle reorgs** — data you indexed can be\nun-happened, and an indexer that assumes finality too early will serve wrong data.\n\n**Frontend**: viem\u002Fwagmi (the current standard), RainbowKit or ConnectKit for wallet\nconnection, WalletConnect for mobile. **⚠️ Show users what they're signing** in human terms;\nopaque signature prompts are the substrate of the phishing losses in §10.1.\n","# Blockchain Development: Testing, Security, Deployment, and Operations\n\n> **Part 3 of 4** of the *Cryptocurrency and Blockchain Development* reference (plugin `cryptocurrency-development`), covering §9–§10 and §13. Sibling skills: `blockchain-protocol-layer` (§0–§3 and §11–§12), `blockchain-smart-contract-development` (§4–§8), `blockchain-reference` (§14–§19). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Verified August 2026. See §16 → `blockchain-reference` for the currency snapshot and what goes stale first.\n\n> **How to read this.** Reference, not tutorial. Sections are independent. Three markers:\n> - **[DURABLE]** — cryptography, distributed systems, or a security lesson the industry\n>   has paid for repeatedly. Does not expire.\n> - **[VERSIONED]** — protocol state, client versions, tooling, upgrade schedules. Moving\n>   fast; verify before relying on it.\n> - **[CONTESTED]** — genuine technical or design disagreement.\n>\n> **⚠️ GOTCHA** boxes mark the mistakes that lose money irreversibly. This domain has an\n> unusually direct mapping from bug to financial loss, so those boxes carry more weight\n> here than in an ordinary engineering reference.\n>\n> **Scope note:** this is an engineering document. It covers how these systems are built\n> and how they fail. **It is not investment advice, and does not evaluate any asset as an\n> investment.**\n>\n> **The three framings that organize everything below:**\n> 1. **Deployed code is adversarial code running in public with money attached.** Every\n>    function is callable by anyone, in any order, at any time, composed with contracts\n>    that don't exist yet, by attackers who read your source and have unlimited attempts.\n>    This is a fundamentally harsher environment than ordinary software.\n> 2. **You cannot patch it.** Immutability is the point and also the problem. Upgradeability\n>    is a design decision with its own large attack surface (§6 → `blockchain-smart-contract-development`), and \"we'll fix it in the\n>    next release\" is not available to you.\n> 3. **The expensive failures are boring.** Not exotic cryptography — **access control,\n>    business logic, and stolen keys.** §10's data is unambiguous on this, and it should\n>    reorder your security priorities.\n\n---\n\n## §9. Testing\n\n### 9.1 The toolchain\n\n**[VERSIONED] The Foundry\u002FHardhat choice is no longer binary, and the 2026 answer differs\nfrom the 2022 answer.**\n\n**Foundry** — Rust-based, **tests written in Solidity**, extremely fast, with built-in\nfuzzing, invariant testing, mainnet forking, and cheatcodes (`vm.prank`, `vm.deal`,\n`vm.expectRevert`, `vm.warp`). **The default for protocol and security-sensitive work.**\n\n**Hardhat 3** — a major rewrite (new EDR engine, rebuilt config) that **added native\nSolidity tests**, multichain\u002FOP Stack simulation, and gas statistics. **This closed the two\nhistoric gaps**: reported benchmarks put Hardhat 3 **within ~2× of Foundry on equivalent\ntest suites, versus the 10–20× penalty of Hardhat 2**, and Solidity-native testing removed\nFoundry's exclusivity there.\n\n**⚠️ The practical 2026 position: they coexist.** Foundry's `foundry.toml` is parsed by\nHardhat and artifacts can be shared, so many teams use **Foundry for fast unit\u002Ffuzz\u002F\ninvariant testing of core logic and Hardhat for TypeScript integration tests, deployment\nscripts, and L2 simulation**. **Pin a shared solc version across both** to avoid\ncompiler-version drift. The genuinely wrong move is choosing Hardhat in 2026 because a 2022\ntutorial said so, then trying to retrofit Foundry-level test speed into a deeply\nHardhat-coupled codebase.\n\n### 9.2 What to actually test\n\n**[DURABLE] Unit tests are the floor, not the goal.** The techniques that find real bugs:\n\n- **Fuzzing** — random inputs against properties. `forge test` does this natively; **turn it\n  on for every function taking a numeric argument.**\n- **Invariant \u002F stateful fuzzing** — the highest-value technique available to most teams.\n  Define properties that must hold across *any sequence* of calls (\"total supply equals the\n  sum of balances,\" \"the vault is never insolvent,\" \"no user can withdraw more than they\n  deposited\"), then let the fuzzer attack them. **Echidna** and **Medusa** are the\n  specialist tools.\n- **Fork testing** — run against real mainnet state and real dependencies. Catches\n  integration assumptions that mocks hide.\n- **Formal verification** — **Certora Prover**, **Halmos**, **Kontrol**, the SMTChecker.\n  Mathematically proves properties hold under all inputs. **[VERSIONED] Increasingly a\n  standard offering from security firms rather than an exotic add-on**, and it's the gold\n  standard for high-value protocols.\n- **Static analysis** — **Slither** (run it; it's fast and catches real things),\n  **Mythril**, **Aderyn**.\n- **Differential testing** against a reference implementation.\n- **Coverage** — necessary, wildly insufficient. 100% line coverage tells you nothing about\n  whether you tested the *adversarial* path.\n\n---\n\n## §10. Security\n\n### 10.1 What actually loses money — start here\n\n**[VERSIONED, and it should reorder your priorities.]** The empirical picture from 2025–2026\nincident data is unambiguous and does not match where most developer attention goes.\n\n**By loss category** (OWASP Smart Contract Top 10 for 2026, built from 2025 incident data\nacross 149 documented incidents totalling ~$1.42B):\n```\nAccess control vulnerabilities   $953.2M   ← the overwhelming majority\nLogic errors                      $63.8M\nReentrancy                        $35.7M\nFlash loan exploits               $33.8M\n```\n**⚠️ Read that again. Access control is roughly fifteen times the loss of logic errors and\ntwenty-seven times reentrancy.** The most devastating attacks don't exploit exotic\ncryptography — **they exploit mundane permission mistakes.** Hacken's 2025 data agrees:\naccess-control exploits drove ~59% of total losses, smart-contract vulnerabilities ~8%.\n\n**And the bigger shift [VERSIONED]:** **smart contract exploit losses fell ~89%\nyear-over-year in Q1 2026** per DefiLlama — audits and architecture are working — **and it\ndidn't reduce total losses, because attackers moved to the humans.** Q1 2026 saw ~$450M lost\nacross 145 incidents, of which **phishing and social engineering accounted for ~$306M,\nnearly two-thirds**. A single January social-engineering attack drained **$282M without\ntouching a line of code.** Six audited protocols were breached in that quarter; **one had\npassed 18 prior audits.**\n\n**⚠️ The operational consequence: your security budget is probably misallocated.** Code\naudits address code vulnerabilities. They would not have prevented the largest 2026\nincidents. **Key management, operational security, insider risk, and social-engineering\nresistance now deserve first-class attention alongside the audit** — and note that\n**Chainalysis attributes roughly 76% of 2026 crypto hack losses to state-backed actors\nlinked to Lazarus Group**, whose approach includes six-month social-engineering campaigns\nand embedding operatives as IT workers. That is a different threat model than \"did we\ncheck-effects-interactions correctly.\"\n\n### 10.2 The vulnerability canon\n\n**[DURABLE] Know these cold. Most exploits are known classes hitting code that skipped\nreview, not zero-days.**\n\n| Class | Mechanism | Defense |\n|---|---|---|\n| **Broken access control** | Missing\u002Fincorrect modifier; unprotected initializer or upgrade | §6.2 → `blockchain-smart-contract-development`. **Audit every privileged path** |\n| **Reentrancy** | External call before state update; also **cross-function** and **read-only** (view function returns stale mid-transaction state) | **Checks-Effects-Interactions**; `nonReentrant`; transient storage |\n| **Oracle manipulation** | Spot price from a manipulable source | §8.2 → `blockchain-smart-contract-development` |\n| **Integer issues** | Overflow on pre-0.8 or in `unchecked`; **precision loss from division-before-multiplication**; rounding in the protocol's favour | 0.8+; order operations carefully; round deliberately |\n| **Unchecked return values** | `call`\u002F`send`\u002Fnon-standard ERC-20 silently failing | Check returns; `SafeERC20` |\n| **DoS** | Unbounded loops; a reverting recipient blocking a queue; gas griefing | Bound loops; **pull over push** |\n| **Front-running \u002F MEV** | Ordering | Slippage limits, deadlines, commit-reveal (§8.4 → `blockchain-smart-contract-development`) |\n| **Signature issues** | Replay across chains\u002Fcontracts, missing nonce, **`ecrecover` malleability**, signatures for the zero address | EIP-712 with full domain; nonces; OZ `ECDSA` |\n| **Weak randomness** | `block.timestamp`, `blockhash`, `block.prevrandao` | **On-chain randomness is not private.** Use a VRF |\n| **Delegatecall to untrusted code** | Attacker controls your storage | Never delegatecall to user input |\n| **Uninitialized proxies** | §6.1 → `blockchain-smart-contract-development` | `_disableInitializers()` |\n| **First-depositor \u002F donation** | Share-price manipulation in vaults | Virtual shares; seed the vault |\n| **Price\u002Fliquidity assumptions** | Assuming deep liquidity, or a pool that can't be drained | Model the adversarial case |\n\n### 10.3 Beyond the code\n\n**⚠️ Verify your contracts on the block explorer.** Chainalysis documented five protocols\nin six months where the **exploited contract was the protocol's own and was unverified**,\ntotalling ~$36.7M — and noted that in an era of easy decompilation, unverified code buys you\nnothing while destroying user trust and third-party review.\n\n**Bug bounties** (Immunefi is the venue) are cheap relative to an exploit. **Monitoring and\nincident response** — Forta, OpenZeppelin Defender, custom watchers — plus a **rehearsed\npause procedure**. **Timelocks** give users an exit window. And **[VERSIONED] the rise of\nAI-assisted exploit development is likely accelerating**, per Chainalysis — the attacker's\ncost of finding a bug in public bytecode is falling.\n\n**Audit reality check**: costs range from roughly $3,000 for a simple contract to $100,000+\nfor complex multi-contract systems. **⚠️ An audit is a snapshot of specific code at a\nspecific commit by fallible humans under time pressure. It is not a guarantee**, as the\nprotocol with 18 prior audits demonstrated. Get multiple audits for high value, fix\nfindings *and* their root causes, and re-audit after changes.\n\n---\n\n## §13. Deployment and Operations\n\n### 13.1 Deployment\n\n**Checklist**: audited and findings resolved · deployed to a testnet and exercised ·\n**exact compiler version pinned** · optimizer settings recorded · **deterministic build\nreproducible** · constructor arguments verified · **source verified on the explorer** (§10.3)\n· ownership transferred to a multisig\u002Ftimelock, **not an EOA** · initializers called and\nlocked · pause mechanism tested · monitoring live · **incident runbook written before\nlaunch**.\n\n**CREATE2** gives deterministic addresses across chains — useful, and note that a\ncounterfactual address can receive funds before the contract exists.\n\n### 13.2 Key management\n\n**[DURABLE] This is now a first-order security concern rather than an afterthought (§10.1).**\nHardware wallets for anything meaningful. **Multisig (Safe) for protocol control** — and\n**verify what you're signing**, since blind signing is how multisig holders get drained.\nTimelocks. Separate deploy keys from admin keys from operational keys. **Never put a\nprivate key or mnemonic in a repo, an env file that gets committed, or a CI log** — key\ncompromise produced the *largest single losses* in 2026's incident data.\n\n### 13.3 Node and validator ops\n\nClient updates on fork deadlines (§3.1 → `blockchain-protocol-layer`) — **fork weeks are when self-managed infrastructure\nhurts most**. Run a minority client (§1.3 → `blockchain-protocol-layer`). Monitor sync status, peer count, attestation\neffectiveness, and disk headroom. Test on testnets before mainnet forks. **Slashing\nprotection databases must never be lost or duplicated across machines** — running the same\nvalidator key in two places is the classic self-inflicted slashing.\n\n### 13.4 Indexing and frontends\n\n**[DURABLE] Events are your API to the off-chain world**, and under-emitting is a design\nerror you'll regret. **Indexers**: The Graph, Ponder, Subsquid, or a custom\n`eth_getLogs` + reorg-handling pipeline. **⚠️ Handle reorgs** — data you indexed can be\nun-happened, and an indexer that assumes finality too early will serve wrong data.\n\n**Frontend**: viem\u002Fwagmi (the current standard), RainbowKit or ConnectKit for wallet\nconnection, WalletConnect for mobile. **⚠️ Show users what they're signing** in human terms;\nopaque signature prompts are the substrate of the phishing losses in §10.1.\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fcryptocurrency-development\u002Fskills\u002Fblockchain-security-testing-and-ops",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 blockchain-security-testing-and-ops",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill blockchain-security-testing-and-ops",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill blockchain-security-testing-and-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fcryptocurrency-development\u002Fskills\u002Fblockchain-security-testing-and-ops\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",[],[]]