-
Updated
Jun 13, 2022
IPFS
IPFS (InterPlanetary File System) is a peer-to-peer distributed file system that seeks to connect all computing devices with the same system of files.
In some ways, IPFS is similar to the World Wide Web, but IPFS could be seen as a single BitTorrent swarm, exchanging objects within one Git repository. In other words, IPFS provides a high-throughput, content-addressed block storage model, with content-addressed hyperlinks. This forms a generalized Merkle directed acyclic graph (DAG).
IPFS combines a distributed hash table, an incentivized block exchange, and a self-certifying namespace. IPFS has no single point of failure, and nodes do not need to trust each other, except for every node they are connected to. Distributed Content Delivery saves bandwidth and prevents distributed denial-of-service (DDoS) attacks, a problem common with HTTP.
Here are 2,009 public repositories matching this topic...
-
Updated
Jun 10, 2022 - JavaScript
- Version: ipfs-core: 0.14.1
- Subsystem: types, core
Severity: Very Low
Description:
in type definition put: (...) => Promise<CID>, but docs Promise<Block>
Which type is correct?
In Settings : 'Add a new side account' button
Step #2 in Side account creation
(a very light & quick version of onboarding, with only nickname step)
 there is just a message like this displayed:
failed to process trigger: block #21041413 (0x0000…b378), transaction a44fa1857fa5448419ff94682de1ffeccaa74eb0d6dc9d0de8fe37c6c2a90746: Decoding function outputs for the call Function { name: "withdraw", inputs: [], outputs: [Param { name: "", kind: Uint(256), intern
This example
https://github.com/libp2p/js-libp2p/blob/master/examples/peer-and-content-routing
Involves running two scripts simultaneously; they then connect to each other. Each one does this before calling findPeers
// The DHT routing tables need a moment to populate
await delay(100)
This is fine for an example/test but is not good enough for production code. There's no indicat
Seems that Firefox (around version 96-97) changed somethign and is now way more aggresive when a gateway does not start returning response immediately.
For example, first load (empty ipfs repo) of http://dist.ipfs.io.ipns.localhost:8080/go-ipfs/v0.11.0 in Firefox 97 produces:
 won't ever unpin it:
Steps to reprodu
-
Updated
Apr 10, 2020 - TSQL
This was cut from the v0.2.0 release for present time constraints however making ipfs-http more accessible as "the" ipfs binary would make the project more accessible to anyone just wanting to try it out. At the moment I see the following obstacles:
http/README.mdhas no tutorial on how to try outipfs-httpipfs-httpsupports only `i
-
Updated
Jan 4, 2022 - Go
Summary
This is the main tracking issue for Naming Providers support. Naming providers can be either DNS - for use with DNSLink - or even naming services such as ENS and IPNS.
Ideally even doing things like detecting the provider from the domain name and doing the right thing.
Status
| Naming Service | Status |
|---|---|
| CloudFlare | |
| DNSimpl |
-
Updated
Jun 17, 2022 - Go
-
Updated
Mar 10, 2022 - Go
-
Updated
May 15, 2022 - JavaScript


I am using a 1080p monitor, and most of the space is wasted.
I expect the CID to be fully printed given that I have twice the screen space needed to do so.
This is not happening because the the
bafk…vvbyis actually templated server side.I expe