The sophon-miner is used to mine for multiple miners, the advantage is that：
- The miners in the mining pool do not need to deploy their own mining programs.
- It is possible to increase the tps and miner fees for packaging messages.
- Miners can package messages for each other to avoid the problem of selfish mining.
Use Venus Issues for reporting issues about this repository.
For instructions on how to build, install and setup venus, please visit https://venus.filecoin.io/.
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 Venus to make up a fully featured Filecoin implementation:
- specs-actors which has its own kanban work tracker available here
Venus 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:
- If the proposal entails a protocol change, please first submit a Filecoin Improvement Proposal.
- If the change is complex and requires prior discussion, open an issue 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.
- 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:
- Adhere to the standard Go formatting guidelines, e.g. Effective Go. Run
go fmt. - 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.
- Comments: follow the advice on the Commentary section of Effective Go.
- Minimize code churn. Modify only what is strictly necessary. Well-encapsulated changesets will get a quicker response from maintainers.
- Lint your code with
golangci-lint(CI will reject your PR if unlinted). - Add tests.
- Title the PR in a meaningful way and describe the rationale and the thought process in the PR description.
- 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.
Dual-licensed under MIT + Apache 2.0