# Build Secure Blockchain Applications

Blockchain systems require careful architecture, testing, and security decisions across rapidly changing ecosystems. This skill provides structured guidance for smart contracts, Web3 applications, DeFi, and infrastructure.

## Install

```bash
npx skillstore add sickn33/blockchain-developer
```

## Metadata

- Status: approved
- Slug: sickn33-blockchain-developer
- Skillstore revision: r2
- Version status: missing
- Tree hash: 7ebf02dfad5ca65b40a92c53f31c54e8662ce4f302d171d112c0d6771a5e994e
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/blockchain-developer
- Ref: 5a26d1d61d694db29af9b138c661c1981076d9df
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-blockchain-developer
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-blockchain-developer/manifest

## Capabilities

- Designs smart contract and decentralized application architectures across EVM and alternative blockchain ecosystems.
- Guides Solidity, Rust, Vyper, and framework choices for contract development.
- Reviews designs for reentrancy, access control, oracle, bridge, and upgradeability risks.
- Plans DeFi, NFT, DAO, wallet, identity, and enterprise blockchain workflows.
- Recommends testing, formal verification, gas optimization, deployment, monitoring, and documentation practices.

## Use Cases

- Plan a Secure Smart Contract: Define contract roles, state transitions, upgrade strategy, threat model, and testing requirements before implementation.
- Design a Web3 Product: Select networks, wallets, indexing, storage, and transaction flows for a practical decentralized application.
- Assess a Protocol Design: Review DeFi mechanics, oracle dependencies, governance controls, economic risks, and operational monitoring.

## Prompt Templates

### Choose a Blockchain Stack

```
Recommend a blockchain stack for [product]. Compare network cost, security, tooling, wallet support, and scalability. State assumptions and unresolved decisions.
```

### Design a Smart Contract

```
Design a [contract type] for [network]. Define roles, functions, state transitions, events, invariants, failure cases, and a focused test plan.
```

### Review a Protocol Architecture

```
Review this [protocol description]. Identify trust assumptions, attack surfaces, oracle risks, governance risks, upgrade hazards, and mitigations. Prioritize findings by impact.
```

### Plan a Multi-Chain Deployment

```
Create a deployment strategy for [application] across [networks]. Cover contract versioning, bridge risk, configuration, testing, monitoring, incident response, and rollback constraints.
```

## Limitations

- Generated contracts and architectures require independent audits, tests, and environment-specific validation.
- The skill does not replace legal, tax, regulatory, custody, or financial advice.
- It cannot independently deploy contracts, manage wallets, or approve transactions.
- The referenced implementation playbook is not included in the published file structure.

## Best Practices

- Define trust assumptions, invariants, privileged roles, and emergency controls before writing contracts.
- Use established libraries and combine unit, integration, fuzz, invariant, and static analysis tests.
- Deploy to testnets first, monitor critical events, and obtain independent review before managing valuable assets.

## Anti Patterns

- Do not deploy unaudited generated contracts directly to a production network.
- Do not place private keys, seed phrases, or production secrets in prompts or source files.
- Do not optimize gas before validating correctness, access controls, economic assumptions, and failure behavior.

## Security Audit

- Audited at: 2026-08-14T10:35:13.358\+00:00
- Summary: All three static findings are false positives caused by Markdown formatting or descriptive security guidance. No executable commands, secret collection, reconnaissance behavior, prompt injection, or malicious intent were found.

## Stats

- Views: 91
- Downloads: 15
- Favorites: 0
- Popularity score: 0