Iron Finance Denies Rug Pull After Token Collapse


Key Takeaways

  • Iron Finance’s TITAN, which backs the algorithmic stablecoin IRON, collapsed after a massive selloff last night.
  • The price crash likely occurred because of IRON’s pegging mechanism depending on arbitrage.
  • The team has denied allegations of a rug pull, and will let IRON holders redeem the stablecoin for USDC.
This news was brought to you by ANKR, our preferred DeFi Partner.

Iron Finance’s governance token completely collapsed last night. According to the team, the project’s TITAN token suffered from a bank run after users were urged to remove liquidity from all pools.
Iron Finance Under Fire
Iron Finance, a DeFi project that issues a partially collateralized algorithmic stablecoin called IRON, has suffered a major incident.
TITAN, the governance token that backed IRON, collapsed last night due to a massive selloff. The token price crashed from around $60 to $0.00000006, as per data from CoinGecko. Meanwhile, the IRON stablecoin is trading at around $0.70 (stablecoins like IRON are meant to stay pegged to an asset—in this case, that’s the dollar).
The stablecoin was backed by USDC and TITAN in portions of 75% and 25%. Iron Finance launched on Polygon less than a month ago and quickly attracted over $2 billion in liquidity.
It is still not clear what was the reason behind a near-zero price collapse. Many have speculated that the crash could have been due to a “rug pull,” a situation where project founders make off with the users’ funds locked in smart contracts. However, the team denied these claims. On its website, it wrote:

“There is no hacks, no exploits or rug-pullings.”

To incentivize USDC staking in its liquidity pools, the project had offered yields up to 10,000% APY in TITAN tokens. The yield caught the attention of Shark Tank entrepreneur-turned-DeFi enthusiast Mark Cuban, who revealed that he was farming TITAN in a blog post earlier this week. Cuban tweeted that he “got hit like everyone else” last night.
The Likely Cause
TITAN may have crashed due to the stablecoin pegging mechanism. When the price started declining, IRON lost its dollar peg. Like other algorithmic stablecoins, the price should have restored once the pegging mechanisms come into play. But, the situation spiraled out of control.
According to the protocol’s pegging system, whenever the price of the IRON token is less than one U.S. Dollar (USD), anyone can buy the token and redeem it for $1 worth of value, divided into $0.75 of USDC and $0.25 of TITAN.
While this arbitrage mechanism was meant to be the peg for IRON, it was likely the cause of the crash. Yesterday, when the stablecoin was trading under a dollar, arbitrageurs bought and redeemed IRON at a cheaper price. The TITAN tokens were continuously sold on the open market, causing the price collapse.

Sorare

Furthermore, as people tried to redeem more IRON, panic spread, and this lead to a bank run, meaning everyone tried to redeem their IRON tokens at the same time. The sell pressure continued until TITAN’s price fell to almost zero.
This issue was pointed out by Millenial Finance’s lead developer, z80Ðev, a few days ago. They wrote:

Now what worries me is the opposite scenario. When $IRON < $1, the opposite arbitrage opens up. It becomes profitable to buy $IRON for < $1, and then redeem it for ~0.72 USDC and the rest in $TITAN. Someone doing this likely will market sell that $TITAN for USDC

4/n

— z80Ðev (@z80dev) June 14, 2021

Iron Finance said that it would publish a post-mortem after it has a better understanding of what caused the sudden collapse. Regardless of TITAN going to zero, Iron Finance’s vaults still contain more than $200 million worth of USDC. The team has promised it would allow IRON holders to redeem $0.748 worth of USDC per token from this evening.

This news was brought to you by ANKR, our preferred DeFi Partner.
This news was brought to you by ANKR, our preferred DeFi Partner.

Reviews

  • Total Score 0%
User rating: 0.00% ( 0
votes )



Leave a Reply

Your email address will not be published. Required fields are marked *