Contributing to the Project
CasperLabs strives to scale opportunity for everyone - forever.
We have spent the past year heads down building enough of the core system so we can eventually turn over the system to the community - because the blockchain should be maintained and governed by the community itself.
We created a starting point for best practices for contributing to the project. Please take a moment to review these best practices. If you have suggestions to improve, please feel free to make suggestions / edits.
Composition of the Project
The CasperLabs project is made up of the following sections:
Functional Area | Description | Language |
|---|---|---|
Consensus Protocol | The Highway Protocol | Scala |
Execution Engine | Smart Contract execution engine, wasm + state trie | Rust |
Node | Node container, gRPC endpoints, metrics, GraphQL, P2P network and Kademlia Node Discovery | Scala |
Integration Test Framework | Integration tests that run with CI/CD for each Pull request | Python |
Clarity Block Explorer | The CasperLabs web interface for creating accounts and block explorer | Typescript |
Smart Contract Examples | Example Smart Contracts for developer enablement | Rust / Assemblyscript |
Documentation | Node Operator guide, dApp developer guides in GitHub | Markdown |
Proposed List of Improvements
If you have an idea for an improvement, you can file it here (@Piotr Dziubecki could you please add a create ticket link here)
If you would like to work on an issue, please assign the issue to yourself and place the issue in 'In Progress” (@Piotr Dziubecki please check the access permissions for public ticket editing) - maybe we need another workflow - maybe they comment first)