Your AI agent just agreed to a trade that needs backing. A forward it has to deliver on in 24 hours. A loan it has to repay. A leg in a multi-step swap that only completes if every other leg does. Before any of that clears, the agent has to post collateral, and the deepest collateral asset in crypto is Bitcoin.
So it goes to post BTC. And immediately it hits the oldest problem in cross-chain: Bitcoin the chain cannot run the contract logic a collateralized position needs. No expressive contracts, no objects, no state machine watching the position over time. The collateral has to be usable on a chain that can reason about it, while the BTC itself lives on a chain that cannot.
This post is about the wrong way to solve that, the right way, and what it takes for an agent to do it without a human in the loop.
The easy path quietly re-custodies your collateral
The standard fix is to wrap. Hand the real Bitcoin to a custodian, a federation, or a bridge contract, and receive a token on the destination chain. Now the agent can use that token as collateral anywhere that chain's contracts run.
Look at what just happened. The agent removed the custodian from the trade, then invited one straight back in at the collateral. The token it now holds is a claim on someone else's honesty and solvency. If the entity holding the real coins is compromised, drained, frozen, or simply wrong, the collateral backing the agent's obligation evaporates, and the agent has no good way to audit any of it in real time.
For a human treasurer, that is a known, priced risk. For an autonomous agent, it is worse: the agent cannot tell the difference between collateral it controls and collateral that only looks like it controls. A settlement layer that is trustless at the moment of the trade but custodial at the moment of the collateral is not trustless. It has just moved the trust somewhere the agent stopped looking.
A vault that never moves the coins
A BTC Collateral Vault takes the opposite trade. The Bitcoin never leaves Bitcoin, and it is never represented by a minted token. It stays as native BTC, locked in a script on the Bitcoin chain. What crosses to the settlement chain is not the asset. It is one piece of information: the hash of a secret.
If you have seen a hash-time-locked contract (HTLC) before, this is the same machine, pointed at a new job.
-
Hashlock. The BTC is locked in a Bitcoin script that will release only to whoever can present the preimage of a hash
H = SHA-256(secret). Nobody can move the coins early, because nobody but the party who generated the secret knows it. - Timelock. If the obligation is never settled, a timelock path lets the agent reclaim its own BTC after a deadline. No keeper, no counterparty cooperation, no support ticket. The refund is a property of the script, not a promise from a company.
- The cross-chain link. The settlement-chain side of the deal is bound to the same hash. Claiming the settlement leg reveals the secret on-chain; that revealed secret is exactly what unlocks the BTC. One preimage settles both sides, or neither side moves.
The collateral is real Bitcoin the whole time. The agent's keys never leave the agent. And the integrity of the position no longer depends on auditing a custodian, because there isn't one.
What the agent actually does
From the agent's point of view, this is a small number of deterministic steps, which is exactly what you want when there is no human to catch a mistake.
- Generate a secret and its hash. Keep the secret private.
- Lock native BTC into the vault script on Bitcoin, keyed to that hash and a timelock it chooses.
- Publish the hash and the vault reference to the settlement-chain contract holding the counter-obligation.
- On settlement, the claim reveals the preimage, which the agent (or the counterparty, depending on the flow) uses to unlock the BTC. If settlement never happens, the timelock refunds the agent.
There is no step where the agent has to trust a wrapper to be solvent, a bridge to stay unhacked, or a federation to stay honest. The only things it trusts are Bitcoin's script rules and the settlement chain's contract, both of which it can verify itself.
We expose this through a Model Context Protocol server: a 6-tool MCP an agent reasoning over an LLM can call directly to quote, lock, settle, and refund, so the vault flow is a set of tool calls rather than a bespoke integration for every model.
The honest status line
I keep chain claims precise, because in this domain an overclaim is a lie the agent inherits.
- Ethereum mainnet: the atomic settlement leg is live end to end today.
- Sui: contracts are deployed and CLI-tested, not mainnet-live.
- Bitcoin: the collateral-vault mechanism is validated on signet. Mainnet is pending, not shipped.
- Roadmap: Base, Arbitrum, Solana, TON.
So the BTC Collateral Vault is a validated design on signet with a live settlement counterpart on Ethereum, not a Bitcoin-mainnet product I am pretending exists. If you build on it today, that is the surface you are building on.
Why this is the layer worth getting right
This week the agent economy took a real step: agent payments consolidated under a single standard as x402 moved to a foundation with dozens of members behind it. That is genuine, and it matters. But a payment rail answers one question, "how does an agent pay," and it answers it in one token, on one chain.
Collateral is a different question. It is not "how do I pay you" but "how do I back a promise I have not yet kept, in the best collateral asset there is, across chains, without handing it to anyone." The moment an agent posts something to back an obligation, the custodian question comes back, and most of the stack answers it by quietly re-custodying. A vault that keeps the BTC native and moves only a hash is how you answer it without blinking.
If your agent could post native BTC as collateral without wrapping it, what is the first obligation you would have it back: a forward, a loan, or a leg in a multi-step trade?
Docs and the 6-tool MCP: https://hashlock.markets/docs?utm_source=devto&utm_medium=article&utm_campaign=2026-07-17-btc-collateral-vaults
The academic grounding for the settlement model, if you want the formal version: https://papers.ssrn.com/sol3/papers.cfm?abstract_id=6712722
Top comments (0)