blockchain-pollyanna
Critical analysis of blockchain hype and solutions looking for problems. Use when evaluating blockchain proposals, teaching about technology hype cycles, or distinguishing genuine use cases from marketing.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- blockchain-pollyanna
- license
- MIT
- metadata
- { "exposes": "technology-hype", "category": "parody", "educational": true }
- description
- Critical analysis of blockchain hype and solutions looking for problems. Use when evaluating blockchain proposals, teaching about technology hype cycles, or distinguishing genuine use cases from marketing.
03 SKILL.md 正文
Blockchain Pollyanna
Educational guide to blockchain hype - when solutions go looking for problems.
Overview
This skill teaches critical evaluation of blockchain proposals, distinguishing genuine use cases from hype-driven nonsense. Named for excessive optimism about blockchain solving every problem.
The Pattern
Blockchain Pollyanna claims:
- "Put voting on blockchain!" (solves problems that don't exist)
- "Blockchain for supply chain!" (databases work fine)
- "Decentralized everything!" (centralization has benefits too)
- "Web3 will replace everything!" (usually means "I have tokens to sell")
Blockchain: What It Actually Is
Technical reality:
- Distributed append-only ledger
- Consensus mechanism for untrusted parties
- Trade-offs: slow, expensive, energy-intensive
- Good for: Preventing double-spending without trusted party
Not magic: Just a database with specific trade-offs
The Hype Cycle
Phase 1: Solution Looking for Problem
"We have blockchain! What problems can it solve?"
- Backwards from real innovation
- Real innovation: Problem → Solution
- Hype: Solution → Find problems
Phase 2: Ignore Existing Solutions
"Blockchain for medical records!"
- Existing solution: Encrypted databases (work fine)
- Blockchain adds: Complexity, cost, slowness
- Benefit: Unclear or non-existent
Phase 3: Handwave Technical Problems
"Details don't matter, blockchain is the future!"
- Scalability? "We'll solve it later"
- Energy use? "That's being improved"
- User experience? "Not important yet"
When Blockchain Actually Makes Sense
Legitimate use case criteria:
- Need untrusted parties to agree on state
- No trusted third party available/wanted
- Transparent history is valuable
- Worth the trade-offs (slow, expensive, complex)
Actual good use: Cryptocurrency (maybe!)
- Decentralized money without banks
- Trust math instead of institutions
- Censorship-resistant transactions
Even then: Trade-offs (slow, volatile, environmental cost)
When Blockchain Makes NO Sense
"Blockchain for Voting"
Problems it claims to solve: Voter fraud (rare), lack of transparency
Problems it creates:
- How to verify voters without central authority?
- Secret ballot vs transparent blockchain (contradiction!)
- 51% attack could steal election
- Bugs in code = election compromised
- Paper ballots are more auditable
Verdict: Blockchain creates more problems than it solves
"Blockchain for Supply Chain"
Claims: Transparency, provenance tracking
Reality:
- Databases already do this
- "Garbage in, garbage out" (blockchain can't verify physical reality)
- Adding blockchain adds cost with no benefit
- Centralized databases work better
Verdict: Regular database is better, cheaper, faster
"Blockchain for Medical Records"
Claims: Patient control, interoperability
Reality:
- HIPAA requires deletion (blockchain is immutable!)
- Private medical data on public ledger? (Terrible idea!)
- Encryption helps but adds complexity
- Centralized encrypted databases work better
Verdict: Blockchain contradicts medical privacy requirements
Red Flags
Watch for:
- "Put X on blockchain!" without explaining why
- Ignoring existing solutions that work
- Handwaving technical problems
- "Revolutionary" without specifics
- Token sale involved (conflict of interest!)
- "Decentralized" as virtue regardless of cost
The Questions to Ask
For any blockchain proposal:
- What problem does this solve?
- Why can't a database solve it?
- Who are the untrusted parties?
- Is transparency worth the trade-offs?
- Who profits from this proposal?
- Have they tried non-blockchain solutions?
Usually: Answers reveal database would work better
Why People Fall For It
Reasons for blockchain hype:
- Sounds futuristic and innovative
- Financial incentive (tokens!)
- Genuine distrust of institutions (sometimes justified!)
- Bandwagon effect ("Everyone's doing it")
- Complexity masks lack of substance
- "Decentralized" sounds ideologically appealing
But: Technology should solve real problems, not theoretical ones
The Honest Assessment
Blockchain strengths:
- ✅ Decentralized consensus
- ✅ Transparent history
- ✅ Censorship-resistant
- ✅ No trusted third party needed
Blockchain weaknesses:
- ❌ Slow (compared to databases)
- ❌ Expensive (computational cost)
- ❌ Energy-intensive (environmental cost)
- ❌ Immutable (can't fix mistakes easily)
- ❌ Scalability problems
- ❌ User experience challenges
Use when: Strengths outweigh weaknesses (rare!)
Educational Use
Use this skill to:
- Teach critical evaluation of tech hype
- Distinguish marketing from substance
- Understand trade-offs in system design
- Recognize solutions looking for problems
- Ask the right questions about proposals
The Bigger Lesson
Technology is tools, not magic:
- Every technology has trade-offs
- Match tool to problem
- Existing solutions often work better
- Hype ≠ substance
Blockchain isn't bad - it's just not the solution to every problem!
Note: This skill critiques hype, not the technology itself. Blockchain has legitimate uses - but most proposed uses aren't among them.
04 同仓库更多 Skills
Docs Research
Use MCP Central Docs server to search, ask, and retrieve documentation (FastMCP, standards, packaging).
wrappee-drift
Read-only, single-repo audit of a repo's tool coverage against the software it wraps (its current real API/docs, not training-data memory) and against comparable/competing wrappers. Trigger when the user says "wrappee drift" followed by a repo name, "capability audit" followed by a repo name, or asks whether a repo is missing features the wrapped software or a competitor now has. Always scoped to one named repo per invocation -- never trigger this fleet-wide or unprompted; that is explicitly against the SOP. Do NOT trigger for internal fleet-standard compliance (that is drift-scan) or strategic worth/archive decisions (that is quality-check) -- this is specifically about the gap between the repo's tool list and the wrapped software's/competitors' actual current capabilities.
modules
暂无简介
mcp-standards
Use when developing MCP servers to access comprehensive standards for scaffolding, packaging, sampling, documentation, testing, error handling, monitoring, and CI/CD workflows.
webapp-cua-test
Run the pre-Tauri CUA click-through test (real browser, dev stack, OCR "Connected" wait, sidebar nav walk) for a fleet MCP server repo under D:\Dev\repos. Trigger when the user says "cua webapp test" or "webapp clickthrough" followed by a repo name, asks for an e2e click-through of a webapp, or asks whether a webapp boots and connects in a real browser. Not for the installed NSIS app (that is the nsis-build skill / cua-nsis-test) and not for DOM assertions (Playwright), and not for hunting fake data or dead buttons (fakefind).
ship
Final release gate for a fleet MCP server repo under D:\Dev\repos -- run all quality gates, build the release artifact, verify it, commit, push, and cut a GitHub release. Trigger this whenever the user says "ship it", "ship" followed by a repo name, "release" followed by a repo name, or asks to finalize and publish work that's already been done in a repo. This is the terminal step after assfix/nsis-build, not a substitute for them -- if the repo hasn't been assessed recently, say so before shipping rather than shipping blind.