Keep crypto clean.
Not all Bitcoin is treated equally. Coins that trace to hacks or sanctions get frozen on arrival. cBTC is Bitcoin you can prove is clean — backed 1:1, provenance-screened, verifiable on-chain.
Your Bitcoin has a history — and you can't see it.
Blockchain analytics can trace any coin back through hacks, scams and sanctioned wallets. Exchanges use it to freeze deposits on arrival. You did nothing wrong, but the coin's past is now your problem.
Prove your coins are clean. Don't hide them.
Hakky turns cleanliness into a portable, on-chain asset. Mint cBTC from screened Bitcoin, carry a verifiable attestation of provenance with it, and redeem 1:1 for BTC anytime. Mixers do the opposite of this — and so do we.
A mixer / tumbler
- Breaks the link between sender and receiver
- Obscures where funds came from
- Serves people with something to hide
- Makes coins more suspect, not less
Hakky Protocol
- Keeps provenance transparent and on-chain
- Attests where funds came from, in public
- Serves honest holders who want to prove it
- Makes coins portably clean across venues
Three moves: screen, mint, redeem.
Every cBTC is minted only against BTC that has passed screening, and can never exceed the Bitcoin held in reserve. The whole loop is enforced by five open-source contracts.
Deposit is screened
You send BTC to protocol custody. Its provenance is checked and an accredited attestor publishes a signed cleanliness attestation on-chain via the AttestationRegistry.
cBTC is minted 1:1
The ReserveVault verifies the deposit and mints cBTC — but only if supply stays within attested reserves: totalSupply() ≤ reserveSats().
Move it, prove it, cash out
Hold or transfer cBTC anywhere. Burn it through the vault to redeem native BTC 1:1 — the reserve shrinks to match. Always fully backed.
Five contracts. One clean invariant.
A small, auditable surface. Each module does one job, and every one of them is public.
Clean BTC
8-decimal, 1:1 BTC-backed token. Supply is capped by proven reserves; transfers can be compliance-gated but ship open by default.
Cleanliness attestations
Accredited attestors publish signed, expiring provenance attestations per address — score, sanctions flag and an evidence link. Public and revocable.
Proof of reserves
Publishes the attested BTC reserve balance that backs cBTC, plus a pointer to the signed custody report. Anyone can verify the peg on-chain.
Configurable policy
Monitor · Gated · Allowlist modes. Ships in monitor-only — cBTC behaves like any ERC-20 until governance ever chooses to enable gating.
Mint & redeem gateway
The one door in and out: mints against verified deposits with replay protection, and burns cBTC to release BTC 1:1 on redemption.
Nothing hidden.
Every contract, test and deploy script is MIT-licensed and public.
Browse contracts →Fully backed, and honest about how.
The peg is protected by a single public invariant enforced at mint time: cBTC in circulation can never exceed the BTC held in reserve. You don't have to trust a dashboard — you can read it from the chain.
We're equally clear about what v1 isn't: like every 1:1 BTC-backed token today, reserves sit with qualified custody and a multisig publishes the attestation. That's not trustless — and we say so. The roadmap moves toward decentralized custody and zk proof-of-reserves.
See it working — right now.
These read straight from the deployed contracts through the public API at api.hakky.xyz. Testnet data, live on-chain.
Check an address
Enter any address to read its on-chain cleanliness attestation.
Protocol activity
From honest custody to trust-minimized.
We ship what works today and decentralize deliberately — no vaporware milestones.
Foundation
- cBTC + full contract suite
- Attestation registry
- Proof-of-reserves oracle
- Testnet + audit prep
Live peg
- Qualified-custody reserves
- Attestor onboarding
- Mainnet cBTC
- Public PoR reporting
Decentralize
- MPC / threshold custody
- Multi-attestor network
- zk proof-of-reserves
- DeFi integrations
Governance
- $HAKKY governance
- Community attestor accreditation
- Parameter & fee governance
$HAKKY is a roadmap governance token. There is no token sale, presale, or airdrop, and none is implied by this page.
The questions you should be asking.
Is this a mixer?
No — it's the opposite. A mixer breaks the link between sender and receiver to obscure where funds came from. Hakky keeps provenance fully transparent and on-chain, and helps honest holders prove their coins are clean. Nothing is hidden, mixed, or anonymized.
Is it a surveillance tool, then?
No. Attestations are user-consented, portable proofs you opt into to unlock clean liquidity — not blanket monitoring. The registry only records the attestations that attestors publish; it doesn't track your activity, and cBTC ships in monitor-only mode where transfers aren't gated at all.
What actually backs cBTC?
Native Bitcoin, 1:1. Each cBTC (8 decimals, so 1 base unit = 1 satoshi) is minted only against BTC in reserve, and a smart-contract invariant makes it impossible for supply to exceed the attested reserves. Burn cBTC to redeem BTC at any time.
Is v1 trustless?
No, and we won't pretend otherwise. v1 uses qualified-custody reserves and a multisig-published proof-of-reserves, exactly like every 1:1 BTC-backed token in production today. The roadmap moves custody and attestation toward MPC/threshold signing and zk proof-of-reserves.
Is $HAKKY a token I can buy?
Not now. $HAKKY is a roadmap governance token. There is no sale, presale, or airdrop today, and this page is not an offer of any security or a solicitation to buy anything. Ignore anyone claiming otherwise.
Can I read the code?
Yes. The entire protocol — contracts, tests, deploy scripts, and the whitepaper — is MIT-licensed and public on GitHub. Audit, don't assume.
Clean coins deserve proof.
Read the whitepaper, browse the contracts, and follow the build. Hakky is open-source and open to scrutiny.