Skip to content

πŸš€ Substrate framework with integrated IPFS support.

License

Apache-2.0, GPL-3.0 licenses found

Licenses found

Apache-2.0
LICENSE-APACHE2
GPL-3.0
LICENSE-GPL3
Notifications You must be signed in to change notification settings

TDSoftware/substrate-ipfs

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.

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/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.

IPFS

This version of Substrate contains a working IPFS node and IPFS integration. Just install and start this implementation like any other substrate blockchain.

# E.g. run the blockchain in development mode
cargo run --bin substrate -- --dev --ws-external --rpc-cors all --enable-offchain-indexing=true

Once started, you should see the connecting peer id in the console:

net: starting with peer id 12D3KooWRhtRwRq6Jo9cTTNjgC5MNRVyb33jXwkX8r3hpENqAmP8
IPFS: Node started with PeerId 12D3KooWRhtRwRq6Jo9cTTNjgC5MNRVyb33jXwkX8r3hpENqAmP8 and address ["/ip4/127.0.0.1/tcp/49595/p2p/12D3KooWRhtRwRq6Jo9cTTNjgC5MNRVyb33jXwkX8r3hpENqAmP8"]

If you are interested, feel free to get in contact: tdsoftware.de

For more details you should check out this this documentation or for implementation details, check the following project folders:

/client/offchain
/frame/tds-ipfs-core
/frame/tds-ipfs
/primitives/runtime/src/offchain

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.