Earnest Money Deposits in Crypto

An earnest money deposit in crypto is the buyer's deposit, locked in escrow while a property deal is still conditional. It is not the full purchase price, and it is not a gift to the seller. On DeFiEscrow it is an escrow with a funding deadline, an approval deadline, and a payout you chose on purpose. If you do not choose the payout on purpose, a timeout will send the deposit back to the buyer, which may or may not be what the purchase contract says.

This sits inside the broader real estate closing. The full price, if it is also paid in USDC or ETH, is often a second escrow created when you actually know the net numbers. Mixing "deposit" and "price" in one escrow with the wrong payout is how earnest money gets structurally forfeited or structurally refunded by accident.

What the deposit is for

The seller takes the property off the market, or treats it as spoken for, because the buyer has something at stake. Traditionally that something sits with a title company or a broker's escrow account. In this version it sits in the contract. The seller can see, on-chain, that the buyer's address deposited the amount the escrow required. The seller cannot withdraw it just because they can see it. Withdrawal of the seller's payout happens only after release, and release happens only after every participant has approved, or not at all if the deal ends in a refund.

That visibility is useful across borders and across weekends, when a wire confirmation is a PDF you are asked to trust. It is not, by itself, a legal tender of the deposit under your purchase contract. Your contract should say that funding this escrow, on this network, in this asset, counts as posting the earnest money. If it does not say that, you have a token transfer and a contract that do not point at each other.

Map the contingency to the approval deadline

Most earnest money is refundable for a while: inspection, financing, title review, sale of the buyer's current home. Those are off-chain conditions. The contract's version of the window is the approval deadline.

Set the funding deadline early enough that the deposit is in before the seller relies on it, and late enough that the buyer can move the asset to the right wallet and still have gas. Set the approval deadline at the end of the contingency period you negotiated, plus time for every required wallet to send an approval. The deadline rules are strict. You cannot extend them in place.

If the buyer's contingency fails and both sides agree the deposit comes home, they simply do not approve, and after the approval deadline anyone can terminate the escrow. The buyer withdraws the deposit. If you need the refund faster than the deadline, a party can raise a dispute and, if they are the raiser, remove it only when they mean to continue. A dispute is a poor substitute for a well-chosen deadline, because the automatic refund on a dispute waits 30 days. The cleaner design is an approval deadline that matches the contingency.

If the contingency passes and the buyer is moving to closing, do not treat the earnest-money escrow as the place the full price will magically grow. Create the closing escrow for the price, with the parties and nets you now know. What happens to the deposit itself should be written down: it is either refunded to the buyer through this escrow's timeout or release-back, or it is a credit you already modeled. The contract will not subtract the deposit from the price for you.

Forfeiture has to be the payout, not a hope

Some purchase contracts say the seller keeps the deposit if the buyer defaults after contingencies expire. A smart contract will not read that sentence and flip the payout. If the seller's address has a willReceive of zero, the seller never receives the deposit, no matter how clearly the PDF describes a forfeiture. If the buyer's deposit is matched by a payout to the seller, then release sends it to the seller, but only after approvals, including the buyer's. A buyer who is in default and refuses to approve will not be forced by the contract to complete the forfeiture. The approval deadline will refund them instead.

So a true forfeiture structure is not "we will figure it out." It is a design you accept up front: for example, the seller is the withdrawer, the buyer must approve to release, and you understand that a refusing buyer gets the deadline refund rather than a forced loss. If your deal needs a third party who can award the deposit to the seller without the buyer's signature, this contract is not that third party. Disputes do not split or forfeit funds. A licensed escrow that follows the purchase contract might be. Say which one you are using.

Size, asset, and the parties

Earnest money is often a small percentage of the price. On a USDC escrow the protocol fee is 1% of the amount in the app's calculation, with no ETH minimum. On a small ETH deposit, the 0.05 ETH minimum can be large relative to the deposit. A 0.2 ETH earnest deposit does not have a 0.002 ETH fee. The floor is 0.05 ETH. For a modest deposit, USDC or USDT is usually the cleaner fee shape, and it also tracks the dollar figure in the purchase contract. Choosing the asset covers the rest of that choice.

Parties stay few. Buyer deposits. Seller is the withdrawer if the happy path pays the seller, or the structure is a refund-to-buyer payout if the happy path of this particular escrow is "deposit comes home at the end of diligence and the price is a later escrow." An agent who must consent can be an acknowledger. Do not add the agent's wallet unless you want their approval to be mandatory.

Write the escrow id, the asset, the amount, both deadlines, and both addresses into the purchase contract or an addendum. Earnest money works when those fields and the legal contingency are the same story. It fails when the PDF says the seller keeps the money and the contract says a timeout pays the buyer.