1. Jan 12, 2024
    • Dmitry Markin's avatar
      Extract warp sync strategy from `ChainSync` (#2467) · 5208bed7
      Dmitry Markin authored
      
      
      Extract `WarpSync` (and `StateSync` as part of warp sync) from
      `ChainSync` as independent syncing strategy called by `SyncingEngine`.
      Introduce `SyncingStrategy` enum as a proxy between `SyncingEngine` and
      specific syncing strategies.
      
      ## Limitations
      Gap sync is kept in `ChainSync` for now because it shares the same set
      of peers as block syncing implementation in `ChainSync`. Extraction of a
      common context responsible for peer management in syncing strategies
      able to run in parallel is planned for a follow-up PR.
      
      ## Further improvements
      A possibility of conversion of `SyncingStartegy` into a trait should be
      evaluated. The main stopper for this is that different strategies need
      to communicate different actions to `SyncingEngine` and respond to
      different events / provide different APIs (e.g., requesting
      justifications is only possible via `ChainSync` and not through
      `WarpSync`; `SendWarpProofRequest` action is only relevant to
      `WarpSync`, etc.)
      
      ---------
      
      Co-authored-by: default avatarAaro Altonen <[email protected]>
      5208bed7
    • Serban Iorga's avatar
      Kitchensink: Fix pallet_mmr config (#2919) · 868788a5
      Serban Iorga authored
      Related to https://github.com/paritytech/polkadot-sdk/issues/2787
      
      Fixes `pallet_mmr::Config` for the kitchensink runtime
      868788a5
  2. Jan 11, 2024
  3. Jan 10, 2024
  4. Jan 09, 2024
  5. Jan 08, 2024
  6. Jan 07, 2024
  7. Jan 06, 2024
  8. Jan 05, 2024
  9. Jan 04, 2024
  10. Jan 02, 2024
  11. Jan 01, 2024
  12. Dec 31, 2023
  13. Dec 29, 2023
    • Sergej Sakac's avatar
      Broker pallet: fix interlacing (#2811) · ae14e6da
      Sergej Sakac authored
      With the current code, when a user interlaces their region, the end
      result will be three regions in the state:
      - the non-interlaced region
      - first part of the interlaced region
      - second part of the interlaced region
      
      The existing implementation retains the non-interlaced region in the
      state, leading to a problematic scenario:
      
      1. User 1 acquires a region from the market.
      2. User 1 then interlaces this region.
      3. Subsequently, User 1 transfers one part of the interlaced regions to
      User 2.
      Despite this transfer, User 1 retains the ability to assign the entire
      original non-interlaced region, which is inconsistent with the fact that
      they no longer own one of the interlaced parts.
      
      This PR resolves the issue by removing the original region, ensuring
      that only the two new interlaced regions remain in the state.
      ae14e6da
  14. Dec 28, 2023
  15. Dec 27, 2023
  16. Dec 26, 2023
  17. Dec 23, 2023
  18. Dec 22, 2023