🥷
Samurai Protocol
  • DISCLAIMER
  • Samurai Financial
  • 1. What is Samurai and how does it work ?
    • 1.1 - What is Samurai?
    • 1.2 - What is the total supply of HNR tokens ?
    • 1.3 - Now, how does it actually work ?
    • 1.4 - How does Samurai differ from RING?
    • 1.5 - Why is SAMURAI on the Fantom (FTM) ?
    • 1.6 - Is Metamask the only wallet compatible for now ? What about TrustWallet ?
    • 1.7 - Do I need to install a VPS?
    • 1.8 - Do I need to keep my computer running ?
    • 1.9 - Where can I see the size of the liquidity pool ?
    • 1.10 - Smart Contract Functionality
  • 2. Understanding the NODES
    • 2.1 How does the Lottery system work?
    • 2.2 How does sliding tax work?
    • 2.3 - How much does a node cost ?
    • 2.4 - Can nodes be transferred from one wallet to another ?
    • 2.5 - Are these real nodes ?
    • 2.6 - Why do you call these "nodes" ?
    • 2.7 - I don’t see my rewards every 4 or 8 hours. Is there a problem ?
    • 2.8 - What happens if I don't claim my rewards every time ?
  • Tokenomics
  • Governance
  • Samurai AI
  • Vaults
  • MultiChain ZenGarden
  • Levels
  • Sambot
  • ZenEstate
  • Governance Proposals
    • Samurai Governance
    • Initiate and adopt protocol level governance
    • SIP-1: Adopt and enforce an incentivised LP staking mechanism - Zen Garden
  • [EXTENSION] SIP-1: Adopt and enforce an incentivised LP staking mechanism - Zen Garden
  • SIP-2: Implement a Samurai native OTC NFT solution
  • [EXTENSION] SIP-2: Implement a Samurai native OTC NFT solution
  • SIP-3: Implement, adopt and enforce Samurai Vaults
  • SIP-4: Implement, adopt and enforce Samurai Multichain ZenGarden
  • SIP-5: Implement, adopt and enforce Samurai Levels
  • SIP-6: Replenish Samurai Levels rewards
  • SIP-7: Conduct an OTC NFT acquisition event
  • SIP-8: Retroactive funding
  • SIP-9: Expand MultiChain ZenGarden
  • SIP-10: Conduct an OTC NFT distribution event
  • SIP-11: Temporarily pause Samurai Levels
  • SIP-12: Replenish Samurai Node NFT's rewards
  • SIP-13: Levels v2 Product feature set Ideation
  • SIP-14: Deploy and fund Samurai Governance Vault
  • SIP-15: Implement, adopt and enforce Samurai Levels v2
  • SIP-16: Conduct ‘Settlement & Release’ initiative
  • SIP-17: Expand ‘Settlement & Release’ initiative
  • SIP-18: Implement, adopt and enforce an update to Samurai Node NFT RPC Endpoints
  • SIP-19: Implement, adopt and enforce Samurai Chat
  • SIP-20: Refine Samurai Levels Parameters and Conditions
  • SIP-21: Retroactive funding 2.0
  • SIP-22: Conduct an OTC NFT acquisition event
  • SIP-23: Conduct an OTC NFT distribution event
  • SIP-24: Enact a Samurai Governance Vault Conversion
  • SIP-25: Refine Samurai Chat Parameters
  • SIP-26: Replenish Samurai Levels v2 rewards
  • Articles / Announcements
    • Samurai is here!
    • Honour
    • News, updates, migration and plans for Honour
    • Clearing the air and moving onwards
    • The path towards sustainability
Powered by GitBook
On this page
  • Motivation
  • Specification

SIP-24: Enact a Samurai Governance Vault Conversion

Motivation

This proposal suggests for the protocol to enact a conversion of a portion of the current Fantom (FTM) holdings situated in the Samurai Governance Vault, in the next 180 days. The enactment of the proposal and the associated conversion of Fantom (FTM) to USDT (or USDC/DAI) shall be conducted in order to ensure the Samurai Governance Vault funds are stored in a stable currency and to circumvent the holdings being prone to the price volatility underlying the Fantom token.

The conversion shall safeguard the protocol’s financial health against the potential backdrop of unpredictable market movements that the cryptocurrency industry naturally presents and ensure that the Samurai protocol is positioned effectively to endure and sustain the foreseeable future.

The funds being converted into a stable currency shall benefit the protocol, by ensuring it is in a robust position where it can successfully bootstrap, encourage and fund protocol-related initiatives, products, services and related development.

  • Financial Stability: Transitioning from Fantom (FTM) to a stablecoin ensures that the protocol's financial resources are not subjected to the turbulences of market volatility, thereby securing a clear, predictable and stable financial base.

  • Operational Resilience: With a more predictable financial outlook, the protocol and its contributors can more effectively plan and execute its operational and developmental agendas without the added complexity of managing crypto market risks.

  • Strategic Flexibility: The conversion provides the protocol with the agility needed to capitalize on emerging opportunities and to support future initiatives without the concern of diminishing the Samurai Governance Vault value due to adverse and unpredictable market movements.

  • Sustained Development and Growth: By converting to stablecoins, the protocol enhances its resilience against market downturns, preserving capital for strategic uses and funding protocol-related initiatives that benefit and foster the protocol amidst various market outlooks and scenarios.

The proposed conversion of FTM holdings to a stablecoin arguably resembles a strategic move to mitigate financial risks associated with market volatility. Furthermore, it aligns with the protocol's overarching goals of potentially further growing and expanding its ecosystem of products, services and tools by situating the protocol in a healthier long-term position, where it can support and encourage such initiatives in the future.

The enactment of this proposal shall hence effectively fortify the protocol's financial health and operational resilience.

Specification

The conversion of 1 650 000 Fantom (FTM) situated in 0x6E5A826c8348B3a3f8854afC333562564C71353e to stablecoins (USDT/USDC or DAI) shall be carried out by the core team, at any available price, in the next 180 days.

The conversion shall be executed at any centralised (CEX) or decentralised exchange (DEX).

The execution of the conversion can fully unfold prior to the 180-day limit. Besides the 180-day time limit, the execution of the conversion is at the discretion of the core team.

PreviousSIP-23: Conduct an OTC NFT distribution eventNextSIP-25: Refine Samurai Chat Parameters

Last updated 5 months ago