Skip to content

API server to retrieve IPFS objects from the Web3.Storage gateway

Notifications You must be signed in to change notification settings

Leto-gg/gateway

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

69 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Leto IPFS Gateway

This is an implementation of an IPFS Gateway what anonymously tracks the volume of requests of IPFS objects/CID's. The main purpose of the CID metrics feature is to keep track of the CIDs requested, providing anonymous but valuable insights into the usage patterns and helping in optimizing the performance and user experience of the IPFS gateway.

Proxy Gateway Architecture

Features

  • Anonymously access IPFS content through the gateway.
  • Keeps user information private by not logging IP addresses or other identifiable information.
  • Lightweight and easy to deploy.

Request tracking: The gateway records every CID requested by users, along with a timestamp. Metrics generation: The gateway generates metrics based on the frequency and recency of CID requests. Data export: The metrics can be exported as CSV, JSON, or other formats for further analysis.

Switching Gateways

If you already have a program/application using an IPFS Gateway, its is very simple to switch to our gateway simply by changing the address of your Gateway to the Leto Gateway located at "https://leto.gg/ipfs/".

Example Hyperlink, linking to an IPFS object: "https://leto.gg/ipfs/bafybeihhgxbaywvizkcfqxdgfbu5ys242xxc4wiv5y7tykmfzp5qwyrtlq"

Using an IPFS HTTP Gateway

Accessing data stored on IPFS is straightforward through the use of various IPFS HTTP gateways.

Given that IPFS is a decentralized, peer-to-peer network, any public HTTP gateway can be utilized to retrieve your data. For the purposes of this guide, we'll be using the gateway provided by Leto.gg. Notably, this service is built upon the Web3.Storage Superfast Gateway. In addition to retrieving your data, it also provides you with valuable anonymous metrics.

When you store data using the web3.storage client, the put method returns an IPFS content identifier (CID) string. That CID points to an IPFS directory that contains all the files you passed in using the put method.

  • Using those cids to point to your program/application is how you retrieve IPFS data from the Web3.Storage infrastructure

w3link (https://ipfs.w3s.link/*) has a rate limit of 200 requests per minute by IP.

Issues and Testing

If you find any bugs, feel free to reach out/make an issues!

About

API server to retrieve IPFS objects from the Web3.Storage gateway

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published