Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • polkadot polkadot
  • Project information
    • Project information
    • Activity
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Insights
    • Repository
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • parityparity
  • Mirrored projectsMirrored projects
  • polkadotpolkadot
  • Repository
Switch branch/tag
  • polkadot
  • roadmap
  • implementers-guide
  • src
  • runtime
  • router.md
Find file BlameHistoryPermalink
  • Sergey Pepyakin's avatar
    Implementer's Guide: Flesh out more details for upward messages (#1556) · 73de27e0
    Sergey Pepyakin authored Aug 14, 2020
    
    
    * Take 2 at the upward messages
    
    * Trying to restore stuff from unsuccesful rebase
    
    * Fix whitespace
    
    * Clean up
    
    * Change rustdoc to comment
    
    * Pivot to a less stricter, w.r.t. to acceptance, model
    
    * Rename `max_upward_message_num_per_candidate`
    
    * Update docs for DownwardMessage
    
    * Apply suggestions from code review
    
    Co-authored-by: asynchronous rob's avatarRobert Habermeier <rphmeier@gmail.com>
    
    * Rephrase "Dispatchable objects ready to ..."
    
    * Finish the sentence
    
    * Add a note about imprecision of the current weight formula
    
    * Elaborate on potential use-cases for the upward message kinds.
    
    * s/later/below
    
    Co-authored-by: asynchronous rob's avatarRobert Habermeier <rphmeier@gmail.com>
    73de27e0