Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
vasilyu1983 avatar

Software Crypto Web3

  • 390 installs
  • 73 repo stars
  • Updated July 13, 2026
  • vasilyu1983/ai-agents-public

software-crypto-web3 is a Claude Code skill that guides secure blockchain development across EVM, Solana, Cosmos, and TON stacks for developers who implement smart contracts, audits, fuzz tests, and Web3 backend integrat

About

software-crypto-web3 is a vasilyu1983/ai-agents-public skill for designing and reviewing blockchain systems with security-first defaults, explicit threat models, and layered testing across unit, integration, fork, and fuzz or invariant suites. It maps toolchain choices such as Foundry and Hardhat for EVM Solidity, Anchor for Solana Rust programs, CosmWasm for Cosmos contracts, and Tact or FunC with Blueprint on TON, plus fuzzers like Echidna and Medusa and static analyzers including Slither and Aderyn. Coverage extends to ERC-20 and ERC-721 token standards, upgradeable proxy patterns, oracle integrations, subgraph indexing, account abstraction, L2 deployments, custody webhook validation, and backend transaction lifecycle monitoring. Developers reach for software-crypto-web3 when implementing DeFi protocols, writing audit-ready contracts, configuring Foundry fork tests, or connecting .NET or Node services to RPC providers and custodial signing flows. Triggers cover Solidity, Foundry, Anchor, CosmWasm, smart contract audits, DeFi protocols, and custodial webhook integration requests during blockchain feature work.

  • software-crypto-web3
  • AI & Agent Building
  • AI-coding skill

Software Crypto Web3 by the numbers

  • 390 all-time installs (skills.sh)
  • +13 installs in the week ending Aug 5, 2026 (Skillselion tracking)
  • Ranked #2,029 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/vasilyu1983/ai-agents-public --skill software-crypto-web3

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs390
repo stars73
Last updatedJuly 13, 2026
Repositoryvasilyu1983/ai-agents-public

How do you build secure multi-chain smart contracts?

Helps with ai & agent building tasks.

Who is it for?

Developers building EVM, Solana, Cosmos, or TON applications who need audit-oriented smart contract patterns, fuzz testing, and production Web3 integration guidance.

Skip if: Developers working on centralized web apps without on-chain components who do not need wallet, RPC, or smart contract tooling.

When should I use this skill?

The user asks about Solidity, Foundry, Anchor, CosmWasm, smart contract audits, DeFi protocols, or Web3 backend RPC and custody integration.

What you get

Threat-modeled contract code, Foundry or Hardhat test suites, fuzz configs, deployment scripts, and Web3 backend integration patterns.

  • smart contract source
  • test and fuzz configs
  • deployment and verification scripts

By the numbers

  • Covers 4 blockchain ecosystems: EVM, Solana, Cosmos, and TON
  • Documents Foundry, Hardhat, Echidna, and Medusa in testing workflows
  • Includes ERC-20, ERC-721, ERC-1155, and SPL token standard patterns

Files

SKILL.mdMarkdownGitHub ↗

Software Crypto/Web3 Engineering

Use this skill to design, implement, and review secure blockchain systems: smart contracts, on-chain/off-chain integration, custody and signing, testing, audits, and production operations.

Defaults to: security-first development, explicit threat models, comprehensive testing (unit + integration + fork + fuzz/invariants), formal methods when high-value, upgrade safety (timelocks, governance, rollback plans), and defense-in-depth for key custody and signing.

---

Quick Reference

TaskTool/FrameworkCommandWhen to Use
Solidity DevelopmentHardhat/Foundrynpx hardhat init or forge initEthereum/EVM smart contracts
Solana ProgramsAnchoranchor initSolana blockchain development
Cosmos ContractsCosmWasmcargo generate --git cosmwasm-templateCosmos ecosystem contracts
TON ContractsTact/FunC + Blueprintnpm create ton@latestTON blockchain development
Testing (Solidity)Foundry/Hardhatforge test or npx hardhat testUnit, fork, invariant tests
Security AuditSlither/Aderyn/Echidnaslither . or aderyn .Static analysis, fuzzing
AI-Assisted ReviewAI scanners (optional)N/APre-audit preparation (verify findings manually)
FuzzingEchidna/Medusaechidna . or medusa fuzzProperty-based fuzzing
Gas OptimizationFoundry Gas Snapshotsforge snapshotBenchmark and optimize gas
DeploymentHardhat Deploy/Forge Scriptnpx hardhat deployMainnet/testnet deployment
VerificationEtherscan APInpx hardhat verifySource code verification
Upgradeable ContractsOpenZeppelin Upgrades@openzeppelin/hardhat-upgradesProxy-based upgrades
Smart WalletsERC-4337, EIP-7702Account abstraction SDKsSmart accounts and sponsored gas (verify network support)

Scope

Use this skill when you need:

  • Smart contract development (Solidity, Rust, CosmWasm)
  • DeFi protocol implementation (AMM, lending, staking, yield farming)
  • NFT and token standards (ERC20, ERC721, ERC1155, SPL tokens)
  • DAO governance systems
  • Cross-chain bridges and interoperability
  • Gas optimization and storage patterns
  • Smart contract security audits
  • Testing strategies (Foundry, Hardhat, Anchor)
  • Oracle integration (Chainlink, Pyth)
  • Upgradeable contract patterns (proxies, diamonds)
  • Web3 frontend integration (ethers.js, web3.js, @solana/web3.js)
  • Blockchain indexing (The Graph, subgraphs)
  • MEV protection and flashbots
  • Layer 2 scaling solutions (Base, Arbitrum, Optimism, zkSync)
  • Account abstraction (ERC-4337, EIP-7702, smart wallets)
  • Backend crypto integration (.NET/C#, multi-provider architecture, CQRS)
  • Webhook handling and signature validation (Fireblocks, custodial providers)
  • Event-driven architecture with Kafka for crypto payments
  • Transaction lifecycle management and monitoring
  • Wallet management (custodial vs non-custodial)

Decision Tree: Blockchain Platform Selection

Project needs: [Use Case]
  - EVM-compatible smart contracts?
    - Complex testing needs -> Foundry (fuzzing, invariants, gas snapshots)
    - TypeScript ecosystem -> Hardhat (plugins, TS, Ethers.js/Viem)
    - Enterprise features -> NestJS + Hardhat

  - High throughput / low fees?
    - Rust-based -> Solana (Anchor)
    - EVM L2 -> Arbitrum/Optimism/Base (Ethereum security, lower gas)
    - Telegram distribution -> TON (Tact/FunC)

  - Interoperability across chains?
    - Cosmos ecosystem -> CosmWasm (IBC)
    - Multi-chain apps -> LayerZero or Wormhole (verify trust assumptions)
    - Bridge development -> custom (high risk; threat model required)

  - Token standard implementation?
    - Fungible tokens -> ERC20 (OpenZeppelin), SPL Token (Solana)
    - NFTs -> ERC721/ERC1155 (OpenZeppelin), Metaplex (Solana)
    - Semi-fungible -> ERC1155 (gaming, fractionalized NFTs)

  - DeFi protocol development?
    - AMM/DEX -> Uniswap V3 fork or custom (concentrated liquidity)
    - Lending -> Compound/Aave fork (collateralized borrowing)
    - Staking/yield -> custom reward distribution contracts

  - Upgradeable contracts required?
    - Transparent proxy -> OpenZeppelin (admin/user separation)
    - UUPS -> upgrade logic in implementation
    - Diamond -> modular functionality (EIP-2535)

  - Backend integration?
    - .NET/C# -> multi-provider architecture (see backend integration references)
    - Node.js -> Ethers.js/Viem + durable queues
    - Python -> Web3.py + FastAPI

Chain-Specific Considerations:

  • Ethereum/EVM: Security-first, higher gas costs, largest ecosystem
  • Solana: Performance-first, Rust required, lower fees
  • Cosmos: Interoperability-first, IBC native, growing ecosystem
  • TON: Telegram-first, async contracts, unique architecture

See references/ for chain-specific best practices.

---

Security-First Patterns (Jan 2026)

Security baseline: Assume an adversarial environment. Treat contracts and signing infrastructure as public, attackable APIs.

Custody, Keys, and Signing (Core)

Key management is a dominant risk driver in production crypto systems. Use a real key management standard as baseline (for example, NIST SP 800-57).

ModelWho holds keysTypical usePrimary risksDefault controls
Non-custodialEnd user walletConsumer apps, self-custodyPhishing, approvals, UX errorsHardware wallet support, clear signing UX, allowlists
CustodialYour service (HSM/MPC)Exchanges, payments, B2BKey theft, insider threat, ops mistakesHSM/MPC, separation of duties, limits/approvals, audit logs
HybridSplit responsibilityEnterprisesComplex failure modesExplicit recovery/override paths, runbooks

BEST:

  • Separate hot/warm/cold signing paths with limits and approvals [Inference]
  • Require dual control for high-value transfers (policy engine + human approval) [Inference]
  • Keep an immutable audit trail for signing requests (who/what/when/why) [Inference]

AVOID:

  • Storing private keys in databases or application config
  • Reusing signing keys across environments (dev/staging/prod)
  • Hot-wallet automation without rate limits and circuit breakers [Inference]

Checks-Effects-Interactions (CEI) Pattern

Mandatory for all state-changing functions.

// Correct: CEI pattern
function withdraw(uint256 amount) external {
    // 1. CHECKS: Validate conditions
    require(balances[msg.sender] >= amount, "Insufficient balance");

    // 2. EFFECTS: Update state BEFORE external calls
    balances[msg.sender] -= amount;

    // 3. INTERACTIONS: External calls LAST
    (bool success, ) = msg.sender.call{value: amount}("");
    require(success, "Transfer failed");
}

// Wrong: External call before state update (reentrancy risk)
function withdrawUnsafe(uint256 amount) external {
    require(balances[msg.sender] >= amount);
    (bool success, ) = msg.sender.call{value: amount}("");
    require(success);
    balances[msg.sender] -= amount; // Too late!
}

Security Tools (Jan 2026)

CategoryToolPurposeWhen to Use
Static AnalysisSlitherVulnerability detection, 92+ detectorsEvery contract
Static AnalysisAderynRust-based, faster for large codebasesLarge projects
FuzzingEchidnaProperty-based fuzzingComplex state
FuzzingMedusaParallelized Go fuzzerCI/CD pipelines
Formal VerificationSMTCheckerBuilt-in Solidity checkerEvery contract
Formal VerificationCertoraProperty-based proofs (CVL)DeFi, high-value
Formal VerificationHalmosSymbolic testingComplex invariants
AI-AssistedSherlock AIML vulnerability detectionPre-audit prep
AI-AssistedOlympixDevSecOps integrationCI/CD security
AI-AssistedAuditBase423+ detectors, LLM-poweredBusiness logic
Mutation TestingSuMoTest suite quality assessmentTest validation
// Certora CVL rule example
rule balanceNeverNegative(address user) {
    env e;
    require balances[user] >= 0;
    deposit(e);
    assert balances[user] >= 0;
}
AI-assisted review: Use AI tooling for pre-audit preparation and coverage, not for final security decisions. Treat outputs as untrusted and reproduce findings with deterministic tools, tests, and manual review.

MEV Protection

StrategyImplementation
Private mempoolFlashbots Protect, MEV Blocker
Commit-revealHash commitment, reveal after deadline
Batch auctionsCoW Protocol, Gnosis Protocol
Encrypted mempoolsShutter Network
// Commit-reveal pattern
mapping(address => bytes32) public commitments;

function commit(bytes32 hash) external {
    commitments[msg.sender] = hash;
}

function reveal(uint256 value, bytes32 salt) external {
    require(
        keccak256(abi.encodePacked(value, salt)) == commitments[msg.sender],
        "Invalid reveal"
    );
    // Process revealed value
}

---

Account Abstraction (Jan 2026)

Note: Adoption numbers and upgrade timelines change quickly. Verify current ERC-4337 ecosystem state and any EIP-7702 activation details with WebSearch before making recommendations.

ERC-4337 vs EIP-7702

StandardTypeKey FeatureUse Case
ERC-4337Smart contract walletsFull AA without protocol changesNew wallets, DeFi, gaming
EIP-7702EOA enhancementEOAs execute smart contract codeExisting wallets, batch txns
ERC-6900Modular accountsPlugin management for AA walletsExtensible wallet features

ERC-4337 Architecture:

User -> UserOperation -> Bundler -> EntryPoint -> Smart Account -> Target Contract
                          |
                          v
                      Paymaster (gas sponsorship)

EIP-7702 (Pectra Upgrade):

  • EOAs can temporarily delegate to smart contracts
  • Enables batch transactions, sponsored gas for existing addresses
  • Complementary to ERC-4337 (uses same bundler/paymaster infra)
  • Supported by Ambire, Trust Wallet, and growing

Key Capabilities:

  • Gasless transactions: Paymasters sponsor gas in ERC-20 or fiat
  • Batch operations: Multiple actions in single transaction
  • Social recovery: Multi-sig or guardian-based key recovery
  • Session keys: Limited permissions for dApps without full wallet access

Smart Wallet Development

// Minimal ERC-4337 Account (simplified)
import "@account-abstraction/contracts/core/BaseAccount.sol";

contract SimpleAccount is BaseAccount {
    address public owner;

    function validateUserOp(
        UserOperation calldata userOp,
        bytes32 userOpHash,
        uint256 missingAccountFunds
    ) external override returns (uint256 validationData) {
        // Verify signature
        require(_validateSignature(userOp, userOpHash), "Invalid sig");
        // Pay prefund if needed
        if (missingAccountFunds > 0) {
            (bool success,) = payable(msg.sender).call{value: missingAccountFunds}("");
            require(success);
        }
        return 0; // Valid
    }
}

---

Layer 2 Development (Jan 2026)

Note: L2 market share and risk stages change quickly. Use current data (for example, L2Beat and ecosystem dashboards) before stating rankings, TVL, or stage classifications.

L2 Selection Guide

L2TypeBest ForKey Feature
BaseOptimisticConsumer apps, mainstream adoptionCoinbase integration, low fees
ArbitrumOptimisticDeFi, mature ecosystemLargest TVL, DAO grants
OptimismOptimisticPublic goods, SuperchainOP Stack, grant programs
zkSync EraZK-RollupFast finality, native AAzkEVM, no withdrawal delay
StarkNetZK-RollupCairo development, ZK-nativeSTARK proofs, custom VM

Enterprise Rollups (2025-2026 Trend)

Major institutions launching L2s on OP Stack:

  • Kraken INK - Exchange-native L2
  • Uniswap UniChain - DeFi-optimized
  • Sony Soneium - Gaming and media
  • Robinhood - Arbitrum integration

EIP-4844 Blob Optimization

Since March 2024, rollups use blob-based data posting:

Before: calldata posting -> expensive
After:  blob posting -> lower data availability cost

Optimism, zkSync optimized batching for blobs in 2025.

---

Common Mistakes (2025-2026)

Reality check: Exploits regularly cause large losses. Access control, signing/custody, and integration bugs remain top incident drivers.
MistakeImpactPrevention
Missing access controlUnauthorized admin actionsUse OpenZeppelin Ownable2Step, AccessControl
ReentrancyDrain funds via callbackCEI pattern, ReentrancyGuard, Slither checks
Unchecked external callsSilent failuresAlways check return values, use SafeERC20
Integer overflow (pre-0.8)Arbitrary value manipulationUse Solidity 0.8.x+ (built-in checks)
FrontrunningMEV extraction, sandwich attacksCommit-reveal, Flashbots Protect, private mempool
Oracle manipulationPrice feed attacksTWAP, multiple oracles, sanity bounds
Improper initializationProxy takeoverUse initializer modifier, _disableInitializers()
Storage collision (proxies)Data corruptionFollow EIP-1967 slots, use OpenZeppelin upgrades

Anti-Patterns to Avoid

AVOID:

  • Using tx.origin for authorization (phishing risk)
  • Storing secrets on-chain (all data is public)
  • Using block.timestamp for randomness (miner/validator influence)
  • Ignoring return values from transfer/send
  • Using deprecated tooling (Truffle/Ganache/Brownie)

BEST:

  • Run static analysis on every change (for example, Slither and Aderyn)
  • Add fuzz/invariant tests before any audit
  • Use formal methods for high-value DeFi (for example, Certora and symbolic testing)

---

LLM Limitations in Smart Contracts

Do not rely on LLMs for:

  • Security-critical logic verification
  • Gas optimization calculations
  • Complex mathematical proofs

Use LLMs for:

  • Boilerplate generation (tests, docs)
  • Code explanation and review prep
  • Initial vulnerability hypotheses (verify manually)

---

When NOT to Use This Skill

  • Traditional backend without blockchain -> Use software-backend
  • Pure API design without Web3 -> Use dev-api-design
  • General security without smart contracts -> Use software-security-appsec
  • Frontend-only dApp UI -> Use software-frontend + Web3 libraries

---

Navigation

Resources

  • references/blockchain-best-practices.md - Universal blockchain patterns and security
  • references/backend-integration-best-practices.md - .NET/C# crypto integration patterns (CQRS, Kafka, multi-provider)
  • references/solidity-best-practices.md - Solidity/EVM-specific guidance
  • references/rust-solana-best-practices.md - Solana + Anchor patterns
  • references/cosmwasm-best-practices.md - Cosmos/CosmWasm guidance
  • references/ton-best-practices.md - TON contracts (Tact/Fift/FunC) and deployment
  • references/defi-protocol-patterns.md - AMM, lending, staking, yield farming, flash loans, oracle integration
  • references/nft-token-standards.md - ERC-20/721/1155, SPL Token, Metaplex, token gating, metadata
  • references/cross-chain-bridges.md - Bridge architectures, LayerZero, Wormhole, IBC, security analysis
  • ../software-security-appsec/references/smart-contract-security-auditing.md - Smart contract audit workflows and tools (see software-security-appsec skill)
  • data/sources.json - Curated external references per chain
  • Shared secure review checklist: ../software-clean-code-standard/assets/checklists/secure-code-review-checklist.md

Templates

  • Ethereum/EVM: assets/ethereum/template-solidity-hardhat.md, assets/ethereum/template-solidity-foundry.md
  • Solana: assets/solana/template-rust-anchor.md
  • Cosmos: assets/cosmos/template-cosmwasm.md
  • TON: assets/ton/template-tact-blueprint.md, assets/ton/template-func-blueprint.md
  • Bitcoin: assets/bitcoin/template-bitcoin-core.md

Related Skills

  • ../software-security-appsec/SKILL.md - Security hardening, threat modeling, OWASP vulnerabilities
  • ../software-architecture-design/SKILL.md - System decomposition, modularity, dependency design
  • ../ops-devops-platform/SKILL.md - Infrastructure, CI/CD, observability for blockchain nodes
  • ../software-backend/SKILL.md - API integration with smart contracts, RPC nodes, indexers
  • ../qa-resilience/SKILL.md - Resilience, circuit breakers, retry logic for chains
  • ../software-code-review/SKILL.md - Code review patterns and quality gates
  • ../dev-api-design/SKILL.md - RESTful design for Web3 APIs and dApp backends

---

Trend Awareness Protocol

IMPORTANT: When users ask recommendation questions about Web3/crypto development, you MUST use WebSearch to check current trends before answering.

Trigger Conditions

  • "What's the best blockchain for [use case]?"
  • "What should I use for [smart contracts/DeFi/NFTs]?"
  • "What's the latest in Web3 development?"
  • "Current best practices for [Solidity/auditing/gas optimization]?"
  • "Is [chain/protocol] still relevant in 2026?"
  • "[Ethereum] vs [Solana] vs [other L1/L2]?"
  • "Best framework for [smart contract development]?"

Required Searches

1. Search: "Web3 development best practices 2026" 2. Search: "[Ethereum/Solana/Base] development updates 2026" 3. Search: "smart contract security 2026" 4. Search: "[Hardhat/Foundry] comparison 2026"

What to Report

After searching, provide:

  • Current landscape: What chains/tools are popular NOW
  • Emerging trends: New protocols or patterns gaining traction
  • Deprecated/declining: Chains or approaches losing relevance
  • Recommendation: Based on fresh data and ecosystem activity

Example Topics (verify with fresh search)

  • L2 ecosystem growth (Base, Arbitrum, Optimism)
  • Solidity vs Rust for smart contracts
  • Foundry vs Hardhat tooling
  • Account abstraction (ERC-4337) adoption
  • Cross-chain bridges and interoperability
  • DeFi security patterns and audit practices

---

Operational Playbooks

  • references/operational-playbook.md - Smart contract architecture, security-first workflows, and platform-specific patterns

Fact-Checking

  • Use web search/web fetch to verify current external facts, versions, pricing, deadlines, regulations, or platform behavior before final answers.
  • Prefer primary sources; report source links and dates for volatile information.
  • If web access is unavailable, state the limitation and mark guidance as unverified.

Related skills

How it compares

Choose software-crypto-web3 for multi-chain contract and backend integration guidance rather than generic backend API skills without on-chain security patterns.

FAQ

Which blockchains does software-crypto-web3 cover?

software-crypto-web3 spans EVM chains with Solidity, Solana with Anchor and Rust, Cosmos with CosmWasm, and TON with Tact or FunC plus Blueprint tooling for contract development and review.

What testing tools does software-crypto-web3 recommend?

software-crypto-web3 lists Foundry and Hardhat for EVM suites, Anchor tests for Solana, and Echidna or Medusa property fuzzing alongside static analyzers like Slither and Aderyn for pre-audit checks.

Does software-crypto-web3 include backend integration guidance?

software-crypto-web3 covers RPC providers, subgraph indexing, custodial webhook signature validation, Kafka-style event flows, and transaction lifecycle monitoring for production Web3 backends.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.