Skip to content

Latest commit

 

History

History
46 lines (27 loc) · 1.89 KB

secured-assets.md

File metadata and controls

46 lines (27 loc) · 1.89 KB
description
Asset Type to Integrate into the App Layer

Secured Assets

Secure Assets allow L1 tokens to be deposited to THORChain, creating a new native asset, which can be transferred between accounts, over IBC and integrated with CosmWasm smart contracts using standard Cosmos SDK messages. They also replace Trade Assets.

{% hint style="info" %} See the Dev Docs for a more detailed description.
Also see Technology for generic Cosmos information. What notation will they have? {% endhint %}

Asset Notation

The delimiter for Secured Assets is a dash '-'.
E.g. ETH.ETH is L1. ETH-ETH will be a secured asset.

While ETH.tc is pictured, that may change to ETH-ETH.

How will Secured Assets Move Between Base and App Layer?

Secured assets are x/bank tokens on the App Layer (Rujira) representing claim to the native asset on base layer (THORChain).

The native asset is secured to and from the app layer with the following flow:

Mint and Burn Secured Assets

Example shows the mint and burn process for BTC

Swapping Secured Assets

Examples below explain how a user:

  1. Swap a Secured Asset (SA)—BTC—to another Secured Asset—ETH
  2. Swap a Secured Asset—BTC—to a base asset—ETH

  1. Secured Asset Swapping, swapping the L1 under the hood

Find more information about Secured Assets in the Rujira Docs or in the Dev Docs.