Kredits:IPFS - Revision history

Raucao: /* List of current peers */

2023-09-10T08:17:04Z

List of current peers

Raucao: /* Kosmos IPFS setup */

2022-06-22T12:34:57Z

Kosmos IPFS setup

Raucao: /* List of current peers */

2020-10-26T08:51:58Z

List of current peers

Raucao: /* List of current peers */

2020-10-26T08:33:02Z

List of current peers

Raucao: /* CLI command for applying the peer config */

2020-10-26T08:13:49Z

CLI command for applying the peer config

Raucao: /* List of current peers */

2020-10-26T08:13:33Z

List of current peers

Raucao: Add peering information and config instructions

2020-10-26T07:56:53Z

Add peering information and config instructions

Raucao at 22:33, 26 November 2019

2019-11-26T22:33:12Z

Raucao: /* Kosmos IPFS setup */

2019-11-26T22:31:20Z

Kosmos IPFS setup

Raucao at 22:05, 26 November 2019

2019-11-26T22:05:19Z

@@ Line 30: / Line 30: @@
   <nowiki>[
+   {
      "ID": "QmRw21aC3TroRVdZhrE2Qh4W6PBA67kbE8p3fNfsVcfW8D",

@@ Line 14: / Line 14: @@
 We run a few IPFS nodes, which are linked together to effectively form a cluster, in which kredits data can be accessed very quickly. This is how we mirror our data in a fast and reliable way:
-* Due to all kredits data being public by design, instead of setting up a private cluster, our IPFS nodes simply run [https://gitea.kosmos.org/kosmos/kredits-ipfs-pinner/ a program] which listens to new IPFS hashes being published by the smart contracts on the Ethereum blockchain. Whenever they see a new document being published, they automatically pin it locally (meaning it is downloaded and marked to be saved indefinitely on that node).
+* Due to all kredits data being public by design, instead of setting up a private cluster, our IPFS nodes simply run [https://gitea.kosmos.org/kosmos/kredits-ipfs-pinner/ a program] which listens to new IPFS hashes being published by the smart contracts on the RSK blockchain. Whenever they see a new document being published, they automatically pin it locally (meaning it is downloaded and marked to be saved indefinitely on that node).
 * Our smaller nodes only connect to a few other p2p nodes in order to save memory and CPU resources. However, they are connected to at least one other Kosmos node at all times.
 * Our largest node, which is also running the public gateway at [https://ipfs.kosmos.org/ipfs/ ipfs.kosmos.org], is connected to a few hundred other IPFS nodes, so that anyone else can access kredits data reasonably fast.

@@ Line 30: / Line 30: @@
   <nowiki>[
+   {
      "ID": "QmbqZCZ2RzVr4r1UEdFak6ra76kHxtGmfV9r3e1Ev6Tj5D",

@@ Line 33: / Line 33: @@
      "ID": "QmbqZCZ2RzVr4r1UEdFak6ra76kHxtGmfV9r3e1Ev6Tj5D",
      "Addrs": ["/dns4/barnard.kosmos.org/tcp/4001"]
+   }
 ]</nowiki>

← Older revision		Revision as of 08:13, 26 October 2020
Line 38:		Line 38:
	==== CLI command for applying the peer config ====		==== CLI command for applying the peer config ====

−	<nowiki>ipfs config --json Peering.Peers '[{ "ID": "QmbqZCZ2RzVr4r1UEdFak6ra76kHxtGmfV9r3e1Ev6Tj5D", "Addrs": ["/~~ip4~~/~~104~~.~~248~~.~~95.16~~/tcp/4001"] }]'</nowiki>	+	<nowiki>ipfs config --json Peering.Peers '[{ "ID": "QmbqZCZ2RzVr4r1UEdFak6ra76kHxtGmfV9r3e1Ev6Tj5D", "Addrs": ["/dns4/barnard.kosmos.org/tcp/4001"] }]'</nowiki>

← Older revision		Revision as of 07:56, 26 October 2020
Line 18:		Line 18:
	* Our largest node, which is also running the public gateway at [https://ipfs.kosmos.org/ipfs/ ipfs.kosmos.org], is connected to a few hundred other IPFS nodes, so that anyone else can access kredits data reasonably fast.		* Our largest node, which is also running the public gateway at [https://ipfs.kosmos.org/ipfs/ ipfs.kosmos.org], is connected to a few hundred other IPFS nodes, so that anyone else can access kredits data reasonably fast.
	* Some developers and users also run the [https://gitea.kosmos.org/kosmos/kredits-ipfs-pinner/ Kredits IPFS Pinner] on their own machines. They may run it once every now and then to simply back up the data, or they may also run it on an always-on server of theirs, in order to mirror all kredits data live.		* Some developers and users also run the [https://gitea.kosmos.org/kosmos/kredits-ipfs-pinner/ Kredits IPFS Pinner] on their own machines. They may run it once every now and then to simply back up the data, or they may also run it on an always-on server of theirs, in order to mirror all kredits data live.
		+
		+	== Peering with Kosmos IPFS nodes ==
		+
		+	As a user of Kredits, or someone who wants to support our project by mirroring the data on your node, we recommend that you configure your node to peer with one of our nodes. This means your node will automatically connect to ours, and it will try to keep that p2p connection alive from then on.
		+
		+	=== go-ipfs ===
		+
		+	In the official reference client, [https://github.com/ipfs/go-ipfs go-ipfs], Peering is supported since version 0.6.0. The relevant configuration section is <code>[https://github.com/ipfs/go-ipfs/blob/master/docs/config.md#peeringpeers Peering.Peers]</code>.
		+
		+	==== List of current peers====
		+
		+	<nowiki>[
		+	{
		+	"ID": "QmbqZCZ2RzVr4r1UEdFak6ra76kHxtGmfV9r3e1Ev6Tj5D",
		+	"Addrs": ["/ip4/104.248.95.16/tcp/4001"]
		+	}
		+	]</nowiki>
		+
		+	==== CLI command for applying the peer config ====
		+
		+	<nowiki>ipfs config --json Peering.Peers '[{ "ID": "QmbqZCZ2RzVr4r1UEdFak6ra76kHxtGmfV9r3e1Ev6Tj5D", "Addrs": ["/ip4/104.248.95.16/tcp/4001"] }]'</nowiki>

@@ Line 3: / Line 3: @@
 It is content-addressable, meaning a filename is just a hash of its content. Thereby, identical content is never duplicated, and the authenticity of the content at a certain name or address can easily be verified by hashing it again after downloading it from the p2p network.
-We use IPFS to store Kredits data, like for example contributor profiles and contribution details. Check out these two documents for example:
+We use IPFS to store Kredits data, like contributor profiles and contribution details. Check out these two documents for example:
 * Contributor profile data: [https://ipfs.kosmos.org/ipfs/QmdjFBqJ6Cq9z1Z1mqNPB9LuScaCwUj7tCRwgKu4fEubwp QmdjFBqJ6Cq9z1Z1mqNPB9LuScaCwUj7tCRwgKu4fEubwp]

← Older revision		Revision as of 22:31, 26 November 2019
Line 11:		Line 11:

	== Kosmos IPFS setup ==		== Kosmos IPFS setup ==
		+
		+	We run a few IPFS nodes, which are linked together to effectively form a cluster, in which kredits data can be accessed very quickly. This is how we mirror our data in a fast and reliable way:
		+
		+	* Due to all kredits data being public by design, instead of setting up a private cluster, our IPFS nodes simply run [https://gitea.kosmos.org/kosmos/kredits-ipfs-pinner/ a program] which listens to new IPFS hashes being published by the smart contracts on the Ethereum blockchain. Whenever they see a new document being published, they automatically pin it locally (meaning it is downloaded and marked to be saved indefinitely on that node).
		+	* Our smaller nodes only connect to a few other p2p nodes in order to save memory and CPU resources. However, they are connected to at least one other Kosmos node at all times.
		+	* Our largest node, which is also running the public gateway at [https://ipfs.kosmos.org/ipfs/ ipfs.kosmos.org], is connected to a few hundred other IPFS nodes, so that anyone else can access kredits data reasonably fast.
		+	* Some developers and users also run the [https://gitea.kosmos.org/kosmos/kredits-ipfs-pinner/ Kredits IPFS Pinner] on their own machines. They may run it once every now and then to simply back up the data, or they may also run it on an always-on server of theirs, in order to mirror all kredits data live.

← Older revision		Revision as of 22:05, 26 November 2019
Line 1:		Line 1:
−	~~''TODO~~: ~~add very quick explanation~~ of IPFS ~~itself''~~	+	[https://ipfs.io/ IPFS] is a public, decentralized, p2p file system.
		+
		+	It is content-addressable, meaning a filename is just a hash of its content. Thereby, identical content is never duplicated, and the authenticity of the content at a certain name or address can easily be verified by hashing it again after downloading it from the p2p network.
		+
		+	We use IPFS to store Kredits data, like for example contributor profiles and contribution details. Check out these two documents for example:
		+
		+	* Contributor profile data: [https://ipfs.kosmos.org/ipfs/QmdjFBqJ6Cq9z1Z1mqNPB9LuScaCwUj7tCRwgKu4fEubwp QmdjFBqJ6Cq9z1Z1mqNPB9LuScaCwUj7tCRwgKu4fEubwp]
		+	* Contribution data: [https://ipfs.kosmos.org/ipfs/QmRKRZfNNBk8WH67VK6JWKeM9akgLGpnvDpgLn3T93jZLc QmRKRZfNNBk8WH67VK6JWKeM9akgLGpnvDpgLn3T93jZLc]
		+
		+	(Or you could fetch the same ones from a different node: [https://ipfs.io/ipfs/QmdjFBqJ6Cq9z1Z1mqNPB9LuScaCwUj7tCRwgKu4fEubwp contributor example], [https://ipfs.io/ipfs/QmRKRZfNNBk8WH67VK6JWKeM9akgLGpnvDpgLn3T93jZLc contribution example])

	== Kosmos IPFS setup ==		== Kosmos IPFS setup ==
−
−	~~''TODO: document how we run and use IPFS''~~