Skip to content
  1. Feb 22, 2022
  2. Feb 18, 2022
  3. Feb 11, 2022
  4. Feb 09, 2022
  5. Feb 08, 2022
  6. Feb 07, 2022
  7. Feb 02, 2022
  8. Jan 26, 2022
  9. Jan 18, 2022
  10. Jan 13, 2022
  11. Jan 10, 2022
  12. Jan 07, 2022
    • Sergey Pepyakin's avatar
      pvf-precheck: PVF pre-checker subsystem (#4643) · d752f866
      Sergey Pepyakin authored
      This commit implements the last major piece of #3211: the subsystem that
      tracks PVFs that require voting, issues pre-check requests to
      candidate-validation and makes sure that the votes are submitted to the
      chain.
      d752f866
  13. Jan 06, 2022
    • Adrian Catangiu's avatar
      Companion for Substrate#10568 - Add new BEEFY RPC (#4638) · 5cc5b674
      Adrian Catangiu authored
      * support best Beefy RPC through arc<mutex>
      
      * beefy RPC through lockless message passing - wip
      
      Not working because channel can't be simply opened and receiver passed
      to `rpc_extensions_builder` because `rpc_extensions_builder` has to be
      `Fn` and not `FnOnce`... and and Receiver side of mpsc can't be cloned
      
      yay!..
      
      * beefy RPC through lockless message passing
      
      * beefy: use specialized type definitions
      
      * bubble up service errors from BEEFY RPC
      
      * update lockfile for substrate
      
      Co-authored-by: parity-processbot <>
      5cc5b674
  14. Jan 05, 2022
  15. Dec 30, 2021
  16. Dec 28, 2021
  17. Dec 27, 2021
    • Sergey Pepyakin's avatar
      configuration: Unified consistency checks (#4581) · 4d768787
      Sergey Pepyakin authored
      This commit refactors the consistency checks. Instead of each individual
      setter performs its checks locally, we delegate those checks to the
      already existing function `check_consistency`. This removes duplication
      and simplifies the logic.
      
      A motivating example of this one is the next PR in the stack that will
      introduce a check for a field, which validity depends on the validity of
      other two fields. Without this refactoring we will have to place a check
      not only to the field in question, but also to the other two fields so
      that if they are changed they do not violate consistency criteria. It's
      easy to imagine how this can go unwieldy with the number of checks.
      
      This also adds a test that verifies that the default chain spec host
      configuration is consistent.
      4d768787
    • ordian's avatar
      session-info: add new fields + migration (#4545) · b342ae11
      ordian authored
      
      
      * session_info: v2 + migration
      
      * use primitives::v2
      
      * use polkadot_primitives::v2
      
      * impl primitives::v2
      
      * fix approval-voting tests
      
      * fix other tests
      
      * hook storage migration up
      
      * backwards compat (1)
      
      * backwards compat (2)
      
      * fmt
      
      * fix tests
      
      * FMT
      
      * do not reexport v1 in v2
      
      * fmt
      
      * set storage version to 1
      
      Co-authored-by: default avatarJavier Viola <[email protected]>
      b342ae11
  18. Dec 25, 2021
  19. Dec 20, 2021
  20. Dec 18, 2021
  21. Dec 17, 2021
  22. Dec 16, 2021
  23. Dec 14, 2021
  24. Dec 11, 2021
  25. Dec 10, 2021
  26. Dec 09, 2021
  27. Dec 07, 2021