Jim Pick jimpick

Introduction to Filecoin app building

This document: https://tinyurl.com/hackfs-pow

Slides from intro presentation: https://speakerdeck.com/andrewxhill/intro-to-filecoin-building-apps-with-powergate

In this workshop, we are going to introduce you to Filecoin through the use of the Powergate. While you can develop using Lotus or other Filecoin implementations directly, the Powergate is designed to provide the necessary abstractions to build Filecoin storage into your application. Some features of the Powergate include fast data retrieval with IPFS serving as a caching layer, deal management, multi-tenant wallet APIs, and more. The system comes set up to run locally in Docker or deploy to your servers.

We'll cover the Powergate CLI and the Powergate JavaScript Client in the two parts of the workshop. To prepare, we encourage you to install a few things before we get started.

Powergate Show & Tell

Objective:

Create drop-in Filecoin API Management tools for systems and apps.

Key components:

Reputation Indices: A collection of data collected from the network for miner selection. Includes miner activity duration, slashing events, and deals.

instructions for building & testing dht-tracer

Step 0: read the project brief

Read this project-brief -- it will give you an understanding of what the goals are for this tool.

Step 1: get the right code

IPLD Layers

Different applications built on top of IPLD need different abstractions. IPLD originates as tightly integrated piece of IPFS. When it was decoupled, two layers of abstractions were built. On the lower level there's [IPLD Formats] and on the higher level there's IPLD. The idea is that you can implement your own format easily and then get the traversal across formats for free.

Those two layers are not enough anymore. There are more concerns that should be separated. This document is describing those layers abstractly without going too much into implementation details. Some layers might be merged when implemented.

	// WARNING: There's much more to know/do around hooks, and
	// this is just a simplification of how these work.

	// shared references, updated
	// per each hook invoke
	let execution = null;
	let current = null;
	let context = null;
	let args = null;

	<!DOCTYPE html>
	<html lang="en">
	<head>
	<meta charset="utf-8">
	<meta name="viewport" content="width=device-width, initial-scale=1.0, shrink-to-fit=no">
	<meta name="description" content="Template cloned from https://github.com/erengy/under-construction.">
	<title>textile.io</title>
	<style type="text/css">
	html, body {
	height: 100%;

	#!/usr/bin/env bash

	# USAGE:
	#
	# Option 1: Build and run tests using specific lotus Git SHA:
	#
	# > ./test-storage-and-retrieval-local-dev-net.sh --lotus-git-sha=15b3e57634458af983082dcbb736140bba2abfdb
	#
	# Option 2: Build and run using binaries you've built previously (much faster)
	#

	package main

	import (
	"context"
	"log"
	"time"

	"github.com/filecoin-project/lotus/chain/store"
	"github.com/filecoin-project/lotus/lib/rpcli"
	"github.com/libp2p/go-libp2p-core/peer"

	.terraform/
	*.pem
	*.tf
	*.tfstate
	*.yaml
	*.backup
	istio-*/
	cert-manager-*/
	*.swp
	env

	#!/usr/bin/env bash

	cat <<EOF \| xargs -L1 ipfs ping -n 1
	QmUd6zHcbkbcs7SMxwLs48qZVX3vpcM8errYS7xEczwRMA
	QmbVWZQhCGrS7DhgLqWbgvdmKN7JueKCREVanfnVpgyq8x
	QmUEMvxS2e7iDrereVYc5SWPauXPyNwxcy9BXZrC1QTcHE
	QmdnXwLrC8p1ueiq2Qya8joNvk3TVVDAut7PrikmZwubtR
	QmNSYxZAiJHeLdkBg38roksAR9So7Y5eojks1yjEcUtZ7i
	EOF