Ethereum for Dummies
Ethereum is a decentralized platform that runs smart contracts: applications that run exactly as programmed without any possibility of downtime, censorship, fraud or third party interference.
More issues
Collaborative Clusters
This section documents the collaborative clusters feature in IPFS Cluster. Collaborative clusters allow individual, untrusted peers to join an IPFS Cluster as “followers” (without permission to modify or edit the pinset). In the subsections we detail how to setup and join these clusters:
* Hosting a collaborative cluster
* Joining a collaborative
Hands-on IPLD Tutorial in Golang: PART 1
In this first post of the hands-on series, we will understand the basic concepts of IPLD followed by coding in Golang to persist key-value entries.
Difference Between SideChains and State Channels
State Channels and Sidechains are the two terms in Ethereum community that are often used interchangeably, thus causing mass confusion.
But today we will get it clear.
Go make a cup of coffee first, it’s going to be a long one.
The purpose of this article is to clearly
IPFS Cluster Configuration
All IPFS Cluster configurations and persistent data can be found, by default, at the ~/.ipfs-cluster folder. For more information about the persistent data in this folder, see the Data, backups and recovery section.
ipfs-cluster-service -c <path> sets the location of the configuration folder. This is also controlled by
IPFS Cluster Service
The ipfs-cluster-service is a command line application that runs a full cluster peer:
* ipfs-cluster-service init initializes configuration and identity.
* ipfs-cluster-service daemon launches a cluster peer.
* ipfs-cluster-service state allows to export, import, and cleanup the persistent state.
The ipfs-cluster-service provides its own help by running ipfs-cluster-service --help or ipfs-cluster-service <command&
IPFS Cluster CTL
The ipfs-cluster-ctl command line application is a user-friendly REST API client for IPFS Cluster. It allows to perform all the operations supported by a Cluster peer:
* Pinning
* Unpinning
* Adding
* Listing items in the pinset
* Checking the status of pins
* Listing cluster peers
* Removing peers
Usage
Usage information can be obtained
IPFS Proxy
The IPFS Proxy is an endpoint which presents the IPFS HTTP API in the following way:
* Some requests are intercepted and trigger cluster operations
* All non-intercepted requests are forwarded to the IPFS daemon attached to the cluster peer
This endpoint is enabled by default, and listens by default on /ip4/
IPFS Cluster REST API Reference
IPFS Cluster peers include an API component which provides HTTP-based access to the peer’s functionality. The API attempts to be REST-ful in form and behaviour. It is enabled by default, but it can be disabled by removing its section from the service.json configuration file.
The following API docs
Running Cluster on Kubernetes
This guide will show you how to:
* Run a simple Cluster on Kubernetes
* Using Kustomize, adapt the Cluster Kubernetes resources to your scenario
This guide assumes you have a running Kubernetes cluster to deploy to and have properly configured kubectl
Prepare Configuration Values
Configuring the Secret Resource
In Kubernetes, Secret