Denis Pisarev
82e52b8be8
* CI: prep for the new ff deployment * CI: variable for CI image * git: add CI team and remove Max from CODEOWNERS * CI: diener should be updated in CI image, not here. * CI: diener should be updated in CI image, not here. * CI: run cargo deny on changes to manifests and lock; run build jobs on schedules [skip ci] * CI: remove flaming-fir deployment, it will be handled from s3 updates [skip ci] * CI: trigger simnet with a certain substrate version * CI: remove cargo-audit in favor of cargo-deny; prepare for being triggered * CI: prepare to be triggered * CI: chore
Substrate · 
Substrate is a next-generation framework for blockchain innovation 🚀.
Trying it out
Simply go to substrate.dev and follow the installation instructions. You can also try out one of the tutorials.
Contributions & Code of Conduct
Please follow the contributions guidelines as outlined in docs/CONTRIBUTING.adoc. In all communications and contributions, this project follows the Contributor Covenant Code of Conduct.
Security
The security policy and procedures can be found in docs/SECURITY.md.
License
- Substrate Primitives (
sp-*), Frame (frame-*) and the pallets (pallets-*), binaries (/bin) and all other utilities are licensed under Apache 2.0. - Substrate Client (
/client/*/sc-*) is licensed under GPL v3.0 with a classpath linking exception.
The reason for the split-licensing is to ensure that for the vast majority of teams using Substrate to create feature-chains, then all changes can be made entirely in Apache2-licensed code, allowing teams full freedom over what and how they release and giving licensing clarity to commercial teams.
In the interests of the community, we require any deeper improvements made to Substrate's core logic (e.g. Substrate's internal consensus, crypto or database code) to be contributed back so everyone can benefit.