Skip to content
Maxy
Learn
CompareMuseum

Maxy · the escrow runs a Bitcoin node

Bitcoin in milliseconds.

Maxy settles signed EVM orders in real Bitcoin in a median 438 ms, signature to broadcast. It’s the first settlement path where the contract holding the money verifies Bitcoin itself (a Bitcoin node, engineered for efficiency and accuracy, running inside the escrow), so every intermediary built to relay Bitcoin’s state, and every wait it imposes, is gone.

Signature to Bitcoin broadcast · 30-day median

Three steps.
No third network, no vault, no HTLC.

Your total time · one order, traced live median · 30-day window · dated on the status page

One hop for your Bitcoin: solver’s wallet → your address

Real BTC, no vault, no wrapped asset.

The node · live, inside the escrow contract EVM

Bitcoin’s proof-of-work is the oracle

0 intermediaries between the escrow and Bitcoin: no validators, federation, custodian, or relayer.

438 ms Signature to Bitcoin broadcast 30-day median · elsewhere: minutes to hours
0 Intermediaries between the escrow and Bitcoin no validators, federation, custodian, or relayer
1 Hop for your Bitcoin: solver’s wallet → your address real BTC · no vault · no wrapped asset
$18.4M Settled in 30 days · 168 BTC 4,812 orders · 0 user funds lost
Tier 1 · Core technology · why the path is structurally shorter

Three breakthroughs no incumbent can copy

Each one removes a category of machinery, not a step. The first is the primitive the other two depend on.

Breakthrough 1 · A Bitcoin node inside the settlement contract

The escrow verifies Bitcoin itself

The contract holding your funds runs a Bitcoin node, a full node, engineered for efficiency and accuracy, on the EVM. It follows Bitcoin’s chain, verifies proof of work, checks the transactions in each block, and handles reorgs on its own. Bitcoin’s proof-of-work is the oracle: there is no validator set, no federation, no multisig quorum, and no relayer network between the escrow and the truth. And because the node lives in the same contract that holds the funds, verification and release are one step, there is no bridge message between the thing that knows and the thing that pays.

Not needed a third network · observation consensus · pooled execution · outbound queue · key churn Time deleted the minutes a third network spends agreeing on what Bitcoin already proved Trust Bitcoin’s proof-of-work and the escrow contract, no new validator set to bribe, no signer quorum to go offline
Breakthrough 2 · Self-proving payments

The Bitcoin transaction is the settlement message

The solver pays from its own wallet straight to your address. A zero-value OP_RETURN output carries the order’s intent hash, so the node binds that payment to exactly one order the moment it is in a block. One hop, real BTC, no deposit address, no custody vault, no wrapped asset, no unwind. The solver bears the gas and the network fee.

Not needed a transfer to a vault · confirmation gate · signer ceremony · mint · exit to real BTC Time deleted the minutes to hours a bridge spends moving coins in, then out again Trust none added, the payment is proven by the node, not attested by anyone
Breakthrough 3 · Collateral replaces waiting for finality

Delivery at broadcast, guaranteed by a slashable bond

The solver posts collateral with its commit. If the payment lands, the node proves it and releases the escrow; if it doesn’t, the same node enforces the deadline and slash() returns your principal plus a share of the bond. Because the outcome is guaranteed either way, your Bitcoin is yours at broadcast. Block time leaves your critical path by economics enforced on-chain, not by trusting a custodian.

Not needed a confirmation gate on your path · a custodian · a trusted party of any kind Time deleted Bitcoin’s block interval, at whatever depth the order requires Trust posted collateral, enforced on-chain by the same node, no custodian, no insurance fund, no promise
Tier 2 · Market mechanism · why the number keeps falling

Speed is a market outcome, not a tuned constant

Maxy has no matching engine, no batch, and no quote loop. It pays solvers to be first, lets anyone compete, and lets the winner be decided by arithmetic.

Latency is monetized

First qualified fill wins, and the commit is bonded

Only the first solver to commit and post collateral earns the fill. There is no assignment step and nothing to wait to be matched with, speed is literally the product solvers sell. The 438 ms is an emergent market number, and it improves with competition.

Pricing on the intent

A descending price schedule rides on your signature

A firm limit or a descending schedule, flat within each step, no expiry, is part of the signed order. Solvers accept by arithmetic, so there are no RFQ round-trips, no re-quotes, and no oracle on the fast path. Because the first fill wins, competition fills the order at the earliest, best step: spread and time-to-fill compress together.

Permissionless supply

Anyone can join the race

One command puts a new solver in competition, and every new solver pushes the median down. Liquidity is the solvers’ own, there is no pooled liquidity to bootstrap and no wrapped asset to issue, so the flywheel behind the headline number is competition, not a roadmap.

Tier 3 · Path minimization · the remaining machinery, deleted

What’s left is a signature, a commit, and a payment

Once the escrow can see Bitcoin and the outcome is collateralized, every other mechanism the industry built to work around those two gaps becomes unnecessary.

One signature, gasless

No HTLC, no approve, no redeem, no secret

One permit-style signature is your only action; the escrow pulls exactly what you signed and the solver bears the gas. There is no approve-then-swap, no redeem transaction, and no secret to guard, so no HTLC at all, with its fund → confirm → reveal → redeem → confirm sequence and its timeout.

Time deleted hours, two transactions, two confirmation waits, and a redeem window
Failure has a clock

Deterministic, on-chain failure handling

A solver that commits and vanishes is slashed inside the contract, on a deadline you signed, and the bond makes you whole from your principal up. No dependency on a third network’s liveness, no ceremony to repeat, no timelock refund window, no support queue.

Time deleted every failure mode that resolves off-chain, or not at all
Risk-scaled finality

Depth scales with size, computed by the node

Confirmation depth is a security parameter, not a fixed gate everyone waits behind. The node sets it per order, larger sizes require more, and tracks reorgs against the heaviest chain, so the escrow’s release is exactly as conservative as the order needs and never more.

Time deleted the one-size-fits-all confirmation threshold
30-day median · elsewhere: minutes to hours

438 ms isn’t an optimization.

It’s what’s left when the contract can see Bitcoin.

Why no incumbent can copy it

Every other design exists to work around one fact: the contract holding the money can’t see Bitcoin. The machinery built around that gap is their product, and their time.

The same order · four architectures

Only one lane is a stopwatch

Maxy’s 438 ms is a dated median. The other lanes are still inside the machinery built to work around not seeing Bitcoin.

The structural gap
In the other designs, the wait is built in.

A pool chain waits for consensus, a bridge for its signers, an HTLC for confirmations. Maxy’s path has no stage like that.

Mechanisms, not adjectives

The structural gap

Every cell verifiable against public docs, and every figure on this page dated on the status page.

Measured, dated, and open to inspection

Every figure on this page is a 30-day measurement linked from the live status page, every settled order links to its Bitcoin transaction, and the node is documented in public.

The clock is public

Speed here is a measurement anyone can repeat, and a number solvers compete on in the open, not a claim on a slide.

every figure dated · explorer-linked

Time a live order

4,812 orders settled in the last 30 days, every one linked to its Bitcoin transaction. Pick one and time it against the block explorer.

Read the node

The primitive behind everything on this page, a Bitcoin node engineered for efficiency and accuracy, running inside the escrow, is documented and public. Diligence starts there.

And because solvers only earn by being first at the best step of a descending schedule, the 438 ms keeps falling with competition rather than with a roadmap.

Bitcoin in milliseconds, because the escrow runs a Bitcoin node.

Because the contract can see Bitcoin, the payment can be an ordinary transaction to your address, a bond can guarantee delivery before confirmations, and one signature can settle the order. The third networks, vaults, and HTLCs the industry built to work around not seeing Bitcoin were never needed here.

3 steps · 0 intermediaries · 438 ms median