# Destroy asset

If asset represents a real world object or something else that can be destroyed there also has to be an option to destroy the digital representation. In this guide we will should you how do destroy an existing asset.

# Prerequisites

In this guide, we will assume you have gone through the Asset ledger deployment guide and have deployed an asset ledger and that you have gone trough Issue asset guide and created asset. You will also need a MetaMask/Bitski account with some credits.

WARNING

Asset ledger must have DESTROY_ASSET capability.

# Usage overview

We begin by importing the client modules.

import { ActionDestroyAsset, ActionKind, Client, Priority } from "@0xcert/client";

Before we can start destroying assets we must initialize our client first.

const client = new Client({
  provider,
  apiUrl: 'https://api-rinkeby.0xcert.org',
});
await client.init();

WARNING

For successful client initialization you need connected 0xcert framework provider instance. See Providers chapter for detailed instructions. Your provider must be connected to Rinkeby Ethereum test network.

Once client is initialized, we define our destroy asset action.

const actionDestroyAsset: ActionDestroyAsset = {
  kind: ActionKind.DESTROY_ASSET,
  assetLedgerId: ledger.id,
  senderId: provider.accountId,
  id: asset.id,
};

As assetLedgerId we must provide the ID of our newly deployed asset ledger from guide Asset ledger deployment or any other deployed ledger. We specify which issued asset we want to destroy by setting id to the ID of the asset. We can use asset we created in guide Issue asset or any other created asset that we own.

WARNING

Asset with the provided ID must exists on the provided asset ledger.

As senderId we set provider.accountId, which means that we will be destroying our asset.

TIP

Account address specified as senderId can only destroy asset if they are the asset's owner.

After we defined our destroy asset action, it's time to define our order which will perform the defined action.

const order = {
  signersIds: [
    provider.accountId
  ],
  actions: [
    actionDestroyAsset,
  ],
  wildcardSigner: false,
  automatedPerform: true,
  payerId: provider.accountId,
};

Order must be signed by all of the accounts specified in signersIds array. In our case, we are destroying our asset, so we are the only signer of the order. We add our defined destroy asset action in actions array. There can be multiple different actions present in one order and they will be atomically performed. If wildcardSigner is set to true order can be signed by any account. In our case we need only our signature for the order to be successfully performed, so we set wildcardSigner to false. We want our order to be performed as soon as it can be, so we enable automated performance of the order by setting automatedPerform to true. Order will be automatically performed after all of the requirements of the order are fulfilled. If automatedPerform was set to false we would need to call performOrder(orderRef) function after the order creation. As payerId we set provider.accountId, so we will be paying for the execution of the order. To learn more about different scenarios check out the Additional scenarios section.

WARNING

If payer is not specified wildcardSigner field must be set to true and order's payer will be set automatically. If payer is specified it must be listed as order signer in signersIds array.

After our actions order is defined we can finally create it.

const actionsOrder = await client.createOrder(order, Priority.HIGH).then((data) => data.data);

WARNING

Make sure you have enough credits to perform this action.

Since actions order performance might take some time, we can check the order's status by requesting its data.

const status = await client.getOrder(actionsOrder.ref).then((data) => data.data.status);

If the status of the action order equals to 7, we know that our order was performed successfully and our asset was destroyed. All queries about the destroyed asset will be invalid from now on.

TIP

You can also set up and receive webhooks. In this scenario you will receive webhooks when our order changes (updated or successful) or if it fails. You can learn more about webhooks in chapter Webhooks.