Author: David Knight, Founder of CurrenC (CRNC)
Date: August 2026
Status: Comparative Research Paper
Open an Ethereum wallet and Wrapped Bitcoin (WBTC) and CurrenC (CRNC) may appear to belong in the same category. Both are ERC-20 tokens on Ethereum. Both can be transferred between wallets, traded through decentralized exchanges, held in self-custody, and potentially used in lending markets, liquidity pools, vaults, and other decentralized applications. Both are also associated with digital scarcity and a headline supply of 21 million: WBTC through its representation of Bitcoin, and CRNC through a fixed supply defined directly in its own Ethereum contract.
That surface similarity, however, conceals a fundamental difference. WBTC is a tokenized representation of Bitcoin held elsewhere, and its circulating supply can expand or contract through minting and redemption. CRNC is not a representation of another asset. Its full supply was created once at deployment, with no continuing minting authority, governance process, or custodial reserve behind it.
WBTC was created to solve a real interoperability problem. Bitcoin and Ethereum are separate networks, and native BTC cannot simply be deposited into an Ethereum smart contract. Bitcoin does not use the ERC-20 standard, so its native asset cannot directly participate in Ethereum lending markets, decentralized exchanges, vaults, or other applications.
WBTC addresses this limitation by creating an Ethereum-compatible representation of Bitcoin. BTC is held in custody while a corresponding amount of WBTC is issued. That WBTC can then circulate through compatible wallets and protocols while representing a claim on the BTC held in reserve.
The system divides responsibilities among custodians, merchants, and governance participants. Custodians secure the underlying BTC, merchants facilitate minting and redemption, and governance participants oversee certain aspects of the system. WBTC also maintains public proof-of-reserves infrastructure so that users can compare the amount of BTC held in custody with the amount of WBTC in circulation.
This model has provided substantial utility. It has allowed Bitcoin liquidity to participate in Ethereum-based financial markets without requiring Bitcoin itself to become an Ethereum-native asset. The custodial structure is therefore not an accidental flaw attached to WBTC; it is the mechanism that makes the product possible.
The same mechanism that makes WBTC useful also creates dependencies that do not exist when holding native BTC directly. A WBTC holder relies on the underlying BTC remaining securely held, the amount issued remaining consistent with reserves, and authorized participants continuing to administer minting and redemption correctly.
Holders of WBTC also depend on the custody and governance arrangements remaining sufficiently secure over time. Changes involving keyholders, institutions, jurisdictions, or operating policies can affect the perceived risk of the asset even when the underlying BTC remains untouched.
Proof of reserves can demonstrate that backing exists, but it cannot eliminate custody. A multisig wallet arrangement can distribute authority, but it cannot eliminate the existence of keyholders. Governance can provide oversight and transparency, but it cannot make institutional decision-making unnecessary.
These systems may substantially reduce the probability of misuse or failure. They manage the trust structure, but they do not remove it. WBTC remains a claim on BTC held under an organized custody and redemption system; it is not native Bitcoin.
This distinction became especially visible in August 2024, when BitGo announced that the WBTC business would transition to a multi-jurisdictional custody arrangement through a partnership with BiT Global. The announcement generated concern across parts of the DeFi industry, particularly because of the perceived risks associated with the new structure and the involvement connected to Justin Sun.
Maker governance subsequently moved to reduce its exposure by lowering debt ceilings for WBTC-related vaults. This prevented the protocol from substantially increasing its WBTC-backed exposure rather than immediately eliminating every existing position. Coinbase launched its own wrapped Bitcoin product, cbBTC, the following month and later announced that it would suspend WBTC trading in December 2024.
The important lesson is not that WBTC lost its backing, failed to honor redemptions, or collapsed. None of those things occurred. The episode demonstrated that the risk profile of a wrapped asset can change when its custodians, keyholders, jurisdictions, governance relationships, or operating arrangements change.
Bitcoin’s monetary rules had not changed, and Ethereum’s rules had not changed. The institutions surrounding WBTC were changing, however, and DeFi protocols had to decide whether they remained comfortable with the resulting dependencies.
That is a defining characteristic of a custodial representation. Its security is not determined exclusively by the blockchain on which the token appears or by the blockchain securing the underlying reserve. It also depends on the organizations and processes connecting the two.
CRNC begins from a different premise. It was not created to represent an asset held on another network, and there is no underlying BTC, currency, commodity, or external reserve against which it can be redeemed. CRNC is the asset itself.
Its total supply of 21 million tokens was created once at deployment. The contract contains no continuing authority to issue more, burn tokens at discretion, freeze wallets, pause transfers, alter balances, upgrade the code, adjust monetary parameters, or govern the asset through tokenholder voting.
Like Bitcoin, CRNC has no continuing issuer or owner with discretionary authority over the asset. Unlike Bitcoin, its token rules are not subject to a future governance or consensus process of their own. There is no custodian, redemption promise, reserve requirement, bridge, administrator, proxy, DAO, multisignature group, or tokenholder vote with the power to amend the deployed contract’s supply policy or core behavior. There was no token-level control to retain or later renounce.
WBTC depends on institutions continuing to administer custody and redemption correctly. CRNC’s supply and token-level behavior remain determined by the deployed contract. Applications and markets around CRNC may still be governed, but they cannot rewrite the asset’s underlying code.
CRNC’s native design does not remove every form of risk, but it does remove the reserve, redemption, custody, and bridge dependencies inherent to a wrapped asset.
CRNC is young as a market asset, but its technical foundation is not experimental. It is built on the ERC-20 standard, which has been widely reviewed, audited, and battle-tested across Ethereum for nearly eleven years. CRNC adds no upgradeability, governance, emissions, transfer restrictions, or discretionary administrative functions, keeping its contract logic and control surface deliberately minimal.
Users also do not need to rely on CurrenC’s statements alone. The deployed contract is verified on Etherscan, where the source code and on-chain bytecode can be inspected. Supporting documentation and security-review results are publicly available through GitHub and HackenProof, while supply, balances, transfers, and liquidity actions can be independently verified on-chain.
CRNC’s remaining risks are mainly market, user, network, and integration risks. Liquidity and adoption can change, holders remain responsible for wallet security, and external exchanges, lending markets, interfaces, and oracles may introduce dependencies of their own.
Those risks should not be confused with uncertainty over CRNC’s monetary rules. Its supply cannot be expanded, its token contract cannot be upgraded, and no custodian or administrator must continue acting correctly for those properties to remain in effect.
Applications built around CRNC may depend on adjustable or governed components such as oracles, collateral parameters, interfaces, and external smart contracts. Those systems can determine how CRNC is used, but they cannot rewrite its supply or token-level rules. The integrations can evolve while the asset remains unchanged: asset finished, integrations ongoing.
This also helps clarify why CRNC and WBTC are not direct substitutes. WBTC exists to provide tokenized exposure to Bitcoin inside Ethereum-based applications, while CRNC is a separate Ethereum-native asset with no claim on BTC and no redemption mechanism. The comparison is therefore not about whether CRNC can replace WBTC’s function, but about the different dependencies each model introduces after the token enters a holder’s wallet.
Digital assets are often evaluated by asking whether they are audited, backed, liquid, widely integrated, or governed responsibly. Those are all reasonable questions, but another question deserves equal attention:
Which of the asset’s essential properties still depend on someone’s future permission, performance, or judgment?
With WBTC, holders depend on an organized system continuing to secure BTC reserves, maintain verifiable backing, administer issuance and redemption, and preserve confidence in its custody arrangements. That is a transparent tradeoff made in exchange for bringing Bitcoin liquidity into Ethereum and other compatible financial systems.
With CRNC, the core monetary rules do not depend on a custodian, issuer, administrator, or governance body continuing to honor them. There is no reserve promise to maintain, no redemption policy to preserve, no minting authority that must remain restrained, and no token administrator whose replacement could alter the supply rules.
This does not mean CRNC depends on nothing. It still relies on Ethereum for execution and settlement. Holders remain responsible for their own operational security, and external markets and integrations introduce their own dependencies.
The narrower and more meaningful distinction is that CRNC’s supply policy and token-level behavior are not promises requiring future institutional performance; they are properties of the deployed asset. WBTC and CRNC can therefore look similar from the outside while answering the ownership question in fundamentally different ways.
Neither design alone determines market value, adoption, or future success. It does, however, determine what is being held, and who, if anyone, must continue preserving the rules behind it.
CRNC:
CurrenC Official Website: https://currenc.co
CurrenC Links and Resources: https://currenc.co/links.html
Includes the verified CRNC contract on Etherscan, published source code on GitHub, HackenProof audit results, CertiK Token Scan, market and liquidity data, and CRNC proof-of-concept resources.
WBTC:
WBTC Official Website and Proof of Reserves: https://wbtc.network/transparency
BitGo WBTC Custody Announcement — August 9, 2024: https://www.bitgo.com/resources/blog/bitgo-to-move-wbtc-to-multi-jurisdictional-custody-to-accelerate-global/
Maker Governance WBTC Debt-Ceiling Decision — August 2024: https://vote.makerdao.com/executive/template-executive-vote-wbtc-vault-debt-ceiling-reductions-stability-scope-parameter-changes-bug-bounty-payments-clippermomjob-update-july-2024-aligned-delegate-compensation-6s-capital-stability-fee-increase-monetalis-clydesdale-and-coinbase-custody-dao-resolutions-spark-proxy-spell-august-12-2024
Coinbase WBTC Trading Suspension Announcement — November 19, 2024:
