Skip to content

Commit fd1c86c

Browse files
authored
fix: broken e-ipfs link (#2149)
1 parent 8d50c04 commit fd1c86c

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

packages/website/posts/2022-07-06-elastic-ipfs.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ What does this mean for NFT.Storage users? Uploads of all sizes being much faste
6161

6262
## Elastic IPFS under the hood
6363

64-
More literature on how Elastic IPFS works will be coming in the future. However, here are some notes on how it diverges significantly from the two major IPFS implementations today, go-ipfs and [js-ipfs](https://js.ipfs.io/). And all the [code is open source](https://github.com/ipfs-elastic-provider), so you can always dive into it yourself!
64+
More literature on how Elastic IPFS works will be coming in the future. However, here are some notes on how it diverges significantly from the two major IPFS implementations today, go-ipfs and [js-ipfs](https://js.ipfs.io/). And all the [code is open source](https://github.com/elastic-ipfs/), so you can always dive into it yourself!
6565

6666
- No Blockstore: Blocks are retrieved directly from CAR files uploaded by users.
6767
- Single peer ID: We run the service as a single peer ID across cloud service regions, leaning into off-the-shelf redundancy and load balancing from the cloud provider.

0 commit comments

Comments
 (0)