EscrowCreate

Set aside funds in an escrow that delivers them to a predetermined recipient when certain conditions are met. If the escrow has an expiration, the funds can also be returned to the sender after it expires. The conditions for release can include a specific maturity time, a hash-based cryptocondition, or a smart function.

(Updated by the TokenEscrow amendment. )

(Updated by the SmartEscrow amendment. )

{
    "Account": "rf1BiGeXwwQoi8Z2ueFYTEXSwuJYfV2Jpn",
    "TransactionType": "EscrowCreate",
    "Amount": "10000",
    "Destination": "rsA2LpzuawewSBQXkiju3YQTMzW13pAAdW",
    "CancelAfter": 533257958,
    "FinishAfter": 533171558,
    "Condition": "A0258020E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855810100",
    "DestinationTag": 23480,
    "SourceTag": 11747
}

Query example transaction

In addition to the common fields, EscrowCreate transactions use the following fields:

You must specify one of the following combinations of fields:

It is not possible to create a conditional or function-based escrow with no expiration, but you can specify an expiration that is very far in the future.

If an escrow has multiple criteria for release, including any combination of a time-based release, a crypto-condition, or a smart function, the escrow can only release funds to the recipient if all of the criteria are met. For example, you can make an escrow that can only be released if the smart function returns success and a crypto-condition is fulfilled, but you cannot make an escrow that can be released if the smart function or crypto-condition are satisfied.

If the escrow has a Bytecode field, it has a special transaction cost of 10 times the base fee plus an additional 5 drops per byte. The exact formula is:

(base_fee × 10) + (bytecode_size × 5)

• base_fee is the reference transaction cost, in drops of XRP.
• bytecode_size is the size of the Bytecode field, in bytes.

Besides errors that can occur for all transactions, EscrowCreate transactions can result in the following transaction result codes:

Error Code	Description
tecDIR_FULL	Either the sender or the destination owns too many objects in the ledger. This error is effectively impossible to receive if fixDirectoryLimit is enabled.
tecDST_TAG_NEEDED	The destination account requires destination tags but this transaction did not provide one.
tecFROZEN	For a trust line token escrow, the token is frozen: this includes the sender being individually frozen, the destination being deep frozen, or the token being globally frozen. (Requires the TokenEscrow amendment. )
tecINSUFFICIENT_FUNDS	For token escrows, the sender does not currently hold enough funds to pay for the escrow. (Note: XRP escrows return tecUNFUNDED for this case instead.) (Requires the TokenEscrow amendment. )
tecLOCKED	For an MPT escrow, the token is locked. (Requires the TokenEscrow amendment. )
tecNO_AUTH	For token escrows, the sender is not authorized to create this escrow. There are several cases that can cause this error, including: The sender does not have an MPToken entry to hold this MPT. The MPT issuance does not have the Can Transfer flag enabled. The MPT or trust line token requires authorization, but the sender is not authorized. The MPT is restricted to a permissioned domain, but the sender is not part of that domain. (Requires the TokenEscrow amendment. )
tecNO_DST	The specified destination account does not exist in the ledger.
tecNO_ISSUER	For a trust line token escrow, the issuer of the token (as specified in Amount) does not exist in the ledger. (Requires the TokenEscrow amendment. )
tecNO_LINE	For a trust line token escrow, the sender does not have a trust line for the specified token. (Requires the TokenEscrow amendment. )
tecNO_PERMISSION	The sender does not have permission to create this escrow. There are several cases that can cause this error, including: The escrow destination is a pseudo-account. For a trust line token escrow, the sender is the issuer of the token or they hold a negative balance of the token. For an MPT escrow, the sender is the issuer of the token. For a trust line token escrow, the issuer hasn't enabled the Allow Trust Line Locking flag. For a trust line token escrow, the issuer requires authorization but the sender is not authorized. For an MPT escrow, the MPT issuance does not have the Can Escrow flag enabled. A time specified in FinishAfter or CancelAfter is already in the past. The escrow is expired. (Updated by the TokenEscrow amendment. )
tecOBJECT_NOT_FOUND	For an MPT escrow, the MPT issuance does not exist or the sender does not hold the MPT; or, the MPT requires access to a permissioned domain but the domain does not exist in the ledger. (Requires the TokenEscrow amendment. )
tecPRECISION_LOSS	For a trust line token escrow, the amount of the escrow is too small relative to the sender's balance, which would cause it to be rounded to 0. (Requires the TokenEscrow amendment. )
tecUNFUNDED	For XRP escrows, the sender lacks sufficient spendable balance, which excludes XRP set aside for reserves. (Note: token escrows use tecINSUFFICIENT_FUNDS instead.)
temBAD_AMOUNT	The Amount is invalid. For example, it is negative; it is not XRP and the TokenEscrow is not enabled; or it is larger than the maximum possible MPT amount. (Updated by the TokenEscrow amendment. )
temBAD_CURRENCY	The Amount specifies an invalid currency, such as a trust line token with the currency code for XRP. (Requires the TokenEscrow amendment. )
temBAD_EXPIRATION	The was a problem with the expiration (CancelAfter) or finish time (FinishAfter). For example, the transaction did not specify a required field, or the expiration is before the finish time.
temINVALID_BYTECODE	The Bytecode field did not contain a valid smart function. (Requires the SmartEscrow amendment. )
temTEMP_DISABLED	Smart functions have been temporarily disabled by fee voting. (Requires the SmartEscrow amendment. )

• Escrow entry