Youtube Video

Playing the video that you've selected below in an iframe

Neptune Mutual to Close Cover Marketplaces

5 min read
Neptune Mutual Final

After much deliberation and careful thought Neptune Mutual decided to close the cover marketplaces.

After much deliberation and careful thought Neptune Mutual decided to close the cover marketplaces. Below the reasons for the decision as well as what it means for the community.

The marketplaces will be closed using an emergency withdrawal process whereby the liquidity provided to cover pools by LPs will be returned to the wallet addresses from which the liquidity was supplied. In addition to protecting cover pool LPs, there will also be refunds to all cover policy purchasers with an existing and valid policy who have paid over 10 USD in policy fees in one transaction.

For veNPM holders, please fill out this form to receive a refund for your veNPM to NPM conversion penalty.

From the end of June there will no longer be NPM emission incentives for LPs i.e. Epoch 3 of the liquidity gauge emissions will be canceled.

Unused funds raised from financial backers will be returned to those backers; this includes DEX liquidity that has now been removed from SushiSwap and Uniswap. A small amount of liquidity on SushiSwap Arbitrum has been left to enable a minimum amount of NPM trading.

The protocol will be open sourced, and become a true public good. Enabling the community to fork the code developed by the Neptune Mutual team such that others might use the existing resources to further our mission to make the blockchain space better protected against smart contracts and other risks.

There are numerous factors that have led to this difficult decision, some of which are external factors which are uncontrollable or unforeseeable. A few factors summarized below:

CEX Listing#

“Given Neptune Mutual’s Tier 1 backers, why have you not listed on a top CEX?”

This is perhaps one of the most frequently asked questions. In short, the answer is that for a variety of reasons Neptune Mutual was not able to achieve the diverse set of performance metrics (community size and engagement, marketplace user activity, DEX 24 hour trading volume, TVL growth etc.) required to list on top tier CEX. The CEXs that are prepared to list NPM token do not have the depth of liquidity or breadth of user-base to offer good prospects for NPM tokenholders.

Growth Performance#

The above point invariably leads to the question

“Why has Neptune Mutual not achieved strong growth?”

It is tempting to take a shortcut to answer this question by pointing a finger at one specific factor, but the reality is that there are many contributing factors. A few summarized below:

The DeFiInsurance Narrative#

Since the outset of engaging with the community we have endeavored to highlight the need for DeFiInsurance; Neptune Mutual built a comprehensive dataset of on-chain hacks available, anywhere, and each week we highlight the many millions of dollars that are stolen as a result of smart contract hacks. Despite this, we have consistently been confronted by projects unwilling to spin up cover pools in our marketplace because of the sentiment that audits of their code are sufficient to persuade their community that their protocol is safe. Less than 0.3% of all digital assets are protected with some form of DeFiInsurance, and yet despite all the media reports of hacks, the conference discussions about the importance of governance or CEX proof-of-reserves, it continues to be the case that it is extremely difficult to get media attention to focus on the need for a fast and efficient means of mitigating smart contract risk.

A variety of approaches have been taken by different DeFiInsurance protocols to address this, from attending multiple conferences throughout the year and significant marketing spend, to the leaner approach that Neptune Mutual took (in part as a result of the bear market in 2023). What can be said is that no DeFiInsurance protocol has managed to achieve significant growth over the last 18 months, sadly the overall TVL of the sector has shrunk a lot.

Continue to Invest in Growth, or Refund?#

For all the reasons above, at this moment the best course of action is no longer to double-down on investing in growth, but rather to refund unused capital and close the marketplaces.

The consequences are very tough for the Neptune Mutual team who have spent the past 3 years of their time on the mission to facilitate  safer environments within DeFi.  The team has delivered products according to the roadmap and the fact that the protocol was never hacked, despite attempts being made on the darkweb, is testament to the expertise, passion and absolute focus on security.  The team survived the FTX and UST crisis unscathed, and believed that the continued growth in hacks would lead to growth in the demand for a good solution to mitigate these risks, but sadly, as can be seen right across the DeFiInsurance category, this is not yet in sight. So we would like to thank the team for all the dedication, skill and passion invested into the Neptune Mutual project since the outset.

What's Next?#

The team will open source the protocol, including blockchain indexing protocol (subgraph alternative), frontend, middleware, database, and backend code, to make it a true public good. This will allow anyone to fork the code and create covers by defining parameters and premium ranges, potentially leading to innovative covers and organic usage.

The Discord channel will be closed to reduce the risk of phishing and other types of cyber attack, any questions / queries will be responded to in the Telegram channel.

We want to take this final opportunity to thank you all for your support.

Disclaimer:#

Neptune Mutual will contact only its financial backers, with whom a signed agreement exists, in relation to next steps (i.e. holding NPM tokens does not qualify you for any form of refund). Contact will be made only from a neptunemutual.com domain email address so please check the source of any email you may receive very carefully. Please ignore any messages from any other email or social media accounts in relation to token/cash refunds.

By

How was Multichain Exploited?

2 min read
Exploit Analysis

Learn how an attacker exploited the Multichain's AnyswapV4Router contract to take away 87 ETH.

TL;DR#

On February 15, 2023, the AnyswapV4Router contract of Multichain encountered a front-running attack, during which the attacker made a profit of about 87 ETH, worth approximately $130,000.  

Introduction to Multichain#

Multichain is an infrastructure designed to support arbitrary cross-chain interactions.

Vulnerability Assessment#

The vulnerability occurred because the attacker used a MEV contract to front-run and invoke a function of the AnySwapV4Router contract to sign and approve the transfer.

Steps#

Step 1:

We attempted to analyze the attack transaction executed by the exploiter.

Step 2:

The attacker used the MEV contract to front-run and call the anySwapOutUnderlyingWithPermit function of the AnyswapV4Router contract in order to sign and approve the transfer.

Step 3:

Despite the fact that the function makes use of the token's permit signature verification, the stolen WETH lacked a related signature verification function and only triggers a fallback in the deposit function.

Step 4:

Thus, due to the lack of signature verification, the attacker is able to transfer the $WETH approved to the victim contract, through the from address parameter directly to the attack contract using the safeTransferFrom function.



Aftermath#

The team stated that this was an old vulnerability that was reported in January 2022.

In their previous postmortem report, they explicitly stated that the risk originating from this exploit still remained for users who had not yet revoked approvals for the affected router contracts.

They further mentioned that the users themselves would have to revoke the approvals.

Solution#

Between January 10, 2022 and February 19, 2022, the team reported that more than 61% of all affected users had revoked access to the contract containing the underlying vulnerability.

The liquidity pool's vulnerability was quickly fixed after it was reported, as the team upgraded the affected tokens' liquidity to new contracts. The risk remained, however, for users who had not yet revoked approvals for the affected router contracts.

We may not have prevented the occurrence of this hack, however the impact or aftermath of this attack could have been significantly reduced if the team associated with Multichain Protocol had set up a dedicated cover pool in the Neptune Mutual marketplace. We offer coverage to users who have suffered a loss of funds or digital assets occurring as a result of smart contract vulnerabilities owing to our parametric policies.

Users who purchase the available parametric cover policies do not need to provide loss evidence in order to receive payouts. Payouts can be claimed as soon as an incident is resolved through the incident resolution system. At the moment, our marketplace is available on two popular blockchain networks, Ethereum, and Arbitrum. 

Neptune Mutual's security team would also have evaluated the platform for DNS and web-based security, frontend and backend security, intrusion detection and prevention, and other security considerations.

Reference Source BlockSec

By

Tags

Exploit Analysis MEV Bot Multichain Front Running Attack Decentralized Insurance Parametric Insurance

Related Posts

More Related Posts

Analysis of the Curio Exploit

Learn how Curio was exploited, which resulted in a loss of approximately $16 million.

Exploit Analysis

Understanding the UwU Lend Exploit

Learn how UwU Lend was exploited, which resulted in a loss of assets worth $23 million.

Exploit Analysis

How Was Steam Swap Exploited?

Learn how Steam Swap was exploited, resulting in a loss of assets worth approximately $105,000.

Exploit Analysis