🥷
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-18: Implement, adopt and enforce an update to Samurai Node NFT RPC Endpoints

Motivation

This proposal suggests for the protocol to implement, adopt and enforce an update to the existing smart contract that enables, facilitates and provides access to the RPC endpoints that are accessible and usable to Samurai Node NFT holders.

The proposal suggests for the NFT metadata within the smart contracts to be changed appropriately, to a newly developed solution.

Enacting the NFT metadata change shall enable Samurai Node NFT holders to be provided access to RPC endpoints that are compatible with the Ethereum and Arbitrum blockchains and that have deprecated Avalanche (AVAX) C-Chain endpoints. The enactment of this change would thus increase the availability of RPC endpoints from three blockchains to four, effectively expanding the coverage and scope of the RPC endpoints facilitated by Samurai Node NFTs, while mitigating the use of RPC endpoints on blockchains with less user activity.

Shall the proposal and the consequent NFT metadata adjustment be approved, the newly developed solution will improve the current security of Samurai Node NFTs and the RPC endpoints, as a result of newly implemented ID elements. The newly added ID elements would be checked and verified upon their usage.

Specification

Edit the current RPC URLs embedded in NFT metadata.

Call setURIForBase function on contract 0x4f89c90E64AE57eaf805Ff2Abf868fE2aD6c55f3 to set the new base URI for the new NFT metadata which embed the RPC URLs

PreviousSIP-17: Expand ‘Settlement & Release’ initiativeNextSIP-19: Implement, adopt and enforce Samurai Chat

Last updated 5 months ago