* pallet-lottery: add generate_storage_info Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * pallet-lottery: test call_to_indices with TooManyCalls Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * review: move try_push above transfer Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * pallet-lottery: test stop_repeat Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * pallet-lottery: test do_buy_ticket as white-box Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * pallet-lottery: use BoundedVec in bechmarks Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * pallet-lottery: fix zero div panic Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * review: extend buy_ticket tests Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * review: test buy_ticket AlreadyParticipating Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * fmt Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * review: use /// comments on private functions Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * review: use with_bounded_capacity Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
Substrate ·

Substrate is a next-generation framework for blockchain innovation 🚀.
Trying it out
Simply go to docs.substrate.io 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.
