Author: David Knight | Date: April 2026 | Status: Live (On-Chain Verified)

Crypto solved ownership.

It hasn’t solved usage.

This proof of concept demonstrates a different model:

Hold the asset → Use it as collateral → Unlock liquidity → Spend → Keep the asset

All executed on-chain. All verifiable.

In 2020, I was in the Dominican Republic.

At a resort, I saw something that stuck with me: A booth offering car rentals paid in Bitcoin.

It felt like the future.

Bitcoin — not just as a store of value — but as something you could actually use.

Six years later, that future hasn’t arrived.

Bitcoin didn’t evolve into a payment system. It consolidated into something else:

A store of value.

Even attempts like Lightning haven’t meaningfully changed this.

So the reality today is still:

Hold crypto → Spend fiat

Most users operate in two systems:

• Store value → crypto

• Spend → fiat

The limitation isn’t theoretical. It’s behavioral.

To spend a volatile asset: You have to sell it.

And that creates friction:

• Breaks long-term positioning

• Introduces timing risk

• Triggers potential tax events

So users don’t spend.

They hold.

Some solutions exist:

• Card integrations

• Wallet payment rails

• Stablecoin spending

These work — but only for one category:

Stablecoins

Not for:

• Bitcoin

• Ethereum

• Long-term holdings

What doesn’t exist cleanly today:

A volatile asset → used directly as collateral → to enable spending → without selling it

While remaining:

• in native form

• non-custodial

• structurally unchanged

This is the entire system:

[ Hold Asset ] → [ Use as Collateral ] → [ Borrow Stablecoin ] →[ Spend ] → [ Repay ] →[ Reclaim Original Asset ]

This is what was tested.

Protocols like:

• Aave

• Morpho

• Dolomite

already enable:

Collateral → Borrow → Repay

But the constraint is in the type of collateral:

Most assets are:

• Inflationary (e.g. AAVE, LINK)

• Wrapped (WBTC, WETH)

• Governance-controlled

• Not structurally final

Which introduces:

• Monetary policy risk

• Smart contract risk layers

• Custodial dependencies (in some cases)

So while liquidity exists — clean collateral does not.

One of the strongest properties in crypto:

Fixed supply

• No dilution

• No governance

• No policy changes

But historically:

These assets are not used They are held

This POC explores a different path:

Use a fixed-supply asset not just as storage but as collateral for real-world usage

A minimal lending system was deployed using Ethereum as the base layer.

Structure:

• Collateral: CRNC (fixed supply ERC-20, Ethereum L1)

• Borrow asset: USDC (borrowed on Ethereum L1)

• Execution 1 — Borrow USDC: Collateral + borrowing → Ethereum L1

• Execution 2 — Purchase with USDC: Payment rail → Base (L2)

Flow:

1. Deposit CRNC (L1)

2. Borrow USDC (L1)

3. Transfer USDC to payment rail (Base L2)

4. Spend in real world

5. Repay USDC (L1)

6. Withdraw CRNC (L1)

No wrapping of the collateral. No modification of the asset. No custody layer.

All steps were executed live.

Contract: 0x3bD7Fdf59E08f809A26927E1694930786C8e7709

Example:

• 20,000 CRNC deposited

• 2 USDC borrowed

• Fully repaid

• Collateral reclaimed

Full step-by-step log:

https://currenc.co/CRNC_POC1_steps.pdf

The borrowing and collateral lifecycle remained entirely on Ethereum mainnet. The only off-extension in this flow was the payment rail, which utilized Base L2 for retail settlement.

This confirms a working model:

Ownership ≠ Spending

You can:

• Keep the asset

• Access liquidity

• Spend without exiting

This is a structural shift. CRNC remained entirely on Ethereum L1 throughout the process. The asset never moved layers. Only the liquidity did.

The system works — but not cleanly end-to-end.

Current limitations:

• Payment rails rely on L2 (Base in this case)

• Bridging introduces additional steps

• Execution spans multiple environments

Importantly:

Collateral integrity remained fully on Ethereum L1 No bridging, wrapping, or modification of CRNC occurred.

This separation highlights the current gap:

Financial logic is solved on L1 Spending infrastructure still relies on external layers

Another real constraint:

Most users don’t want:

• fully traceable spending

• public transaction history tied to purchases

This POC does not solve that.

But Ethereum is actively moving in this direction.

Relevant direction (Ethereum roadmap)

• Account abstraction evolution

• Transaction bundling

• Privacy-preserving execution research

Vitalik has outlined paths toward:

• privacy layers

• stealth addresses

• shielded interactions

Timeline: Gradual rollout across 2026–2027 cycles (not a single release)

CRNC, as a native ERC-20, inherits these improvements automatically.

This system is only possible because of Ethereum:

• Programmable execution

• Deterministic smart contracts

• Asset composability

Without it:

This entire flow breaks.

This POC was built during a transition phase.

Upcoming upgrades remove major friction:

1. Higher L1 Throughput (2026)

• Lower fees

• Faster execution → Small payments viable on L1

2. Account Abstraction (EIP-7702 / 8141)

• Multi-step flows → single transaction, UX collapse into one action

3. Gas Abstraction

• Pay gas in stablecoins → Removes ETH dependency

If Ethereum-native payment rails (e.g. wallet-integrated card networks on L1) had been available, this proof of concept would have executed entirely on Ethereum without reliance on L2.

Not a product.

Not a platform.

A primitive:

A fixed-supply asset → usable without being sold

Crypto solved ownership.

The missing piece is:

using that ownership without giving it up

This worked.

Not conceptually. Not theoretically.

On-chain.

This document is a technical demonstration.

It is not financial advice or a recommendation to use any asset or protocol.