# Safura Redefining how companies manage their digital risks. Residual Risk Coverage On-chain In today's digital economy, businesses are perpetually on edge. Data breaches, cyberattacks, and critical server downtimes are not "if" but "when" scenarios. Even with robust cybersecurity measures, firewalls, and rigorous staff training, a company will always face residual risk – the inherent, unmitigated risk that remains after all reasonable controls have been implemented. This is precisely where Safura is exploring a revolutionary solution: a Residual Risk Coverage Product designed to transform how traditional businesses achieve and maintain ISO 27001 compliance and bolster their financial resilience. Digital assets' value has increased to the trillions over the years. The Web3 economy has a lot of potential but in order for wider adoption, it needs to be safe. Currently, less than 1% of digital assets are covered. This presents a unique opportunity for cover to fill the gap. The implementation of cover will enhance community trust and protect against risks like exchange failures, cyber-attacks, and lost or stolen wallet keys. Safura will provide its own platform while embedding cover offerings on DEXes & wallet front-ends. Smart contract security shouldn't end with the audit report. Safura, a DAO founded by auditors and members of the AuditOne ecosystem, has forked a protocol for asset cover (a clean fork of Nexus Mutual with different parameters & tokenomics) which is being deployed on the Sonic blockchain. Community members can choose to have their funds protected with coverage, giving them peace of mind and protecting their assets from potential risks. Projects can purchase coverage to increase community trust, knowing they're protected against potential vulnerabilities. For AuditOne, it's about putting skin in the game and backing our audits with long-term security guarantees.\ \ Vitalik Buterin (the founder of Ethereum) gave his opinion about such cover solution here: # The Problem Consider these stark realities: * Average Cost of a Data Breach: IBM's 2023 report estimates the average cost of a data breach at a staggering $4.45 million globally, a figure that rises exponentially for larger enterprises. * Downtime Epidemic: Industry analyses indicate that a single hour of server downtime can cost large enterprises anywhere from $300,000 to over $1 million. * Compliance Penalties: Regulatory bodies like GDPR can impose fines of up to 4% of a company's global annual turnover for data protection failures, often accompanied by crippling legal and reputational damage. In Web3 cover protocols exist and even those face serious risks, which can lead to significant financial losses. Accurate risk assessment and determination of appropriate premiums are essential to the success and sustainability of a cover policy. Safura is a community-driven cover concept where members share risk, and the community analyzes claims. This process leverages member experience and feedback to ensure accurate risk assessment and appropriate feedback handling. Auditors are well placed to evaluate technical risk, creating a direct link between auditing and after-performance compensation. The $SAFU token will play an important role in these coverage pools, acting as a settlement and payment tool. **Coverage Mechanism:** The coverage pools will allow projects to lock $SAFU tokens as collateral for protection coverage. The premium rates and coverage limits will be determined based on the project's audit history and risk profile. In case of an exploit, the coverage pool will compensate the affected project using the locked $SAFU tokens. This system ensures that only thoroughly audited projects receive coverage, minimizing the risk for users.\ \ **Risk Mitigation:** We will implement relative and absolute coverage limits to mitigate early-stage risks. This means coverage amounts will be capped based on the project's size and risk assessment. Additionally, the community will evaluate and approve coverage applications, ensuring a democratic and transparent process.

# Why Safura? Safura offers comprehensive protection for Web3 applications, combining advanced security, financial stability, and reliability through cover smart contracts. By doubling down your project's protection against vulnerabilities and exploits, Safura reduces financial losses and ensures stability in the event of an attack with Smart contract cover, meaning a high level of reliability and protection for its users, building up stakeholder confidence and reducing risks.\ \ As part of the ecosystem of AuditOne, Safura is well-positioned to gain traction early on. We have already been talking to many clients to offer coverage for their smart contracts. Furthermore, we will embed the protection directly into platforms of clients, user facing and optional for purchase in just a few clicks. The ecosystem is designed to provide value for all stakeholders: **Clients:** Get flexible and easy-to-use protection that can be modified or extended to meet changing needs. **Auditors:** Earn extra rewards by completing audits and staking, and maintain accountability for your work. **Community:** Joins cover pool, earns staking rewards, and shares a portion of the premiums.
# Sonic Safura will launch on the Sonic blockchain ecosystem, with the help of Metropolis being the first external project to utilize their launchpad for a token fairlaunch. Sonic has seen remarkable growth, with its **Total Value Locked (TVL)** surging from **$131M on Jan 15, 2025, to over $399M** on Feb 15. Currently, **DefiLlama reports its TVL at around $428M**, placing it among notable Layer 1 networks. This rapid expansion highlights Sonic’s increasing prominence in the **DeFi sector**. Safura can leverage this momentum to attract significant liquidity and user engagement for the community.
# Safura Protocol Safura is a DeFi cover alternative for risk-sharing among members. It allows members to purchase various cover products to protect against risks. The $SAFU token is used within the protocol for risk sharing. ### How it works? ### User: 1. **Purchase Coverage:** Secure cover by staking $SAFU tokens in dedicated staking pools. 2. **Receive Token:** After purchasing protection, you’ll receive a modifiable NFT representing your coverage. 1. These NFTs allow users to: 1. Adjust the coverage amount and duration. 2. Extend their existing coverage. 3. Transfer the coverage to other addresses easily. Each cover policy is represented by an NFT, providing users with full transparency and control. 3. **File a Claim:** In case of a loss, file a claim for part of the cover amount while maintaining active coverage for the remaining balance. ### Protocols: 1. **Become eligible** for the coverage. (Multiple audits required) 2. **Choose embedded protection** (& on Safura) or **only on Safura** to be purchasable. 3. **Get a share of the revenue** generated from your coverage. # Safura Fairlaunch Safura, a platform founded by members of the AuditOne ecosystem, aims to transform community-driven risk management through its innovative protocol, culminating in the upcoming $wSAFU token (the tradable version of $SAFU is $wSAFU and you will be able to wrap/unwrap on Safura) fairlaunch on the [Metropolis DEX](https://metropolis.exchange/). Mark your calendars for April 26, and get ready to participate. The $wSAFU Fairlaunch is a public liquidity event where participants can contribute Sonic tokens ($S) in exchange for $wSAFU-$S LP tokens. These tokens can be claimed once the liquidity event concludes. The LP tokens received will have a value in $S that matches the amount contributed. We will use $wSAFU tokens to create LP tokens. The final price of the token will be calculated based on the following formula: **50% of Total $S allocated / Amount $wSAFU token** This process allows the LP pool for the $wSAFU token to open securely. It ensures that everyone who participates in the Fairlaunch pays the same price for the token. This setup also protects against bot attacks during the early stage of adding liquidity. There are 4,000,000 $wSAFU tokens set aside for the Fairlaunch contract. **Total Amount of $wSAFU distributed: 4,000,000** (Equals roughly 200k USD as of March 17) ### $SAFU NFT Token Giveaway and Fairlaunch Roadmap ### Launch of the Safura NFT Collection **Date:** 14th March 2025 * Kickoff with an NFT giveaway. * Engage with Twitter posts and weekly Galxe quests. * Win NFTs that secure your spot in the upcoming fairlaunch. #### Public Launch of Safura on Sonic Testnet **Date:** 9th April 2025 * Try out Safura’s coverage pools and risk management protocols. * Get a first look and provide feedback before mainnet. #### Fairlaunch of $wSAFU on Metropolis starts **Date:** 26th April 2025 * Early access via Galxe and Twitter quests. * Whitelist opportunity for acquiring $wSAFU tokens #### Launch of Safura on Sonic Mainnet **Date:** 30th April 2025 * Official mainnet deployment. * Projects can now integrate coverage into their platforms. * A major step toward security and transparency in Web3. #### Distribution of the allocated $S Token: **Total Supply:** 20M $SAFU * 45% (9M): Safura DAO (Contribution, bounties & marketing) * 25% (5M): Community Incentives * 20% (4M): Fairlaunch * 10% (2M): AuditOne Treasury (vested). # $SAFU Token $SAFU token is a governance and utility token linked to a capital pool. When contributing $S to the capital pool, $SAFU is minted and sent to the contributor's wallet. * Onchain Governance: $SAFU holders vote on protocol upgrades and investment allocations. * DAO Governance: Members use $SAFU to decide on the use of DAO treasury funds through proposals and voting. * Staking: $SAFU is used for staking, allowing members to create capacity for cover purchases and earn rewards from cover fees. * Claims Assessment: Stakers participate in assessing claims with a lockup period to prevent attacks; fraudulent voters risk having their staked $SAFU burned.

Token Benefits

### Total initial token supply of $SAFU: 20M 9M (45%) Safura DAO (for contributors, bounties & marketing; expenses max. 10% per year)\ 5M (25%) Community Incentives\ 4M (20%) Fairlaunch \ 2M (10%) AuditOne Treasury (1-year cliff and 4 years vesting) \ 1,000 Safura Shields NFTs are airdropped to the community.\ NFT holders get early access to the fair launch and receive 0.5% of $SAFU tokens. The tokens will be unlocked over 6 months starting in Q3.
As Safura is part of AuditOne's ecosystem, $AUDIT holders can convert their tokens to $wSAFU (up to 1M (5%) is made available by the Safura DAO treasury). We will announce a guide on "how to" once the technical infrastructure is developed. *** ### **Contributor compensation (vested) for the first year:** #### **1,000,000 $SAFU (5%) = $50,000** **5% of the total token supply** (valued at $50,000, based on the fictional $1M starting valuation) is allocated for Core Contributors (CC) in the first year. Special task bounties might come up that will be covered by the Safura DAO allocation. #### **Breakdown of Allocation** 1. **Lead (160,000 $SAFU = $8,000):** * The lead contributor receives **16% of the allocated 100,000 tokens**, emphasizing their pivotal role in guiding the DAO’s development. * This substantial reward reflects the responsibilities and strategic influence the lead is expected to have. 2. **Other Committee Members (each 120,000 $SAFU = $6,000):** * Committee members **each receive 12% of the allocated tokens** for their critical support in decision-making and execution. 3. **Non-Committee Members (each 40,000 $SAFU = $2,000):** * Non-committee contributors **each receive** **4% of the allocated tokens**, recognizing their valuable, albeit limited, contributions to the DAO. *** #### **Premise of Allocation** 1. **Gradual Unlocking Over the Year:** * Tokens are vested incrementally (e.g., monthly or quarterly), ensuring contributors remain aligned with the DAO’s goals throughout the year. * This avoids front-loading rewards and incentivizes sustained efforts. 2. **Contribution-Based Distribution:** * Allocations are tied to predefined roles and contributions. Contributors are rewarded based on their impact and responsibilities within the DAO. 3. **Authority to Cancel Token Allocations:** * The **Lead** has the authority to **terminate future token unlocks** for contributors who fail to meet their commitments. * This safeguard ensures accountability and protects the protocol’s resources. *** #### **Token vesting & unlock through Hedgey Finance** * **Key Features:** * Transparent, trustless execution of vesting schedules. * Contributors can track their vesting schedules and claim tokens automatically. * Minimizes manual oversight, reducing the risk of errors or disputes. *** #### **Subsequent Years (Year 2, Year 3, etc.)** 1. **Evaluation-Based Adjustments:** * Token allocations may change based on annual evaluations of: * Contributors’ performance and impact. * The DAO’s evolving requirements and goals. * External factors such as market conditions. 2. **Dynamic Allocation:** * Future allocations ensure the DAO remains flexible and can adapt rewards to incentivize contributors as the protocol matures. # Liquidity Planting 🌱 Earn rewards by staking your tokens in our coverage pools! Safura's Liquidity Planting allows you to grow your yield while supporting vital smart contract coverage. 1. Each "Liquidity Planting Campaign" involves staking specific tokens into a Safura coverage pool associated with a partner project to earn designated rewards. 2. To participate, you must stake your tokens through the official [Safura dApp](https://app.safura.io/stake) interface. 3. Rewards are calculated based on the specified rate for each campaign (e.g., 0.03 $AUDIT per $SAFU staked for the AuditOne campaign) and the amount of tokens staked. 4. Each campaign may have a total reward pool limit (e.g., 50,000 $AUDIT for the AuditOne campaign). Once this limit is reached, rewards for that specific campaign will cease. 5. Rewards for all new stakes initiated within a calendar month will be **distributed at the end of that same month**. 6. Only stakes with a chosen duration of **183 days or longer** will be eligible to receive Liquidity Planting Campaign rewards. Stakes with durations shorter than 183 days will not receive any Liquidity Planting rewards. # Token Model The Safura protocol includes a Ratcheting Automated Market Maker (RAMM) for minting and redeeming $SAFU. RAMM is a two-pool system built on the Capital Pool, ensuring claims are payable during major loss events. It balances **$S (Sonic)** inflow/outflow, $SAFU staking, investment allocations, and asset-liability management through an automated mechanism. Members can use assets in the Capital Pool to underwrite cover products and vote on investment allocations. **Ratcheting Automated Market Maker (RAMM)**[​](https://docs.nexusmutual.io/protocol/nxm-token/token-model#ratcheting-automated-market-maker-ramm) The RAMM model consists of two virtual one-sided Uniswap v2-style pools: Below Pool and Above Pool. Both pools share a defined amount of **$S** liquidity paired with virtual $SAFU reserves. **Below Pool:** * Handles swaps below the Book Value. * $SAFU sold is burned; **$S** is distributed. * Can only redeem $SAFU when the spot price is less than or equal to the Book Value. **Above Pool:** * Handles swaps above the Book Value. * **$S** is added to the pool, and $SAFU is minted in return. * Can only purchase $SAFU when the spot price is greater than or equal to the Book Value. # Staking Staking plays a critical role in the protocol, as allocating staked $SAFU against cover products opens up available capacity so other members can purchase cover. Previously, any member could participate in the risk assessment process, though there were technical barriers and cost-prohibitive gas fees that prevented more members from staking $SAFU. In the updated staking model, members can participate in one of two roles: * **$SAFU stakers.** Members who choose a fixed timeframe delegate their staked $SAFU to risk experts who manage staking pools. * **Staking pool managers.** Members with risk and pricing expertise that create and manage risk-staking pools. ### Staking $SAFU[​](https://docs.nexusmutual.io/protocol/staking/#staking-nxm) Members who lack the technical expertise or the time to assess risk and manage $SAFU stakes can choose to participate as **$SAFU stakers** by delegating staked $SAFU to one or multiple staking pools. Delegating $SAFU allows members to socialize gas costs and passively earn $SAFU rewards when people buy cover from the associated staking pool. #### Delegating staked $SAFU[​](https://docs.nexusmutual.io/protocol/staking/#delegating-staked-nxm) When someone chooses to stake and delegate their $SAFU, they delegate both capital and voting power. Staking pool managers can use the delegated $SAFU stakes to allocate against cover products within the pool and use the pool’s voting power to participate in onchain governance. However, delegated $SAFU stakes cannot be used in the Claims Assessment process. $SAFU stakers do not control how their $SAFU is allocated within a staking pool. However, they can review staking pools to see which cover products are included in the pool, the staking pool manager’s record of past $SAFU burns, and the staking pool’s current APY. #### Staking periods[​](https://docs.nexusmutual.io/protocol/staking/#staking-periods) When someone decides to stake their $SAFU, they need to choose the length of time that their $SAFU will be locked in a staking pool: this is referred to as the staking period. Members can choose to stake their $SAFU for as little as 91 days or as long as two years. There are a total of eight staking periods to choose from. Members can delegate their $SAFU to multiple staking pools and for multiple staking periods.
Staking Period #Days
191
2182
3273
4364
5455
6546
7637
8728
Each staking period will have a fixed date range, so all $SAFU delegated in one staking period will expire simultaneously. If a member delegates their staked $SAFU to Staking Period #1 noted above 20 days into the 91-day period, then their staked $SAFU would be subject to a 71-day lockup when Staking Period #1 ends and members can withdraw their $SAFU. ### Tokenized staking positions[​](https://docs.nexusmutual.io/protocol/staking/#tokenized-staking-positions) Once someone chooses their preferred staking period and stakes their $SAFU in one or multiple pools, their staking positions are tokenized as an NFT (ERC-721). Staked $SAFU cannot be withdrawn before the staking period ends, but members can always choose to sell their staking position and access liquidity before the staking period ends. Members must use their whitelisted address to withdraw rewards as they accrue to the tokenized staking position. However, a member can transfer their staking NFT to a non-member address for various reasons (e.g., holding a staking position in an address secured by a hardware wallet). Because these NFTs are transferable, someone can switch their membership address before a staking period, or staking periods, end as the NFT can be transferred to an address, and membership can then be transferred to that address. ### Rewards[​](https://docs.nexusmutual.io/protocol/staking/#rewards) When members purchase cover and pay the cover fee, 90% of the cover fee is minted in $SAFU rewards and distributed to stakers in the pool. Staking rewards are streamed over the course of the cover period and accrue to tokenized staking positions. These rewards do not compound to staking positions and are freely withdrawable by individual NFT owners at any time, so long as the owner is a member of the Safura. Tokenized staking positions accrue rewards using a time-based veToken model, where locking $SAFU for longer periods increases the share of cover fees a member will receive. $SAFU stakers who are long-term aligned receive greater rewards. Staking rewards are calculated as follows: #### Staking rewards formula[​](https://docs.nexusmutual.io/protocol/staking/#staking-rewards-formula) `rewardShares = stakeShares * (1 + (10% * LOCK_PERIODS_IN_A_YEAR * daysUntilStakeLockPeriodEnds / 365)` Where: * `stakeShares` is the amount of $SAFU staked in one position for a given lock period * `LOCK_PERIODS_IN_A_YEAR = 4` Example * `stake = 100 $SAFU` * `stakeShares = 100` * `daysUntilStakeLockPeriodEnds = 92` `rewardShares = 100 * (1 + 10% * 4 * 92 / 365) = 100 * (1 + 0.10) = 100 * 1.10 = 110` #### Incentives to stake $SAFU in longer-term lock periods[​](https://docs.nexusmutual.io/protocol/staking/#incentives-to-stake-nxm-in-longer-term-lock-periods) When members stake $SAFU and enter into longer-term staking periods (i.e., lock periods), they receive more stake shares, which increases the share of cover fees they receive every time someone buys cover from the staking pool. Stake shares decrease over time as a member’s staking position approaches the end of the lock period. Delegating staked $SAFU to a staking pool for a 728-day staking period will provide the highest share of cover fees, given the staking shares would remain high for a year before starting to diminish as the remaining lock period decreases below 365 days. You can refer to the available staking periods in the section above. This mechanism aligns incentives between $SAFU stakers, who benefit from higher staking shares for longer-term staking periods; staking pool managers, who benefit from long-term capacity that can be used to sell covers for up to 364 days; and cover buyers, who benefit from access to deep capacity for longer periods when they decide to purchase protection. ### Risk of $SAFU burns[​](https://docs.nexusmutual.io/protocol/staking/#risk-of-nxm-burns) When members delegate their staked $SAFU to a pool, their $SAFU can be burned to facilitate claim payouts if members who purchased cover from the pool file successful claims. If a claim is filed and approved by claims assessors, then the staked $SAFU allocated to the relevant cover product is burned proportionally across all stakers. Each cover has reserved capacity denominated in $SAFU, which determines the conversion rate applied to a staking pool when $SAFU is burned to facilitate a claim payout. The protocol also takes the global capacity factor into account. See the following scenario for an example: * The total cover amount is 100 $S * 1 $SAFU is equal to 0.1 $S at the time of the cover buy * The claim amount is equal to 50 $S * The global capacity factor is 2 The $SAFU burned to facilitate the claim payout would be as follows: `50 ($S) / 0.1 ($S/$SAFU) / 2 = 250 $SAFU` $SAFU stakers earn rewards but risk losing their staked $SAFU, as $SAFU burns can result in a portion of a position or the whole position being burned.
# Security Safura Protocol Security Overview Safura provides robust protocol security by combining regular audits, live contract monitoring, and protective community mechanisms. Below is a detailed breakdown of the audits and security practices that help ensure the safety of Safura smart contract infrastructure. We have completed a diff audit by auditors from [AuditOne](https://www.auditone.io/audit-report/safura-audit). #### Audits Endorsed by Safura To uphold the integrity and safety of Safura’s smart contracts, Safura utilized Nexus Mutual’s top-tier audited smart contracts. * [**iosiro Audit – October 2023**](https://iosiro.com/audits/nexus-mutual-tokenomics-smart-contract-audit)\ Reviewed the Ratcheting AMM (RAMM) contracts to verify the security and functionality of the new framework. * [**Chaos Labs Economic Audit – October 2023**](https://chaoslabs.xyz/resources/chaos_labs_nexus_mutual_pt_1.pdf)\ Completed a deep economic assessment of the RAMM design to ensure sustainable tokenomics and proper incentive structures. * [**iosiro Audits – Nov-Dec 2022 & Feb-Mar 2023**](https://gist.github.com/iosiro-security/9ab387c0f43fddfc50e3a66802d2f4f7#file-iosiro_nexus-mutual-v2-md)\ Evaluated all contracts in the contracts/modules folder, the foundation of Nexus Mutual V2. * **iosiro Audits – May & June 2021**\ Covered key components including: * [Stacked risk contracts](https://iosiro.com/audits/nexus-mutual-stacked-risk-on-chain-mcr-and-swap-operator-smart-contract-audit) * [On-chain MCR contracts](https://iosiro.com/audits/nexus-mutual-stacked-risk-on-chain-mcr-and-swap-operator-smart-contract-audit) * [Swap operator](https://iosiro.com/audits/nexus-mutual-stacked-risk-on-chain-mcr-and-swap-operator-smart-contract-audit) * [Distributor smart contract](https://iosiro.com/audits/nexus-mutual-distributor-smart-contract-audit) * [Emergency response contract](https://iosiro.com/audits/nexus-mutual-emergency-response-smart-contract-audit) * **G0 Group Audits – June & Nov 2020, March 2021**\ Assessed: * [Pooled staking contracts](https://github.com/g0-group/Audits/blob/master/G0Group-NexusMutual2020Jun.pdf) * Claim payout upgrade mechanisms * Distribution contracts * [**Solidified Audit – April 2019**](https://github.com/solidified-platform/audits/blob/master/Audit%20Report%20-%20Nexus%20Mutual%20%5B22.04.2019%5D.pdf)\ Conducted a pre-mainnet audit of the core smart contracts and system components critical to launching the protocol. #### Ongoing Security Practices: RAMM Launch To reinforce trust during the RAMM deployment, Nexus Mutual implements advanced on-chain safeguards and real-time surveillance: * **Circuit Breakers**\ Enforces ETH withdrawal and NXM minting caps to mitigate systemic risk. These limits are eased gradually over time. * **Real-Time Monitoring**\ Leveraging Tenderly alerts, the engineering team stays updated on any abnormal or suspicious contract behavior. * **Emergency Pause Capability**\ The Advisory Board can immediately halt RAMM contract activity in critical situations. #### Bug Bounties As part of Safura’s security efforts, we have launched a bug bounty program running until December 31, 2026. Participants must complete KYC to be eligible, and rewards range from $300 to $10,000, depending on the severity of the reported issue. More details can be found on[ AuditOne's Bug Bounty page](https://www.auditone.io/bug-bounty/safura).
# Claim Assessment Members who held active cover can submit a claim when a loss event occurs. Once a claim is submitted, members can stake $SAFU and participate as a claim assessor, who reviews the validity of a submitted claim. Across the current - and any future - cover products, there are two different claim types. ### Claim types[​](https://docs.nexusmutual.io/protocol/claims-assessment/#claim-types) #### Individual claims[​](https://docs.nexusmutual.io/protocol/claims-assessment/#individual-claims) The individual claim process applies to the following cover products: * Protocol Cover * Bundled Protocol Cover * DeFi Pass Cover * Native Protocol Cover * Fund Portfolio Cover * $S Slashing Cover * Quota Share Cover For individual claims, cover holders can submit claims with supporting proof of loss and details about their loss. These claims are reviewed by assessors on an individual basis to determine the validity of each claim that is filed. #### Group claims[​](https://docs.nexusmutual.io/protocol/claims-assessment/#group-claims) The group claim process applies to our since deprecated Yield Token Cover product. For future products, a group claim can apply if a loss is assessed on a group basis. If such a loss event were to occur, the Advisory Board would trigger a group claim event through an onchain governance proposal. A group claim outcome would determine if one event was valid. These claims would not be assessed on an individual basis. ### Claim process[​](https://docs.nexusmutual.io/protocol/claims-assessment/#claim-process) Coverage holders start the claim process when a loss occurs, and assessors get involved once a claim has been submitted. #### 1. Claim submission[​](https://docs.nexusmutual.io/protocol/claims-assessment/#1-claim-submission) Members who held active cover when the loss event occurred can submit a claim through the Safura user interface. When a claim is submitted, the cover holder will provide details related to the loss incident, the loss amount, and the supporting proof of loss. Before a claim can be filed, the cover holder must make a claim deposit denominated in $S. * The claim deposit is refunded in the same transaction as the claim payout if the claim is approved. * If the claim is denied, the claim deposit will not be refunded. The deposited amount is the $S equivalent of the $SAFU amount distributed as claim assessment rewards, e.g., the minimum deposit required could be 0.05 $S, and the maximum amount required is an $S deposit equivalent to 50 $SAFU. See the claims assessment rewards section below. Claim deposits are required to prevent people from spamming the claim process with multiple claims, as there is no limit to the number of times a claim can be submitted. If a cover holder provides a claim deposit, they can file a claim as often as preferred. #### 2. Voting process[​](https://docs.nexusmutual.io/protocol/claims-assessment/#2-voting-process) Once a claim is submitted, the voting process begins. A claim vote lasts for a minimum of three days. **Claim assessors**[**​**](https://docs.nexusmutual.io/protocol/claims-assessment/#claim-assessors) Members can stake their $SAFU and participate as a claim assessor. Claim assessment stakes are locked for 90 days after a member’s last vote was cast. Assessors review the incident details, proof of loss, and other supporting information to determine a claim’s validity. Members discuss submitted claims in[ AuditOne's Discord](https://discord.com/invite/n9jXmCw5d5). **Outcomes**[**​**](https://docs.nexusmutual.io/protocol/claims-assessment/#outcomes) **Accept.** If a claim assessor reviews the proof of loss and supporting evidence and determines a claim is valid, they can submit their vote to approve. Once a vote to approve has been submitted, other members can submit votes to approve or deny the claim. * A simple majority (50%+) is required to decide an assessment vote * The assessment will last for a minimum of three days, which starts from the time the first vote to approve is submitted * There is a 24-hour silent period, where no votes should be cast before an assessment vote closes * If a vote is submitted during the last 24 hours of the vote, the voting period is extended with an amount of time proportional to the voter's stake, with 24 hours representing the maximum time increase. * This design feature prevents "rush attacks," where someone tries to overturn a claim outcome by submitting a vote at the last minute, that moves the majority outcome with no time to appeal the vote. **Deny.** If claim assessors review the claim submission and determine that no loss has occurred or that the claim does not meet the terms of the cover wording, no deny vote is required unless another member submits a vote to approve. * If a claim receives no votes and the three-day period passes, the claim will be denied by default #### 3. Claim payouts[​](https://docs.nexusmutual.io/protocol/claims-assessment/#3-claim-payouts) When a claim vote has closed with an accepted status, a cool-down period of one day needs to pass before the claim payout can be redeemed by the member who submitted the successful claim. Once the cool-down period has passed, a claim vote is finalized, and the member has 30 days to redeem their claim payout. #### 4. Claim assessment rewards[​](https://docs.nexusmutual.io/protocol/claims-assessment/#4-claim-assessment-rewards) **Total rewards**[**​**](https://docs.nexusmutual.io/protocol/claims-assessment/#total-rewards) Members who lock their $SAFU and participate in the claim assessment process earn rewards for voting on claims. The total assessment reward pool is calculated using the following formula: `totalRewardIn$SAFU = min(maxRewardIn$SAFU, expectedPayout * rewardRatio * coverPeriodInDays / 365)` Where the `maxRewardIn$SAFU` is equal to 50 $SAFU, and the `rewardRatio` is 1.3%. **Individual rewards**[**​**](https://docs.nexusmutual.io/protocol/claims-assessment/#individual-rewards) Members who lock their $SAFU and participate in the claim assessment process earn a share of the total reward pool. An individual member’s share of claim assessment rewards can be calculated using the following formula: `reward = totalRewardIn$SAFU * userStakeAtVoteTime / (accepted + denied)` Once you assess and vote on a claim, you will earn your share $SAFU rewards, which you can withdraw after the vote closes and the 24-hour cool-down period passes. ### Fraudulent votes[​](https://docs.nexusmutual.io/protocol/claims-assessment/#fraudulent-votes) Claim outcomes can be reviewed during the cool-down period if fraudulent voting is suspected. If the Advisory Board finds a claim assessor to have voted to deny a legitimate claim or approve an illegitimate claim, then a fraud penalty can be imposed. The Advisory Board can submit a merkle-tree root hash representing the fraudulent voter and their assessment stake. The fraudulent vote is reversed, and the fraudulent assessor's stake is burned. Once the Advisory Board submits the merkle-tree root hash, anyone can process the fraud penalty. By processing the fraud penalty, a member executes the transaction that burns the assessor’s stake and reverses their fraudulent vote.
# Safura DAO **Safura DAO LLC** is a decentralized autonomous organization (DAO) registered as a non-profit limited liability company (LLC) in the Republic of the Marshall Islands. It operates under the Marshall Islands Limited Liability Company Act, the Non-Profit Entities Act, and the Decentralized Autonomous Organization Act (DAO Act) of 2022. The DAO is governed by its members, who participate through on-chain voting using the $SAFU token, enabling a fair and transparent decision-making process. It is overseen by a Governance Committee consisting of five members responsible for operational management and treasury. For more details, refer to the Operating Agreement below. {% file src="/files/9HRPIiCWBgGQydP7xIVG" %} # FAQ **What protections are included in the Safura Cover products?**\ Safura offers coverage for various risks associated with digital assets, including​: * Cyber-Attacks: Coverage for losses due to hacking incidents targeting wallets, platforms, or other digital asset infrastructures.​ **How do I know my claim will get paid?** * Safura operates as a DAO, where claims are assessed by auditors/ security experts from AuditOne, and the claim is voted on by all DAO members. The protocol ensures that when a claim is filed and approved, the necessary funds are available to facilitate the payout. If a claim is approved, the staked $SAFU tokens allocated to the relevant cover product will be burned proportionally across all stakers to facilitate the claim payout.
**Community Involvement** **How can community members participate in Safura?** * Community members can engage with Safura by contributing to the DAO's decision-making processes, participating in staking activities, and supporting the platform's growth through various initiatives.​ If you are interested in contributing to the DAO, please join our [Discord](https://discord.gg/n9jXmCw5d5) and check current DAO tasks on [Dework](https://app.dework.xyz/safura-dao/main-space-59018/overview). **What role does the community play in Safura's governance?** * As a DAO, Safura relies on its community for governance. Members can propose and vote on changes, ensuring that the platform evolves in alignment with the collective interests of its stakeholders.​ As a member, you can also contribute to the DAO and help build it. **Tokenomics** **What is the $SAFU token?** * $SAFU is the native token of the Safura platform. It plays a central role in the ecosystem, facilitating various functions such as staking, governance participation, and accessing coverage services.​ **How is the $SAFU token distributed?** * The distribution model of $SAFU tokens is designed to incentivize active participation and ensure a fair allocation among community members, contributors, and stakeholders.​ The token will be fair-launched on Metropolis in Q2 2025. The total supply is capped at 20M with the following distribution: 45% (9M) Safura DAO (Contribution, bounties & marketing), 25% (5M) Community Incentives, 20% (4M) Fairlaunch, 10% (2M) AuditOne Treasury (vested). **What is the purpose of staking $SAFU tokens?** * Staking $SAFU tokens allows community members to contribute to the platform's security and stability. In return, stakers may receive rewards, fostering a mutually beneficial relationship between the platform and its participants.​ By staking, new capacity for the covers is created so that other members can purchase covers. **How does $SAFU integrate with Safura's coverage pools?** * $SAFU tokens are utilized within coverage pools to provide protection for audited smart contracts. Covers can be bought with $SAFU, or cover capacity can be increased by staking it. #### How much % supply will NFT holders receive? * NFT holders themselves are not allocated a direct percentage of the $SAFU token supply. However, NFTs secure your spot in the fairlaunch, which gives early access and possibly whitelist benefits. * The Fairlaunch itself is allocated 20% of the total supply (4 million $SAFU tokens out of 20 million). NFT holders can participate in this fairlaunch if they win or hold an NFT, but they do not automatically receive a percentage of tokens just for holding the NFT. #### What is the use of holding an NFT? **Utilities of the NFT include:** * Guaranteed access to the $SAFU fairlaunch. * Whitelist eligibility through Galxe and Twitter quests * Participation in future community activities like quests and engagement campaigns. #### Can I win multiple NFTs? * Yes, it’s possible to win multiple NFTs by actively engaging in Twitter and Galxe quests—unless future rules specify otherwise. #### When will the Fairlaunch start? The Fairlaunch will start on April 26, 2025, on Metropolis DEX. * Participants contribute $Sonic tokens ($S) and receive $SAFU-$S LP tokens. * Everyone gets the same token price. * A total of 4,000,000 $SAFU tokens (20% of total supply) are allocated for this event.
# Links and Social Got questions or feedback? Contact us at and stay updated by following us on X:[ https://x.com/Safura\_DAO.](https://twitter.com/Safura_DAO) We’d love to hear from you!"