Skip to content
Snippets Groups Projects
Select Git revision
  • 8165
  • 8001
  • 8159
  • 8068
  • 8118
  • 8162
  • 8161
  • 6994
  • 8106
  • 8166
  • 7944
  • 8148
  • 7980
  • 8164
  • 8128
  • 7567
  • 7691
  • gh-readonly-queue/master/pr-8136-3b4c48e7e3bba96091024643407994938607e3b9 protected
  • master default protected
  • 8069
20 results
Compare History
Davide Galassi's avatar
Move cryptographic hashing procedures to crypto folder. (#2306)
Davide Galassi authored 
Step towards https://github.com/paritytech/polkadot-sdk/issues/1975

As reported
https://github.com/paritytech/polkadot-sdk/issues/1975#issuecomment-1774534225
I'd like to encapsulate crypto related stuff in a dedicated folder.

Currently all cryptographic primitive wrappers are all sparsed in
`substrate/core` which contains "misc core" stuff.

To simplify the process, as the first step with this PR I propose to
move the cryptographic hashing there.

The `substrate/crypto` folder was already created to contains `ec-utils`
crate.

Notes:
- rename `sp-core-hashing` to `sp-crypto-hashing`
- rename `sp-core-hashing-proc-macro` to `sp-crypto-hashing-proc-macro`
- As the crates name is changed I took the freedom to restart fresh from
version 0.1.0 for both crates

---------

Co-authored-by: default avatarRobert Hambrock <roberthambrock@gmail.com>
4c10fd2a
Name Last commit Last update
..
.config
.maintain
bin
client
deprecated/hashing
docker
docs
frame
primitives
scripts
test-utils
utils
zombienet
.dockerignore
.editorconfig
.git-blame-ignore-revs
.gitattributes
HEADER-APACHE2
HEADER-GPL3
LICENSE-APACHE2
LICENSE-GPL3
README.md
README.md

Substrate

GitHub license GitLab Status PRs Welcome Stack Exchange

Substrate is a next-generation framework for blockchain innovation 🚀.

Getting Started

Head to docs.substrate.io and follow the installation instructions. Then try out one of the tutorials. Refer to the Docker instructions to quickly run Substrate, Substrate Node Template, Subkey, or to build a chain spec.

Community & Support

Join the highly active and supportive community on the Substrate Stack Exchange to ask questions about use and problems you run into using this software. Please do report bugs and issues here for anything you suspect requires action in the source.

Contributions & Code of Conduct

Please follow the contributions guidelines as outlined in docs/contributor/CONTRIBUTING.md. 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/contributor/SECURITY.md.

License

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.