4EVERLAND Documents
HomeTwitterDiscordBlogs
  • Welcome to 4EVERLAND
  • Get started
    • Our Features
    • Quick Start Guide
      • Registration
      • Login options
        • MetaMask
        • OKX Wallet
        • Binance Web3 Wallet
        • Bitget Wallet
        • Phantom
        • Petra
        • Lilico
      • Usage Introduction
      • Dashboard stats
      • Account
        • Linking Your EVM Wallet to 4EVERLAND Account
        • Balance Alert
    • Billing and Pricing
      • What is LAND?
      • How to Obtain LAND?
      • Pricing Model
      • Q&As
    • Tokenomics
  • HOSITNG
    • What is Hosting?
      • IPFS Hosting
      • Arweave Hosting
        • Auto-Generation of Manifest
      • Internet Computer Hosting
      • Greenfield Hosting
    • Guides
      • Creating a Deployment
        • With Git
        • With IPFS Hash
        • With a Template
      • Site Deployment
      • Domain Management
        • DNS Setup Guide
        • ENS Setup Guide
        • SNS Setup Guide
          • The gateway: 4sol.xyz
        • SPACE ID Setup Guide
      • Project Setting
        • Git
      • Troubleshooting
      • Common Frameworks
    • Hosting Templates Centre
      • Templates Configuration File
    • Quick Addition
      • Implement Github 4EVER Pin
      • Github Deployment Button
    • Hosting API
      • Create Project API
      • Deploy Project API
      • Get Task Info API
      • IPNS Deployment Update API
    • Hosting CLI
  • Storage
    • Bucket
      • IPFS Bucket
        • Get Root CID - Snapshots
      • Arweave Bucket
        • Path Manifests
          • Instructions for Building Manifest
          • Auto-Generation of Manifest
        • Arweave Tags
        • Unleash Arweave
      • Guides
      • Bucket API - S3 Compatible
        • Coding Examples
          • AWS SDK - Go (Golang)
          • AWS SDK - Java
          • AWS SDK - JavaScript
          • AWS SDK - .NET
          • AWS SDK - PHP
          • AWS SDK - Python
          • AWS SDK - Ruby
        • S3 Tags Instructions
      • 4EVER Security Token Service API
      • Bucket Tools
      • Bucket Gateway Optimizer
    • 4EVER Pin
      • Guides
      • Pinning Services API
      • IPFS Migrator
    • Storage SDK
  • Gateways
    • IPFS Gateway
    • IC Gateway
    • Arweave Gateway
    • Dedicated Gateways
      • Gateway Access Controls
      • Video Streaming
      • IPFS Image Optimizer
    • IPNS Manager
      • IPNS Manager API
  • RPC
    • Guides
    • API Keys
    • JSON Web Token (JWT)
    • What's CUs/CUPS
    • WebSockets
    • Archive Node
    • Debug API
    • Chains RPC
      • BSC / opBNB
      • Ethereum
      • Optimism
      • Polygon
      • Taiko
  • AI
    • AI RPC
      • Quick Start
      • Models
      • API Keys
      • Requests & Responses
      • Parameters
    • 4EVER Chat
  • RaaS - Beta
    • What's Rollups?
    • 4EVER Rollup Stack
  • DePIN
    • 4EVER Network
    • Storage Nodes
  • More
    • Use Cases
      • Livepeer
      • Lens Protocol
      • Optopia.ai
      • Linear Finance
      • Snapshot
      • Tape
      • Taiko
      • Hey.xyz
      • SyncSwap
    • Community
    • Tutorials
    • Security
    • 4EVERLAND FAQ
Powered by GitBook
On this page
  • Understanding IPNS
  • To get started:
  • IPNS Use Cases
  1. Gateways

IPNS Manager

By utilizing advanced encryption technology, build and expand your projects with secure, customizable IPNS name records for your content.

Understanding IPNS

IPNS (InterPlanetary Naming System) serves as a crucial bridge between the existing internet infrastructure and the IPFS (InterPlanetary File System) ecosystem. Its primary purpose is to map the familiar URLs we use on the conventional internet to unique hash values within the IPFS network.

By doing so, when accessing web pages or files on IPFS, users no longer need to grapple with lengthy hash strings; they can simply input URLs as they are accustomed to. IPNS dynamically associates these addresses with the desired content, allowing for stable naming even as the underlying content evolves.

In essence, IPNS enables more user-friendly access to IPFS content without the direct reliance on raw hash values. This convenience significantly contributes to the widespread adoption and utilization of IPFS .

  • Persistent Names for Dynamic Content: IPNS provides stable naming for content that is regularly updated.

  • Simple Versioning: Keep the same IPNS link while updating content.

  • Secure Content Updates: Public key cryptography authenticates content updates.

Advantages of IPNS include:

  • User-Friendly Addresses: Simplifies sharing and remembering links.

  • Dynamic Content Management: Ideal for applications requiring regular updates.

  • Expanded Functionality: Broadens the use cases for IPFS.

Additionally, the 4EVERLAND IPNS Manager further enhances this convenience by providing users with the following functionalities:

  1. Customized Label: Users can log in to the 4EVERLAND dashboard and create custom name records. These records can be created instantly and resolved from any IPFS gateway.

  2. Publishing Period: Users have the flexibility to customize the timeframe (24 hours, 10 days, 90 days, 180 days) for automatically publishing IPNS records to IPFS.

  3. Support for Decentralized Domain Names: IPNS name records support decentralized domain name extensions (ENS).

To get started:

Log in to your 4EVERLAND Dashboard and navigate to Gateway > IPNS Manager.

Click "Create" and choose your preferred method:

  • Generate an IPNS with IPFS Path

  • Create IPNS via decentralized domain.

Set your IPNS name/decentralized domain name, copy the IPFS CID you want to link, and select the publishing period. Then, click "Create" to complete the setup.

IPNS Use Cases

  1. Content Distribution: IPNS provides persistent, human-readable links for frequently updated content hosted on IPFS, such as news articles or dynamic web pages. This means that even as content changes, users can still access the latest version of the data through the same URL.

  2. Decentralized Websites: By associating domain names with IPFS addresses through IPNS, we can build decentralized websites. Even as content changes, the website's URL remains constant, ensuring users can always access the desired information.

  3. Versioned Data: Using IPNS to link to different versions of datasets on IPFS enables users to easily access and verify the latest or specific versions. This is highly useful for data scientists, researchers, or developers as they can directly access the required data snapshots.

  4. Secure Message Delivery: By associating user identities with IPNS addresses, we can create a secure messaging system. This ensures that communication on the IPFS network is secure and verifiable. For example, you can use an IPNS address to send encrypted messages, ensuring that only specific recipients can decrypt and read them.

Last updated 10 months ago