Table of Contents
Planet includes a recent version of the IPFS node and utilizes it to retrieve and publish information on the IPFS P2P network. This integrated IPFS node provides several useful local ports.
To prevent conflicts with other programs that may utilize these ports, such as a pre-existing IPFS desktop application, we have made minor adjustments to the port numbers.
This port serves as the local gateway. You can use it to access content on the IPFS P2P network. Below are a few examples.
Access a specific CID
For example, the v4.2.08.0 release of Uniswap:
Access via Local Gateway:
IPNS is the naming system utilized by IPFS, which can be accessed through the /ipns/ paths as demonstrated below:
If an ENS has its content hash pointing to a resource on IPFS, it can be accessed through an IPFS gateway in the following manner:
If a DNS name has a DNSLink TXT record pointing to a resource on IPFS, it can be accessed through an IPFS gateway:
Blogs and websites published from Planet are IPNS. Other Planet users can simply use Follow Planet to receive the latest updates, or these can also be accessed through the local gateway. For example, the IPNS powered planetable.eth is:
It can be accessed via the local gateway:
Kubo, the Go implementation of IPFS, exposes an HTTP RPC API that allows you to control the node and run the same commands that you can run from the command line.
You can access this API on port 5981. For example, the following cURL request would return the Identity of the node:
curl -X POST http://localhost:5981/api/v0/id
Origin isolation is an important security feature for decentralized app front-ends running on IPFS gateways. So, when you try to access a URL like this:
Kubo will return a redirect to transform the URL into this:
However, Safari does not support this kind of URL as of this writing:
*.localhost. This is a known issue recorded in the WebKit bug tracking system:
To prevent that redirect on Safari, you need to replace
127.0.0.1 so that the redirect will not occur: