
Collaboration between Neptune Mutual and SushiSwap
Explore Neptune Mutual's ongoing collaboration with SushiSwap offering several benefits.
Youtube Video
Playing the video that you've selected below in an iframe
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:
“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.
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:
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.
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.
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.
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.
Understand Sybil attacks, their examples, and prevention strategies to secure networks.
As blockchain technology evolves with new innovations and more people adopt this innovative financial system, security threats remain a significant concern. It’s been causing users to hesitate to join the space due to the potential loss of funds.
One such threat is the Sybil attack, a formidable security challenge that has led to the loss of millions over the years. With this attack, the attacker gains access to a network's nodes and disrupts its integrity, posing a severe risk to blockchain networks and their users.
In this blog, we will delve into the mechanics of Sybil attacks, exploring how they work and the threats they pose to blockchain networks. We will examine different types of Sybil attacks, provide real-world examples, and discuss effective prevention strategies.
Let’s begin.
A Sybil attack is a critical security threat where an individual or group creates multiple fake identities or nodes, to gain control over a network. In the context of blockchain, nodes are essential for validating the transactions and maintaining the network integrity.Each node has a copy of the blockchain, which gets updated as new transactions are confirmed.
A Sybil attack disrupts this process by creating numerous fake nodes, potentially allowing the attacker to gain a majority control over the network. This enables them to manipulate the network's consensus. If successful, the attacker can alter records, double-spend coins, or invalidate legitimate transactions, undermining the trust and security of the entire blockchain system.
These attacks can be triggered by vulnerabilities in how nodes are created or validated. If it's too easy to set up new nodes, malicious actors can flood the network with fake ones, ready to attack at any moment.
Beyond blockchain, Sybil attacks can also occur in other contexts, such as online voting systems or social media platforms, where multiple fake accounts can be used to manipulate results or spread false information.
As mentioned earlier, malicious actors can create numerous fake nodes within a blockchain network to proceed with Sybil attacks.
Once the attacker has enough fake nodes in the network, they can manipulate its processes. For example, in networks where decisions are made based on votes from nodes, the attacker can use their fake nodes to outvote honest nodes and push through malicious proposals. They could also intercept and analyze user data, jeopardizing the privacy and security of the network's users.
A common goal for Sybil attackers is to achieve a 51% attack. This happens when an attacker controls more than half of the network's computing power. With this majority, they can rewrite or change the order of transactions, prevent new transactions from being confirmed, or even reverse their own transactions to spend the same cryptocurrency twice (known as double spending).
Sybil attacks can be categorized into two main types: direct Sybil attacks and indirect Sybil attacks.
A direct Sybil attack occurs when a malicious node interacts directly with honest nodes in the network. In this scenario, the fake nodes created by the attacker communicate with genuine nodes, which are unable to distinguish between legitimate and fraudulent nodes. As a result, the attacker can influence the honest nodes to take actions that serve their self-interests, such as approving malicious transactions or proposals.
On the other hand, an indirect Sybil attack involves the use of proxy nodes as intermediaries. Instead of interacting directly with the honest nodes, the attacker uses these proxy nodes to mask the activities of the Sybil nodes. This allows the attacker to disseminate false information and execute their attack without revealing the true source of the malicious activity.
Sybil attacks have targeted various blockchain networks over the years. One notable example occurred in November 2020, when the Monero blockchain experienced a 10-day-long Sybil attack. The attacker used several malicious nodes to disrupt the network to deanonymize transactions.
Another significant Sybil attack happened to Ethereum Classic in the summer of 2020. Originally part of the Ethereum network, Ethereum Classic retained the old chain after a major hack led to a hard fork. In this attack, a hacker gained control of the majority of Ethereum Classic’s hash power, enabling them to execute a double-spend attack and steal over $5 million in ETC by manipulating transactions and exchanges.
A high-profile Sybil attack also targeted the Verge blockchain in 2021. The attackers executed a 51% attack, erasing approximately 200 days' worth of transaction data. However, the network was able to recover within a few days.
The Solana network also faced a Sybil attack in 2022, resulting in the theft of over $5 million worth of cryptocurrencies. The attacker exploited a vulnerability in Solana, highlighting the susceptibility of even high-performance blockchains to such attacks and underscoring the importance of continuous security improvements.
These examples highlight the various forms and impacts of Sybil attacks, demonstrating the need for robust security measures in decentralized networks.
Preventing Sybil attacks is crucial for maintaining the security and integrity of blockchain networks. Several strategies can be implemented to make it difficult and expensive for attackers to create multiple fake nodes.
One effective method is to use consensus mechanisms like Proof-of-Work (PoW) and Proof-of-Stake (PoS). In PoW, nodes must solve complex mathematical problems requiring significant computational power and energy. This high cost makes it impractical for an attacker to control enough nodes to dominate the network.
Similarly, in PoS, validators must stake a significant amount of cryptocurrency to participate. For example, on the Ethereum network, validators need to stake 32 ETH, making it economically unfeasible to run multiple nodes for a Sybil attack.
Social trust graphs can also help detect Sybil nodes. These graphs analyze the connectivity data between nodes and assess their trustworthiness. Nodes that display suspicious behavior are flagged with a low trust level, making it easier to identify and isolate Sybil nodes. Techniques like SybilRank and SybilGuard are examples of such methods.
Identity validation can prevent Sybil attacks by ensuring that each node represents a legitimate participant. This can be done through direct validation, where a central authority verifies new validators by checking their details, such as IP addresses and real-world identities. With projects like Worldcoin, proof-of-personhood validation could be significant in identifying users with iris biometrics.
Implementing a hierarchical system can also deter Sybil attacks. In this approach, new nodes are placed on probation until they prove their legitimacy. Long-standing nodes with a proven track record are given more influence, making it difficult for new, potentially malicious nodes to carry out major attacks.
While various preventive measures exist to combat Sybil attacks, these threats persist. It’s been evident that attackers continuously develop innovative ways to exploit vulnerabilities and bypass existing preventive measures.
As an investor in DeFi projects, safeguarding your funds from such threats is crucial. Neptune Mutual offers a solution with our DeFi insurance services. Neptune Mutual is a Web3 project dedicated to providing DeFi insurance solutions to users who wish to protect their investments from unforeseen incidents that could result in financial loss.
Our platform operates as a marketplace across three different blockchain networks: Ethereum, Arbitrum, and BNB Smart Chain. We enable DeFi projects to create cover pools, from which users can purchase cover policies to insure their investments against potential risks.
To benefit from our insurance solutions, users should encourage the projects they have invested in to establish cover pools on our marketplace. Projects can easily reach out to us through our contact page to set up their cover pools and define parameters.
Follow us on X and join our Discord chat to know more about Neptune Mutual.