bch-development
BCH (Bitcoin Cash) Development Rules
🚨 CRITICAL: Override Pattern for BCH-Specific Logic
This is a non-negotiable architectural rule. BCH implementation uses struct embedding with method override pattern.
Architecture Overview
// internal/infrastructure/api/btc/bch/bitcoin_cash.go
type BitcoinCash struct {
apibtcimpl.Bitcoin // Embeds BTC implementation
}
Key Principle: BitcoinCash embeds Bitcoin, inheriting all BTC methods by default.
Rules
More from hiromaily/go-crypto-wallet
shell-scripts
Shell script development workflow. Use when modifying files in scripts/ directory or any *.sh files.
50makefile-update
Makefile development workflow. Use when modifying Makefile or files in make/ directory.
35docs-update
Documentation update workflow. Use when modifying files in docs/ directory or any markdown files (*.md).
34btc-terminology
Critical Bitcoin terminology rules to prevent confusion between bech32m (encoding) and taproot (address type). Use when working on BTC-related code, config files, or shell scripts.
34db-migration
Database schema and migration workflow. Use when modifying database schemas in tools/atlas/ or SQLC queries in tools/sqlc/.
31openspec-propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
27