Pendulum Docs
  • Learn
    • Welcome to Pendulum
    • Our Journey
    • Litepaper
    • Tokenomics
      • Token Utility
      • Unlocking Vesting Tokens
    • Roadmap
    • Grants Received
  • Build
    • Introduction
    • Network Parameters
    • Build Environment
      • Local relay chain setup
      • Local Pendulum chain setup
      • Pre-Configured Pendulum
        • Install
        • Configure
        • Launch
        • Sub-commands
          • export-genesis
          • generate-specs
          • generate-docker
      • Foucoco (testnet)
      • Troubleshooting
    • Developing dApps
      • ink!
    • Node Operators
      • Collators
        • Collators List
        • Set up Collator
          • Hardware Requirements
          • Ubuntu Installation
          • Docker Installation
          • Keys Management
          • Become a Collator
          • Node upgrade instructions
      • Spacewalk Vaults
    • Integrations
      • Indexers
      • Oracles
      • Wallets
    • Spacewalk (Stellar bridge)
      • User
        • Spacewalk Step-by-step guide
          • Asset Redemption Post-Vault Liquidation
      • Operating a Vault client
        • Getting Started
          • Testing it locally
            • Building pallets and testchain
            • Creating test accounts
            • Testing the vault client
        • Usage
          • Issue assets
          • Redeem assets
        • Collateral and Liquidation
          • Recovering a vault after liquidation
        • Fees, Costs and Incentives
        • Vault rewards
          • Claiming Vault rewards
        • Troubleshooting
          • Generating metadata
    • Forex AMM
      • Architecture
      • Swap User Guide
      • LP User Guide
        • Swap Pools
        • Backstop Pool
        • Cross Interaction
      • Coverage Ratio and Slippage
      • Deployment Parameters
      • Security and Audits
    • Technical FAQ
    • Status reports
      • 22-10-11 Foucoco stopped after runtime upgrade
  • Community
    • Crowdloan
      • Sign T&Cs for rewards
    • Staking
      • Choosing a Collator to Stake with for $PEN Staking Rewards
      • Delegation
      • Rewards
      • Further Operations on Delegators
    • Testnet Faucet
    • On chain identity guide
    • Cross-chain transfer KSM
    • Using Ledger
    • Governance
    • PEN and AMPE Wallets
    • Add PEN/DOT Liquidity to StellaSwap
    • Pendulum Grant Program
    • Amplitude Grants Program
    • Ambassador Program
    • Ambassador Bounties
  • Resources
    • FAQ
    • Links
      • Website
      • Github
      • Social Media
    • Audits
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
  1. Build
  2. Spacewalk (Stellar bridge)
  3. Operating a Vault client
  4. Collateral and Liquidation

Recovering a vault after liquidation

PreviousCollateral and LiquidationNextFees, Costs and Incentives

Last updated 8 months ago

Was this helpful?

If a vault you operate gets liquidated, the collateral is confiscated. To make the vault operational again, you have to deposit new collateral and register it again. When a vault is liquidated, Spacewalk considers the locked tokens on Stellar to be lost. This means you can use the tokens that users locked in the vault’s Stellar account to retrieve new collateral. For this, you can either

  1. Trade the tokens for the collateral asset on a CEX, or

  2. If other vaults for the same wrapped asset are available, bridge the tokens available on the vault’s Stellar account to Pendulum using the other vaults and perform liquidation redeems against the liquidation vault to get back parts of the confiscated collateral.

In order to change the vault’s status from Liquidated back to Active you need to call the vaultRegistry::recoverVaultId() extrinsic. A prerequisite for this is that the vault does not have any pending issue or redeem requests. Otherwise, it first needs to fulfill those before it can be ‘recovered’. You can check for pending bridge requests with the vaultRegistry::vaults() storage query. The field toBeRedeemedTokens needs to be at 0.

If the vaultRegistry::recoverVaultId() extrinsic executes successfully, the status of your vault should change back to Active: true meaning that it’s active and willing to accept issue requests again.

Afterward, you can deposit new collateral as usual by calling the vaultRegistry::depositCollateral() extrinsic.