Reference implementation of the Filecoin protocol, written in Go
Go to file
2021-05-13 17:48:55 -04:00
.circleci chore(ci): Enable build on RC tags 2021-05-13 12:36:54 -04:00
.github Update proving-issues.md 2021-02-27 00:55:55 -05:00
api Merge tag 'v1.8.0' into release/v1.9.0 2021-04-27 10:30:33 +02:00
blockstore CachedBlockstore is not referenced as of 3795cc2bd2 2021-04-06 13:24:49 +02:00
build Pull the nerpa upgrade pr and update the version to rc4 2021-05-13 17:48:55 -04:00
chain mining lookback is effectively a constant - make it so 2021-05-05 23:23:01 +02:00
cli Add description to the client deal CLI command 2021-04-09 00:58:29 -04:00
cmd Merge tag 'v1.8.0' into release/v1.9.0 2021-04-27 10:30:33 +02:00
conformance Merge branch 'master' into refactor/lib/blockstore 2021-02-28 19:55:23 +00:00
documentation Merge tag 'v1.8.0' into release/v1.9.0 2021-04-27 10:30:33 +02:00
extern Update to proof v7.0.1 2021-05-06 17:31:15 -04:00
gen API proxy struct codegen (#5854) 2021-03-23 13:42:56 +01:00
genesis port to v2 imports 2020-10-21 12:16:23 -07:00
journal Centralize everything on ipfs/go-log/v2 2021-04-06 15:04:32 +02:00
lib Centralize everything on ipfs/go-log/v2 2021-04-06 15:04:32 +02:00
lotuspond v4 specs-actors integration, nv12 migration 2021-04-27 02:02:44 -04:00
markets Fix unseal comment 2021-03-22 14:39:03 +01:00
metrics API proxy struct codegen (#5854) 2021-03-23 13:42:56 +01:00
miner mining lookback is effectively a constant - make it so 2021-05-05 23:23:01 +02:00
node Merge tag 'v1.8.0' into release/v1.9.0 2021-04-27 10:30:33 +02:00
paychmgr Import secp sigs in paych tests 2021-03-25 12:28:53 +01:00
scripts bugfix: fixup devnet script 2020-11-22 00:11:39 +08:00
storage wdpost: Always head tipset to get randomness 2021-03-11 09:59:26 +01:00
system avoid global ResourceConstraints. 2020-12-02 22:26:30 +00:00
testplans remove overwrite for go-data-transfer in testplans 2021-03-31 23:17:16 +03:00
tools Merge branch 'master' into feat/other-network-images 2021-04-01 11:22:59 -07:00
.codecov.yml Add misc tooling to codecov ignore list 2021-01-13 17:07:27 +01:00
.dockerignore add docker support 2019-12-05 11:31:32 +08:00
.gitignore OpenRPC Support (#5843) 2021-03-19 19:22:46 +01:00
.gitmodules remove extern/blst 2021-01-20 16:19:07 +01:00
.golangci.yml lint: don't skip builtin 2021-03-25 17:21:56 -07:00
CHANGELOG.md Fix 1.9.0-rc2 date 2021-04-30 14:34:03 -04:00
Dockerfile.lotus add job to build docker image and push to AWS ECR private repo 2021-01-20 16:27:19 +01:00
go.mod Merge tag 'v1.8.0' into release/v1.9.0 2021-04-27 10:30:33 +02:00
go.sum Merge tag 'v1.8.0' into release/v1.9.0 2021-04-27 10:30:33 +02: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 API proxy struct codegen (#5854) 2021-03-23 13:42:56 +01:00
README.md README: refine Contribute section. 2021-01-12 16:59:48 +00:00
SECURITY.md Update SECURITY.md (#5246) 2020-12-23 00:48:25 -03:00

Project Lotus Logo

Project Lotus - 莲


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

Building & Documentation

For instructions on how to build, install and setup lotus, please visit https://docs.filecoin.io/get-started/lotus.

Reporting a Vulnerability

Please send an email to security@filecoin.org. See our security policy for more details.

These repos are independent and reusable modules, but are tightly integrated into Lotus to make up a fully featured Filecoin implementation:

Contribute

Lotus is a universally open project and welcomes contributions of all kinds: code, docs, and more. However, before making a contribution, we ask you to heed these recommendations:

  1. If the proposal entails a protocol change, please first submit a Filecoin Improvement Proposal.
  2. If the change is complex and requires prior discussion, open an issue or a discussion to request feedback before you start working on a pull request. This is to avoid disappointment and sunk costs, in case the change is not actually needed or accepted.
  3. Please refrain from submitting PRs to adapt existing code to subjective preferences. The changeset should contain functional or technical improvements/enhancements, bug fixes, new features, or some other clear material contribution. Simple stylistic changes are likely to be rejected in order to reduce code churn.

When implementing a change:

  1. Adhere to the standard Go formatting guidelines, e.g. Effective Go. Run go fmt.
  2. Stick to the idioms and patterns used in the codebase. Familiar-looking code has a higher chance of being accepted than eerie code. Pay attention to commonly used variable and parameter names, avoidance of naked returns, error handling patterns, etc.
  3. Comments: follow the advice on the Commentary section of Effective Go.
  4. Minimize code churn. Modify only what is strictly necessary. Well-encapsulated changesets will get a quicker response from maintainers.
  5. Lint your code with golangci-lint (CI will reject your PR if unlinted).
  6. Add tests.
  7. Title the PR in a meaningful way and describe the rationale and the thought process in the PR description.
  8. Write clean, thoughtful, and detailed commit messages. This is even more important than the PR description, because commit messages are stored inside the Git history. One good rule is: if you are happy posting the commit message as the PR description, then it's a good commit message.

License

Dual-licensed under MIT + Apache 2.0