Skip to content
Maxy
Learn
CompareMuseum

MaxyMint · proof-gated minting and redemption for wrapped Bitcoin

A better way to wrap Bitcoin.

MaxyMint replaces the mint desk with a proof. A user pays Bitcoin to a deposit address, Maxy’s on-chain Bitcoin verifier checks the payment, and your existing wrapped token mints itself, to a wallet or straight into Aave, Morpho, Venus, or any vault, in one transaction.

Same token contract, same listings, same liquidity, same TVL. No exchange account, no attestation, no help desk. Just a proof.

Tier 1 · who it’s for · issuers and DeFi protocols

One proof rail, two kinds of customer

Issuers keep their token and their custody. DeFi protocols get native Bitcoin deposits inside their own app.

For wrapped Bitcoin issuers

Keep the token. Keep the custody. Drop the desk.

Your token is already listed, integrated, and deep. MaxyMint does not ask you to launch a new one. It takes the minter role on the token you have and gates every mint behind a proof of the Bitcoin payment, verified on-chain. Deposits and redemptions stop being a workflow your staff runs and become a condition the contract checks.

For DeFi protocols

Native Bitcoin deposits, inside your app, in one transaction

A user with Bitcoin in a cold wallet can fund a position in your market without an exchange, a bridge UI, or a wrapping step they run themselves. They pay a deposit address, the proof lands, the wrapped token mints, and it is supplied on their behalf in the same transaction. You get real Bitcoin TVL through the token your market already lists.

The proof is the permission
One Bitcoin transaction. One proof. Your token, minted by math.

Anyone can submit the proof · nobody can block it.

Tier 2 · the mechanism · register, pay, prove, mint

One Bitcoin transaction, one proof, one mint

The user pays a deposit address from any Bitcoin wallet. The proof does everything a desk used to do.

Each Bitcoin payment mints exactly once, ever. Amounts convert without rounding: 25,000,000 satoshis is 0.25 tokens, to the unit. If a protocol cannot accept the deposit at proof time, the tokens go to the recipient’s claimable balance instead.

Step 1 · Register

One deposit, declared on-chain

A deposit address, the exact amount, the confirmation depth, and where the tokens should go: a wallet, or a lending protocol. The choice can change until the proof lands.

Step 2 · Pay

Bitcoin from any wallet

Hardware wallet, mobile wallet, exchange withdrawal. One ordinary Bitcoin payment of the exact amount to a single-use address.

Step 3 · Prove

Anyone submits the proof

A keeper does it by default, but the contract accepts a valid proof from anyone. The verifier checks the block, the amount, the script, and the depth.

Step 4 · Mint & deliver

Your token, minted and placed

Exact conversion, fee split, mint. Wallet mode delivers to the named recipient. Protocol mode supplies the vault and hands back the receipt token.

The proof is the permission · nobody attests, nobody approves

The mint is a condition, not a decision

The keeper that usually submits it holds no special power; a user could submit their own proof from a laptop and get the same result.

A custodial mint desk decides. MaxyMint has no button.

Someone looks at a deposit, matches it to an account, and pushes a button. Tokens mint only when a cryptographic proof of the exact payment, at the required depth, passes the same on-chain Bitcoin verifier that settles Maxy swaps.

From Bitcoin to yield · protocol delivery

From Bitcoin to yield in one transaction

At registration the user picks protocol delivery and a market. When the proof lands, the freshly minted token is supplied to that market on the user’s behalf and the receipt token, an aToken, a vToken, or vault shares, arrives in their wallet.

Capital

No idle stop between wrap and deposit

Interest accrues from the mint block.

Safe fail

A protocol problem never blocks a valid mint.

If the market is capped, paused, or frozen, tokens land in a claimable balance the user can withdraw or redirect.

Tier 3 · trust & compliance · enforced in code, auditable from events

Compliance by construction, not by policy

No attestation, no admin path to tokens, no upgrade proxy. Every mint is reconstructable from events.

The question The mechanism What it means for you

Can a mint be faked?

Supply = proven deposits

The sum of proven satoshis equals the tokens the contract has ever minted. Invariant, fuzzed.

Can an admin touch tokens?

No discretionary party

The admin is a timelock with capped parameters and no path to user funds.

Can the rules change?

What you audit is what runs

A replacement is a new contract granted the minter role, never a silent change to the old one.

Can a mint be stopped?

Paid Bitcoin always mints

Containment is revoking the minter role, which stops new mints while every already-minted claim keeps working.

Can it be audited?

A full trail, no identity gate

Regulators and auditors read the ledger; users never hand a desk their identity to mint.

Who holds the Bitcoin?

Honest boundary

MaxyMint removes the desk from the mint and redeem path. It does not pretend to remove the vault.

Redemption · no black-hole help desk

Unwrapping runs on the same proof

Redemption is where wrapped Bitcoin loses trust today: a ticket, a queue, a human, and no guarantee of a reply. MaxyMint treats a burn the way it treats a deposit. The holder burns tokens and names a Bitcoin address on-chain; the burn itself is the request, and the release is governed by the same proof rail that governs the mint.

Nobody triages it. Nobody can lose it.

Chains

Specified on BNB Chain, built for every chain

The verifier is the only dependency. Where Maxy verifies Bitcoin on-chain, MaxyMint can mint.

On BNB Chain the launch adapters cover the three largest lending markets that list a BTC token, roughly two billion dollars of supplied TVL between them. Every other chain gets the same three shapes: an Aave V3 adapter, a Compound-style adapter, and a generic ERC-4626 adapter that serves Morpho-design vaults and anything built like them.

Reference deployment: BNB Chain.

Same contract shape on Ethereum, Base, Arbitrum, Solana, Tron, Robinhood Chain.

Launch adapters: Venus, Aave V3, Lista Lending.

Any wrapped Bitcoin

Any BTC-denominated token

An existing token needs only standard transfer semantics and at least 8 decimals. No transfer hooks, no rebasing, no fee on transfer. One whole token is one Bitcoin, converted without rounding.

Any Bitcoin wallet

Native Bitcoin, from anywhere

Deposits are ordinary Bitcoin payments to single-use addresses, recommended P2WPKH and P2TR at launch. Sizes from 10,000 satoshis to 100 BTC per deposit, with a daily assignment cap enforced on-chain.

Any lending market

Three adapter shapes cover the field

Aave V3, Compound-style, and ERC-4626. Adding a market is deploying a small immutable adapter and allow-listing it through the timelock. The core contract never changes.

MaxyMint

Same token. Same liquidity. No desk.

Wrapped Bitcoin already won the integrations. What it never had was a mint and redeem path nobody has to trust. MaxyMint bolts that path onto the token you already run, and lets a user go from a cold wallet to a yield position in one transaction.

Custody stays where it is, auditable by proof of reserves. Everything else is enforced by code and readable from events.

One Bitcoin transaction. One proof. Your token, minted by math.

1 transaction · 0 attestations · 0 tickets