Permanently deletes an existing Vault object from the ledger, removes all associated ledger entries, and frees up the reserve requirement for the Vault Owner.
Only the Vault Owner can initiate this transaction, and the vault must be completely empty before deletion.
SingleAssetVault amendmentが必要です。 Loading...
LendingProtocolV1_1 amendmentが必要です。 Loading...
{
"TransactionType": "VaultDelete",
"Account": "ra5nK24KXen9AHvsdFTKHSANinZseWnPcX",
"Fee": "12",
"Flags": 0,
"LastLedgerSequence": 7108682,
"Sequence": 8,
"VaultID": "77D6234D074E505024D39C04C3F262997B773719AB29ACFA83119E4210328776"
}In addition to the common fields, VaultDelete transactions use the following fields:
| Field Name | JSON Type | Internal Type | Required? | Description |
|---|---|---|---|---|
MemoData | String | Blob | No | A data field to record why the vault was deleted, as hexadecimal. Limited to 256 bytes. LendingProtocolV1_1 amendmentが必要です。 Loading... |
VaultID | String | Hash256 | Yes | The unique identifier of the vault that needs to be deleted. |
There are no flags defined for VaultDelete transactions.
Besides errors that can occur for all transactions, VaultCreate transactions can result in the following transaction result codes:
| Error Code | Description |
|---|---|
tecNO_ENTRY | The Vault object with the provided VaultID does not exist on the ledger. |
tecNO_PERMISSION | The account submitting the transaction doesn't own the vault. |
tecHAS_OBLIGATIONS | The vault still holds assets or has outstanding shares, so it can't be deleted. |
temDISABLED | MemoData is present and the LendingProtocolV1_1 amendment isn't enabled. |
temMALFORMED | VaultID is zero.MemoData is present but empty, or longer than 256 bytes. LendingProtocolV1_1 amendmentが必要です。 Loading... |