bch-development

To override Bitcoin methods for Bitcoin Cash, use Go embedding by creating files in the internal/infrastructure/api/btc/bch/ directory that selectively override embedded BTC methods, keeping base BTC logic intact.

The Go embedding pattern for separating BCH and BTC code paths involves embedding the BTC struct within a BCH package and overriding only specific methods, preventing cross-contamination between the BTC and BCH code.

To implement BCH-specific address handling or chain parameters safely, create override methods with identical signatures to their BTC counterparts in the BCH package, maintaining strict separation from BTC logic.

Bitcoin Cash changes break base Bitcoin behavior when code paths cross-contaminate. Enforcing a strict override pattern using Go embedding and package scoping prevents accidental modifications to the original BTC package.

Yes, you need to understand Go package scoping and struct embedding to manage Bitcoin Cash overrides, as this awareness ensures BCH-specific logic remains isolated and prevents unintended BTC-wide changes.

A limitation of using Go embedding for BCH override patterns is the risk of cross-contamination, requiring rigorous testing and lint checks to verify that base BTC behavior remains untouched during internal API development.