Hernando Castano
184871525c
* Rename `rialto` deployment to `eth-sub-bridge` * Add base Compose configs for Rialto and Eth-PoA nodes * Add new compose file for eth-sub deployment * Rename bridge-nodes to rialto-nodes * Update bootnode entries for Rialto nodes * Remove new compose file since it was used for quick test * Rename bridge nodes in entrypoint scripts * Remove all nodes from Eth-Sub Compose file The nodes should be getting pulled in from the new compose files. * Remove TODO comment * Rename nodes to networks Reflects the fact that a set of nodes makes up a network. * Add Compose file for Millau network nodes * Enable logging for all Millau nodes * Delete Rialto reserved peers file * Rename `bridge-config` to `scripts` * Add Compose file for Rialto-Millau bridge * Move bridge deployments into `bridges` folder * Drop `bridges` prefix from bridge deployments * Rename folder that had scripts for working with binaries * Move proxy configuration to common top level folder * Make a top level `monitoring` folder * Start updating deployment README * More updates in the README * Remove usage of Git overrides * Remove scripts to run Eth<->Sub I don't think these are used anymore * Remove Github Docker build instructions from main README * Add note about monitoring * Update Millau state root * Add script for running and updating Compose deployments * Remove old update script * Explain usage of `run` script * Update Millau state_root again * Remove repeated Prom image from Rialto-Millau bridge * Quick fix to stop containers in `run` script * Pin GrafanaMatrix Dockerfile to old commit The latest master has some changes in how the application is run. We don't want to update just yet so we're pinning to an old commit. * Make Compose files use a project directory The main consequence of this change is that all paths have to be specified from the root of the `deployments` folder. However, this makes it so that we can reuse components in different deployments, like the GranfaMatrix Dockerfile which is shared by all bridges. * Use `project-directory` when stopping and updating network If we don't use the full Compose command which includes `project-directory` not all the containers get cleaned up correctly. * Update path in Bridge Dockerfile * Correctly ignore `target` folders in Docker builds * Wait for Rialto nodes before running relay * Make `run` script a little less sketchy * Clean up deployment README * Remove stray line * Have run script automatically change into correct directory * Use PoA-to-Rialto instead of Eth-to-Sub in names * Rename `eth-poa-sub` bridge deployment to `poa-rialto` * Use /entrypoints volume for entrypoint scripts * Be more consistent with relay service names * Remove `docker-compose` prefix from network Compose files * Add comment explaning Grafana Matrix commit * Fix wording in README Co-authored-by: Tomasz Drwięga <tomusdrw@users.noreply.github.com> * Cleanup unused line in README * Add link to Slava's test scripts * Remove uneccessary piping when `cd`-ing in `run.sh` Co-authored-by: Tomasz Drwięga <tomusdrw@users.noreply.github.com>
NOTE: We have recently made significant changes to our repository structure. In order to streamline our development process and foster better contributions, we have merged three separate repositories Cumulus, Substrate and Polkadot into this repository. Read more about the changes here.
Polkadot SDK
The Polkadot SDK repository provides all the resources needed to start building on the Polkadot network, a multi-chain blockchain platform that enables different blockchains to interoperate and share information in a secure and scalable way. The Polkadot SDK comprises three main pieces of software:
Polkadot
Implementation of a node for the https://polkadot.network in Rust, using the Substrate framework. This directory
currently contains runtimes for the Westend and Rococo test networks. Polkadot, Kusama and their system chain runtimes
are located in the runtimes repository maintained by
the Polkadot Technical Fellowship.
Substrate
Substrate is the primary blockchain SDK used by developers to create the parachains that make up the Polkadot network. Additionally, it allows for the development of self-sovereign blockchains that operate completely independently of Polkadot.
Cumulus
Cumulus is a set of tools for writing Substrate-based Polkadot parachains.
Releases
Note
Our release process is still Work-In-Progress and may not yet reflect the aspired outline here.
The Polkadot-SDK has two release channels: stable and nightly. Production software is advised to only use stable.
nightly is meant for tinkerers to try out the latest features. The detailed release process is described in
RELEASE.md.
Stable
stable releases have a support duration of three months. In this period, the release will not have any breaking
changes. It will receive bug fixes, security fixes, performance fixes and new non-breaking features on a two week
cadence.
Nightly
nightly releases are released every night from the master branch, potentially with breaking changes. They have
pre-release version numbers in the format major.0.0-nightlyYYMMDD.
Upstream Dependencies
Below are the primary upstream dependencies utilized in this project:
Security
The security policy and procedures can be found in docs/contributor/SECURITY.md.
Contributing & Code of Conduct
Ensure you follow our contribution guidelines. In every interaction and contribution, this project adheres to the Contributor Covenant Code of Conduct.
Additional Resources
- For monitoring upcoming changes and current proposals related to the technical implementation of the Polkadot network,
visit the
Requests for Comment (RFC)repository. While it's maintained by the Polkadot Fellowship, the RFC process welcomes contributions from everyone.