Escrow Smart Contract
The client and the provider lock funds in a smart contract. The provider gets paid once the work is done and both sides agree.
How it works
Five steps to a contract
Create a smart contract with a simple wizard.
Create a smart contract with a simple wizard.
- Step 1Your role in the contractChoose your role in the contract. There are only two roles: client and provider. There is no third-party arbitration.9:41LTE
Your role in the contract
- Step 2Choose a currencyChoose the contract currency. GRAM, TON's native currency, suits quick and small deals, since it's fairly volatile. USDT is a more stable currency for large and long-term deals.9:41LTE
Choose a currency
- Step 3Contract amountEnter the contract amount in the chosen currency. This amount will be paid to the provider once the work is done.9:41LTE
Contract amount
The contract amount is the price of the work. It is paid by the client.
From 10% to 90%. Default: 30%.
0,4% of the amount, but no more than 15 GRAM.
- Step 4Wallet addressesPaste the wallet addresses. These wallets will later be used to deposit and withdraw funds.9:41LTE
Wallet addresses
- Step 5Review the contractReview the contract details before deployment.9:41LTE
Review the contract
Your role in the contract
After creation
Contract card
You are the client, the currency is USDT. Six snapshots of the same card as in the real dashboard, with every action available at each step.
Just created
Balances are zero. You can deposit the deal amount, deposit it together with an extra of up to 30%, or delete the contract while nobody has put anything in.
Funded, waiting
The deal amount is already in the contract, but the provider deposit isn't yet. Until the status is “Active”, you can withdraw your funds. You can still add the extra deposit of up to 30%.
Provider deposited
Both agreed amounts are in, so the contract is active. The funds are locked, and USDT can't be withdrawn. You can accept the work, propose a different share, or add the extra deposit (an additional deposit from the client).
Added a 20% deposit
There's +200 USDT on top of the deal amount. Another 100 USDT fits under the 30% cap. Withdrawals remain closed: an active contract holds the contract amount plus the extra.
Proposed 80% to the provider.
The provider will receive 800 USDT if they agree. The “Accept work” button has disappeared; it will only come back if you set 100%. The proposal can be replaced, and the extra deposit can be topped up.
Provider agreed
The contract is completed: 800 USDT went to the provider and 4 USDT to the service as royalty. You have 400 USDT left, which you can withdraw.
Q&A
Frequently asked questions
Where is the third party?
There isn't one. The provider risks their deposit, so it's in their interest to see the work through.
By default, the provider deposit is 30% of the deal amount. It might seem the provider has the upper hand: they risk 30%, and you risk 100%. But what matters is money, not percentages. Those 30% are the provider's own money, and losing it may hurt them just as much as losing your 100% would hurt you. Nobody gives up their own money for nothing.
Another risk: the client receives the work and may not pay. There are two options here. The first is to offer to settle up early, when the work is almost done. The second is to ask the client to put in an extra deposit of up to 30% on top of the amount. Once the contract is completed, the client gets that deposit back, so they have a reason to close the deal.
Why should I trust you?
You don't have to. The smart contract is public. Your contract's address is a hash of its initial data and code. If the code were swapped, the address would be different.
You can open the code and inspect it (for example, in Tonviewer). The only thing is, you need to understand the code — that's the main problem. In return, it's 100% proof. You can also hand the code to an AI model. Below is the contract code, explained as simply as possible.
ContractUSDT
This is the list of imports: constants and helper functions.
A brief description of the contract.
The list of actions available on the contract.
A helper function that checks whether the contract is active. Once everyone has deposited their amounts, the contract becomes active, and funds can no longer simply be withdrawn.
A function for change. Each message carries a little GRAM to pay for processing the transaction. This function returns whatever is left over.
Calculates the jetton wallet address. It depends on the contract address.
If a transfer fails, the money comes back and the contract corrects its records of who holds how much.
If the message body is empty, do nothing.
Next come the variable declarations.
USDT top-up: accepts transfers and records how much USDT each party has.
Changes the payout percentage. If only half the work is done, you can propose 50%. If the provider agrees, the contract is fulfilled. If not, keep negotiating.
If the provider agrees, the contract pays out their share plus their deposit, and the rest goes back to you. At 0%, the whole deal is cancelled and everyone gets their money back. In that case, the 0.4% service fee is not charged.
The biggest block: it handles refunds.
Error mode. If a wallet is lost or funds bypassed the accounting, one party can hand control over to the other. Strictly speaking, funds bypassing the accounting is impossible unless someone does it on purpose, but the option stays just in case. Forgetting or losing a wallet, on the other hand, is quite possible.
ErrRefund is an emergency withdrawal of jettons that arrived without a notification and weren't recorded. It also helps when a wallet is lost (or, more precisely, its password is lost).
Burn destroys the contract so that an empty shell doesn't linger on the network. It can be burned by whoever created it (the client or the provider) or by the admin, and only when both the client's and the provider's balances are zero.
Verified source of the three contracts. The code hash matches what is on the chain. Each link opens the source on TON Verifier.
ContractMinterContractUSDTContractTON