Skip to content
Snippets Groups Projects
Select Git revision
  • 8001
  • 8069
  • 8230
  • gh-readonly-queue/master/pr-7970-f3be5315d2bb93b7a91e8aba0bad0a79add8ae82 protected
  • master default protected
  • gh-readonly-queue/master/pr-8187-93852b12cd3401a1bbbe1067aab7ffa9eea80b54 protected
  • gh-readonly-queue/master/pr-7375-fc0fcbaecab7dc7e0c3a0ff380c8a81af8b7c48b protected
  • 7720
  • gh-readonly-queue/master/pr-8118-38e93b570f156068786150700e741b85af82cedb protected
  • 7321
  • 7944
  • 7567
  • 8229
  • 7902
  • 8234
  • 6010
  • 8226
  • 7948
  • 7882
  • 6994
20 results
Compare History
user avatar
add fallback request for req-response protocols (#2771)
Alin Dima authored 
Previously, it was only possible to retry the same request on a
different protocol name that had the exact same binary payloads.

Introduce a way of trying a different request on a different protocol if
the first one fails with Unsupported protocol.

This helps with adding new req-response versions in polkadot while
preserving compatibility with unupgraded nodes.

The way req-response protocols were bumped previously was that they were
bundled with some other notifications protocol upgrade, like for async
backing (but that is more complicated, especially if the feature does
not require any changes to a notifications protocol). Will be needed for
implementing https://github.com/polkadot-fellows/RFCs/pull/47

TODO:
- [x]  add tests
- [x] add guidance docs in polkadot about req-response protocol
versioning
f2a750ee
Name Last commit Last update
..
.config
.maintain
bin
client
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.