Bitcoin Hush

${ project.category.slug }

${ project.token } (${ project.short_token }) #${ project.rank }

${ project.name }

@${ project.slug }

$${ project.price }

${ project.price_btc } BTC

Socials

Explorers

${explorer.short}

MarketCap	$ ${ project.market_cap }
Volume(24h)	$ ${ project.volume_24 }
Circulating Supply	${ project.circulating_supply } ${ project.short_token }
Total Supply	${ project.total_supply } ${ project.short_token }

Contacts

@${ admin.user.username }

Similar projects

@MarkhorMeta

@peerguess

@meme

About the project

What makes BTCH different than all the other BTC forks and things?

BTCH is not something that has ever existed before, it is not a chain split nor code fork of HUSH,
nor ZEC, nor BTC, it is a KMD asset chain with imported UTXO dataset.

BTCH takes the value from four different blockchains (HUSH, SUPERNET, DEX, BTC), and then dumps it onto a host chain Komodo (KMD).
It does not fork from KMD, nor does it fork from BTC or HUSH. It is technically NOT A FORK, but a merged airdrop.

So BTCH is actually a Komodo asset chain with all the money from four other different blockchains, mixed into one big HODLer tossed salad.
Also, BTCH is protected by the full hashpower of Bitcoin because Komodo has delayed Proof-Of-Work (dPOW)
which essentially syncs the KMD blockchain to the BTC blockchain occasionally.