Skip to content
This repository was archived by the owner on Nov 15, 2023. It is now read-only.
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Don't deprecate Router but rather make it a meta-project
Co-authored-by: Bernhard Schuster <bernhard@ahoi.io>
  • Loading branch information
pepyakin and drahnr authored Nov 11, 2020
commit 3800729204833f0115b85d86de82bfdc37af5bb4
2 changes: 1 addition & 1 deletion roadmap/implementers-guide/src/glossary.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ Here you can find definitions of a bunch of jargon, usually specific to the Polk
- Parathread: A parachain which is scheduled on a pay-as-you-go basis.
- Proof-of-Validity (PoV): A stateless-client proof that a parachain candidate is valid, with respect to some validation function.
- Relay Parent: A block in the relay chain, referred to in a context where work is being done in the context of the state at this block.
- Router: The router module used to be a runtime module responsible for routing messages between paras and the relay chain. At some point it was split up into separate runtime modules: Dmp, Ump, Hrmp, each responsible for the respective part of message routing.
- Router: The router module is a meta module that consists of three runtime module responsible for routing messages between paras and the relay chain. The three separate separate runtime modules: Dmp, Ump, Hrmp, each responsible for the respective part of message routing.
Comment thread
pepyakin marked this conversation as resolved.
Outdated
- Runtime: The relay-chain state machine.
- Runtime Module: See Module.
- Runtime API: A means for the node-side behavior to access structured information based on the state of a fork of the blockchain.
Expand Down