Temporal has an experimental I2P infrastructure layer allowing access to our hosted API’s and tooling via the I2P network. Currently we have three I2P services:
- IPFS gateway
- IPFS HTTP API
- Temporal HTTP API
Before attempting to access these services you’ll want to make sure you have I2P installed and running. Once you’ve done that, the fastest way to start accessing these services is by manually updating your address book. We are currently publishing the .i2p address however we just recently started doing this, so it may take some time to fully propagate.
For an abbreviated version of this, that simply contains the .i2p addresses and their corresponding base64 addresses, see the gist on github https://gist.github.com/postables/de2885281a58f9dcfce023d4190af22f
If you dont have access to github due to their recent restrictions, see the copy we have on ipfs https://gateway.temporal.cloud/ipfs/QmZAiJKGYMWLu7mwFhYch8Rthkf7jfhAn5rrbspP5ddFkF
One thing to bear in mind, these requests to I2P sites using SSL will give you a certificate warning because the certificate being used was issued for temporal.cloud not the .i2p domains. While you generally shouldn’t accept these, in this case there’s no way around this.
While we won’t focus on the specifics of anonymity provided by I2P in general, we’ll talk about the configurations we’re using, and possible concerns.
The playground can be quite slow over I2P it uses a default tunnel length of 0 hops. Additionally the playground has analytics implemented via fathom, which is pretty solid at respecting privacy and uses UUIDs.
Additionally the playground makes clearnet API calls, which means that your requests will be routed through an outproxy.
Everything other than the playground uses tunnel lengths of 1 hop.
The IPFS gateway resides at temporal-gateway.i2p and has the following base64 address.
In order to access the gateway easily, you should add the aforementioned base64 address to your address book under the name temporal-gateway.i2p
This does not use HTTPS.
Temporal HTTP API
Temporal’s HTTP API, the same one you’re using when making calls to https://api.temporal.cloud resides at temporal-api.i2p and has the following base64 address
In order to access the api easily, you should add the aforementioned base64 address to your address book under the name temporal-api.i2p
This does use HTTPS
IPFS HTTP API
Our IPFS HTTP API, the same one you’re using when making calls to https://api.ipfs.temporal.cloud resides at temporal-api-ipfs.i2p and has the following base64 address
In order to access the API easily, you should add the aforementioned base64 address to your address book under the name temporal-api-ipfs.i2p
This does not use HTTPS
While the playground is server over I2P, it makes API calls to Temporal’s API on the clearnet. This means that your requests will end up going through an outproxy and won’t be entirely contained within I2P. Additionally it uses fathom tracking, and loads a stripe checkout script if on the credits page. The initial connection is a little slow while the website loads.
It resides at temporal.i2p and has the following base64 address
In order to access the playground easily, you should add the aforementioned base64 address to your address book under the name temporal.i2p
This does not use HTTPS
What is Temporal ?
Temporal is an open-source API leveraging IPFS technology to provide robust functionality for distributed data storage systems that can be easily integrated into any enterprise application stacks.
Temporal’s powerful Web 3.0 infrastructure allows users to achieve enterprise-level scale and security without the need for expensive or cumbersome infrastructure.
Thank for Reading & Stay In Touch
We have a few methods of keeping informed about Temporal’s latest developments, and access community support: