Reference implementation of the Filecoin protocol, written in Go
Go to file
2019-11-27 13:31:44 +01:00
.circleci Don't fallback to older parameters if parameters.json changes 2019-11-14 19:55:31 +01:00
api Merge remote-tracking branch 'origin/master' into feat/election-post 2019-11-27 13:31:44 +01:00
bin pull ipget from dists and use it 2019-09-13 15:29:38 -07:00
build Merge remote-tracking branch 'origin/master' into feat/election-post 2019-11-27 13:31:44 +01:00
chain Merge remote-tracking branch 'origin/master' into feat/election-post 2019-11-27 13:31:44 +01:00
cli Merge remote-tracking branch 'origin/master' into feat/election-post 2019-11-27 13:31:44 +01:00
cmd Merge remote-tracking branch 'origin/master' into feat/election-post 2019-11-27 13:31:44 +01:00
datatransfer Merge pull request #619 from gguoss/patch-2 2019-11-15 14:43:03 +01:00
docs REST file import endpoint 2019-10-23 11:39:44 +02:00
extern replace go-bls-sigs and go-sectorbuilder with filecoin-ffi 2019-11-26 18:16:37 -08:00
gen WIP: election post restructuring 2019-11-21 16:21:45 -06:00
genesis Add lotus-gen, rewire genesis mining 2019-11-24 22:45:13 -06:00
lib Merge remote-tracking branch 'origin/master' into feat/election-post 2019-11-27 13:31:44 +01:00
lotuspond Swtich to xerrors 2019-11-22 10:20:56 -06:00
miner Merge remote-tracking branch 'origin/master' into feat/election-post 2019-11-27 13:31:44 +01:00
node Merge remote-tracking branch 'origin/master' into feat/election-post 2019-11-27 13:31:44 +01:00
paych Audit pass for blatantly wrong panics 2019-11-16 17:41:14 -06:00
peermgr Fix most power slashing issues 2019-11-14 12:56:17 +01:00
retrieval cborrpc -> cborutil 2019-11-07 15:11:39 +01:00
scripts Some improvements to the deploy devnet script 2019-11-15 01:47:36 +01:00
storage Merge remote-tracking branch 'origin/master' into feat/election-post 2019-11-27 13:31:44 +01:00
tools/stats Refactor mining logic to match specs ticket chain 2019-11-20 10:52:36 -06:00
tracing Fix jaeger spam 2019-10-03 20:01:23 +02:00
.codecov.yml Disable codecov comments 2019-07-02 11:55:12 +02:00
.gitignore Merge remote-tracking branch 'origin/master' into feat/election-post 2019-11-27 13:31:44 +01:00
.gitmodules Use https in gitmodules 2019-11-27 12:35:16 +01:00
.golangci.yml Remove doc lint 2019-07-11 10:00:24 +02:00
go.mod Merge remote-tracking branch 'origin/master' into feat/election-post 2019-11-27 13:31:44 +01:00
go.sum Merge remote-tracking branch 'origin/master' into feat/election-post 2019-11-27 13:31:44 +01:00
LICENSE-APACHE Add basic readme and licenses 2019-08-01 21:26:11 -07:00
LICENSE-MIT Add basic readme and licenses 2019-08-01 21:26:11 -07:00
Makefile Merge remote-tracking branch 'origin/master' into feat/election-post 2019-11-27 13:31:44 +01:00
README.md Readme: some minor updates 2019-11-09 09:46:51 +01:00

Lotus

project lotus - 莲

Lotus is an experimental implementation of the Filecoin Distributed Storage Network. For more details about Filecoin, check out the Filecoin Spec.

Development

All work is tracked via issues. An attempt at keeping an up-to-date view on remaining work is in the lotus testnet github project board.

Building

We currently only provide the option to build lotus from source. Binary installation options are coming soon!

In order to run lotus, please do the following:

  1. Make sure you have these dependencies installed:
  • go (1.13 or higher)
  • gcc (7.4.0 or higher)
  • git (version 2 or higher)
  • bzr (some go dependency needs this)
  • jq
  • pkg-config
  • opencl-icd-loader
  • opencl driver (like nvidia-opencl on arch) (for GPU acceleration)
  • opencl-headers (build)
  • rustup (proofs build)
  • llvm (proofs build)
  • clang (proofs build)

Arch (run):

sudo pacman -Syu opencl-icd-loader

Arch (build):

sudo pacman -Syu go gcc git bzr jq pkg-config opencl-icd-loader opencl-headers

Ubuntu / Debian (run):

sudo apt update
sudo apt install mesa-opencl-icd ocl-icd-opencl-dev

Ubuntu (build):

sudo add-apt-repository ppa:longsleep/golang-backports
sudo apt update
sudo apt install golang-go gcc git bzr jq pkg-config mesa-opencl-icd ocl-icd-opencl-dev
  1. Clone this repo & cd into it
$ git clone https://github.com/filecoin-project/lotus.git
$ cd lotus/
  1. Build and install the source code
$ make clean all
$ sudo make install

Now, you should be able to perform the commands listed below.

Devnet

Node setup

If you have run lotus before and want to remove all previous data: rm -rf ~/.lotus ~/.lotusstorage

The following sections describe how to use the lotus CLI. Alternately you can run lotus nodes and miners using the Pond GUI.

Genesis & Bootstrap

The current lotus build will automatically join the lotus Devnet using the genesis and bootstrap files in the build/ directory. No configuration is needed.

Start Daemon

$ lotus daemon

In another window check that you are connected to the network:

$ lotus net peers | wc -l
2 # number of peers

Wait for the chain to finish syncing:

$ lotus sync wait

You can view latest block height along with other network metrics at the https://lotus-metrics.kittyhawk.wtf/chain.

Basics

Create a new address:

$ lotus wallet new bls
t3...

Grab some funds from faucet - go to https://lotus-faucet.kittyhawk.wtf/, paste the address you just created, and press Send.

Check the wallet balance (balance is listed in attoFIL, where 1 attoFIL = 10^-18 FIL):

$ lotus wallet balance [optional address (t3...)]

(NOTE: If you see an error like actor not found after executing this command, it means that either your node isn't fully synced or there are no transactions to this address yet on chain. If the latter, using the faucet should 'fix' this).

Mining

Ensure that at least one BLS address (t3..) in your wallet exists

$ lotus wallet list
t3...

With this address, go to https://lotus-faucet.kittyhawk.wtf/miner.html, and click Create Miner

Wait for a page telling you the address of the newly created storage miner to appear - It should be saying: New storage miners address is: t0..

Initialize storage miner:

$ lotus-storage-miner init --actor=t01.. --owner=t3....  

This command should return successfully after miner is setup on-chain (30-60s)

Start mining:

$ lotus-storage-miner run

To view the miner id used for deals:

$ lotus-storage-miner info

e.g. miner id t0111

Seal random data to start producing PoSts:

$ lotus-storage-miner store-garbage

You can check miner power and sector usage with the miner id:

# Total power of the network
$ lotus-storage-miner state power

$ lotus-storage-miner state power <miner>

$ lotus-storage-miner state sectors <miner>

Stage Data

Import some data:

# Create a simple file
$ echo "Hi my name is $USER" > hello.txt

# Import the file into lotus & get a Data CID
$ lotus client import ./hello.txt
<Data CID>

# List imported files by CID, name, size, status
$ lotus client local

(CID is short for Content Identifier, a self describing content address used throughout the IPFS ecosystem. It is a cryptographic hash that uniquely maps to the data and verifies it has not changed.)

Make a deal

(It is possible for a Client to make a deal with a Miner on the same lotus Node.)

# List all miners in the system. Choose one to make a deal with.
$ lotus state list-miners

# List asks proposed by a miner
$ lotus client query-ask <miner>

# Propose a deal with a miner. Price is in attoFIL/byte/block. Duration is # of blocks.
$ lotus client deal <Data CID> <miner> <price> <duration>

For example $ lotus client deal bafkre...qvtjsi t0111 36000 12 proposes a deal to store CID bafkre...qvtjsi with miner t0111 at price 36000 for a duration of 12 blocks. If successful, the client deal command will return a deal CID.

Search & Retrieval

If you've stored data with a miner in the network, you can search for it by CID:

# Search for data by CID
$ lotus client find <Data CID>
LOCAL
RETRIEVAL <miner>@<miner peerId>-<deal funds>-<size>

To retrieve data from a miner:

$ lotus client retrieve <Data CID> <outfile>

This will initiate a retrieval deal and write the data to the outfile. (This process may take some time.)

Monitoring Dashboard

To see the latest network activity, including chain block height, blocktime, total network power, largest miners, and more, check out the monitoring dashboard at https://lotus-metrics.kittyhawk.wtf.

Pond UI


As an alternative to the CLI you can use Pond, a graphical testbed for lotus. It can be used to spin up nodes, connect them in a given topology, start them mining, and observe how they function over time.

Build:

$ make pond

Run:

$ ./pond run
Listening on http://127.0.0.1:2222

Now go to http://127.0.0.1:2222.

Things to try:

  • The Spawn Node button starts a new lotus Node in a new draggable window.
  • Click [Spawn Storage Miner] to start mining (make sure the Node's wallet has funds).
  • Click on [Client] to open the Node's client interface and propose a deal with an existing Miner. If successful you'll see a payment channel open up with that Miner.

Note: Don't leave Pond unattended for long periods of time (10h+), the web-ui tends to eventually consume all the available RAM.

Troubleshooting

  • Turn it off and on - Start at the top
  • rm -rf ~/.lotus ~/.lotusstorage/
  • Verify you have the correct versions of dependencies
  • If stuck on a bad fork, try lotus chain sethead --genesis
  • If that didn't help, open a new issue, ask in the Community forum or reach out via Community chat.

Architecture

Lotus is architected modularly, and aims to keep clean API boundaries between everything, even if they are in the same process. Notably, the 'lotus full node' software, and the 'lotus storage miner' software are two separate programs.

The lotus storage miner is intended to be run on the machine that manages a single storage miner instance, and is meant to communicate with the full node via the websockets jsonrpc api for all of its chain interaction needs. This way, a mining operation may easily run one or many storage miners, connected to one or many full node instances.

Notable Modules

API

The systems API is defined in here. The RPC maps directly to the API defined here using the JSON RPC package in lib/jsonrpc. Initial API documentation in docs/API.md.

Chain/Types

Implementation of data structures used by Filecoin and their serializations.

Chain/Store

The chainstore manages all local chain state, including block headers, messages, and state.

Chain/State

A package for dealing with the Filecoin state tree. Wraps the HAMT.

Chain/Actors

Implementations of the builtin Filecoin network actors.

Chain/Vm

The Filecoin state machine 'vm'. Implemented here are utilities to invoke Filecoin actor methods.

Miner

The block producer logic. This package interfaces with the full node through the API, despite currently being implemented in the same process (very likely to be extracted as its own separate process in the near future).

Storage

The storage miner logic. This package also interfaces with the full node through a subset of the api. This code is used to implement the lotus-storage-miner process.

Pond

Pond is a graphical testbed for lotus. It can be used to spin up nodes, connect them in a given topology, start them mining, and observe how they function over time.

To try it out, run make pond, then run ./pond run. Once it is running, visit localhost:2222 in your browser.

Tracing

Lotus has tracing built into many of its internals. To view the traces, first download jaeger](https://www.jaegertracing.io/download/) (Choose the 'all-in-one' binary). Then run it somewhere, start up the lotus daemon, and open up localhost:16686 in your browser.

For more details, see this document.

License

Dual-licensed under MIT + Apache 2.0