Lynx Blockchain
  • Welcome
  • Technical Evolution and Architecture Overview
  • History of Lynx
    • Evolution of a Blockchain
    • Hybrid Proof of Work (HPoW) Protocol
    • Pioneering Blockchain Data Storage
    • Evolution to Proof of Stake
    • Next Generation Data Storage Architecture
    • Preserving Knowledge
  • Lynx Core
    • Hardware and System Requirements
    • Lynx Dynamics
    • Open Source
    • Core Parameters and Strategy
    • Sustainability
    • Circulating Supply Analysis
    • Locked Addresses
    • Data Storage
      • auth
      • fetch
      • fetchall
      • store
      • status
      • list
    • Understanding the Encryption Option
    • Understanding Lynx Staking Wait Times
    • Understanding Asset Retrieval Times
    • Understanding Block Time Targeting in the Lynx Blockchain
    • Understanding the Lynx Blockchain Statistics Report
  • Lynx Administration
    • Public Peer Nodes
    • Understanding Blockchain Bootstrap Files
      • Bootstrap Extraction Script
      • Bootstrap Creation Script
    • How to Sweep a Lynx Wallet
    • Enable/Disable Staking
  • Clevver
    • Revolutionizing Digital Preservation
    • Permanent Storage for Digital Assets
    • Permanent Digital Archives for Journalism
    • How did Clevver originate?
    • Shortened URL Support
    • Assigning Tags to Assets
    • How to delete content
    • Clevver Terms of Service Agreement
  • Clevver API
    • Public Methods
      • Batches
      • Files
      • User
  • ElectrumX
    • Lynx ElectrumX nodes
    • Build Script Details
  • External Links
    • Lynx Explorer
    • Lynx Github
    • Lynx Uptime Report
    • Clevver Website
  • Lynx Bootstraps
  • Wallet Links
    • Komodo Wallet
    • Wally.id Wallet
    • Lynx Paper Wallet
  • Social Links
    • Lynx Discord
    • Lynx on Bluesky
    • Clevver on Bluesky
  • Exchange Links
    • FreiXLite (LYNX/LTC)
  • FreiExchange (LYNX/BTC)
  • Komodo Wallet (SWAP)
  • XredX (LYNX/LTC)
  • XredX (LYNX/DOGE)
  • XredX (LYNX/IL8P)
Powered by GitBook
On this page
  1. Clevver

Shortened URL Support

Published: July 2023 | Last updated: November 2024

PreviousHow did Clevver originate?NextAssigning Tags to Assets

Last updated 6 months ago

After a file is stored in Clevver, the user is provided a permanent URL to access the file. An example is below. The format of the file will always be the same length and structure. The link format will always start with HTTPS; the host 'get.clevver.org' is the domain name. The 64-character string is the unique identifier of the file on the blockchain. This identifier for your respective file will never change. The three-character file extension will always be appended to the end of the URL. The URL will always be 92 characters in length.

While the above URL can be used on websites, documentation, email correspondence, and code, the URL can be too long for some use cases—specifically, inclusion in smart contracts. So a shorter version format is listed below. The shorter version can be included in smart contract code and other scenarios where field length restrictions are of concern. The URL will always be 52 characters in length.

Clvr.ly Domain Support

Beginning in August 2022, any files created in Clevver will also be assigned a specially branded, shortened URL. Files created before August 22 will manually be assigned short URLs too. The shortened URL structure provides a 48-character length URL. The short URL does not include a file extension.

The shortened URL above links to the same file above, and it includes a particular caching tier that works well for NFT applications. The shortened URL is conveniently under the URI length limitation imposed by some smart contract platforms. There is no extra fee to get or use the shortened URL for a Clevver asset.

https://get.clevver.org/5e24f4e015cf304ae46e3dc2b240412d41db5e1065f0b90cf7bab913085c0f65.pdf
https://clevver.org/5e24f4e0ae46e3dc2b240412085c0f65
https://clvr.ly/5e24f4e0ae46e3dc2b240412085c0f65
Page cover image