Skip to content
  1. Feb 05, 2022
  2. Feb 04, 2022
  3. Feb 03, 2022
  4. Feb 02, 2022
  5. Feb 01, 2022
  6. Jan 31, 2022
  7. Jan 28, 2022
  8. Jan 27, 2022
    • Davide Galassi's avatar
      Add stale branches heads to finality notifications (#10639) · 7f3bb8d0
      Davide Galassi authored
      
      
      * Add stale branches heads to finality notifications
      
      Warning. Previous implementation was sending a notification for
      each block between the previous (explicitly) finalized block and
      the new finalized one (with an hardcoded limit of 256).
      
      Now finality notification is sent only for the new finalized head and it
      contains the hash of the new finalized head, new finalized head header,
      a list of all the implicitly finalized blocks and a list of stale
      branches heads (i.e. the branches heads that are not part of the
      canonical chain anymore).
      
      * Add implicitly finalized blocks list to `ChainEvent::Finalized` message
      
      The list contains all the blocks between the previously finalized block
      up to the parent of the currently finalized one, sorted by block number.
      
      `Finalized` messages handler, part of the `MaintainedTransactionPool`
      implementation for `BasicPool`, still propagate full set of finalized
      blocks to the txpool by iterating over implicitly finalized blocks list.
      
      * Rust fmt
      
      * Greedy evaluation of `stale_heads` during finalization
      
      * Fix outdated assumption in a comment
      
      * Removed a test optimization that is no more relevant
      
      The loop was there to prevent sending to
      `peer.network.on_block_finalized` the full list of finalized blocks.
      
      Now only the finalized heads are received.
      
      * Last finalized block lookup not required anymore
      
      * Tests for block finality notifications payloads
      
      * Document a bit tricky condition to avoid duplicate finalization notifications
      
      * More idiomatic way to skip an iterator entry
      
      Co-authored-by: default avatarBastian Köcher <[email protected]>
      
      * Cargo fmt iteration
      
      * Typo fix
      
      Co-authored-by: default avatarBastian Köcher <[email protected]>
      
      * Fix potential failure when a finalized orphan block is imported
      
      * Apply suggestions from code review
      
      Co-authored-by: default avatarBastian Köcher <[email protected]>
      
      * Apply suggestions from code review
      
      Co-authored-by: default avatarBastian Köcher <[email protected]>
      
      Co-authored-by: default avatarBastian Köcher <[email protected]>
      7f3bb8d0
    • Kian Paimani's avatar
      better way to resolve `Phase::Emergency` via governance (#10663) · 498c3a5e
      Kian Paimani authored
      
      
      * better way to resolve Phase::Emergency via governance
      
      * Update frame/election-provider-multi-phase/src/lib.rs
      
      Co-authored-by: default avatarZeke Mostov <[email protected]>
      
      * review grumbles
      
      * Update frame/election-provider-support/src/onchain.rs
      
      Co-authored-by: default avatarShawn Tabrizi <[email protected]>
      
      * revert usize -> u32
      
      Co-authored-by: default avatarZeke Mostov <[email protected]>
      Co-authored-by: default avatarShawn Tabrizi <[email protected]>
      498c3a5e
  9. Jan 26, 2022
  10. Jan 25, 2022
  11. Jan 24, 2022
  12. Jan 22, 2022
  13. Jan 21, 2022