1. Jan 19, 2023
  2. Jan 18, 2023
  3. Jan 17, 2023
  4. Jan 16, 2023
  5. Jan 13, 2023
    • Branislav Kontur's avatar
      Bump xcm-v3 + substrate (#1767) · 6fc931d0
      Branislav Kontur authored
      
      
      * Bump xcm-v3 + substrate
      
      * More fixes
      
      * Added `#[pallet::call_index`
      
      * Fixes for MMR (TODO:plese check)
      
      * More call indexes
      
      * Cumulus bump
      
      * Fixes for mmr
      
      * Fixes for weights
      
      * Fixes for xcm
      
      * MMR fixes + cargo fmt
      
      * Fix some rpc errors (bump jsonrpsee version)
      
      * Fix cumulus stuff
      
      * Fixes cumulus
      
      * clippy
      
      * more clipy
      
      * Fix test + unused deps
      
      * PR fixes
      
      * cargo update (bump xcm-v3)
      
      Co-authored-by: default avatarSerban Iorga <[email protected]>
      6fc931d0
  6. Jan 12, 2023
  7. Jan 11, 2023
  8. Jan 10, 2023
  9. Jan 09, 2023
  10. Jan 04, 2023
  11. Dec 30, 2022
  12. Dec 29, 2022
  13. Dec 28, 2022
  14. Dec 27, 2022
    • Serban Iorga's avatar
      Replace `BATCH_CALL_SUPPORTED` (#1733) · b9050e90
      Serban Iorga authored
      * Simplify submit_and_watch_signed_extrinsic
      
      The way submit_and_watch_signed_extrinsic is used now, we can always
      derive the SignParam from other params. If in the future we need more
      customization possibilities, we can define a new method.
      
      * Simplify submit_signed_extrinsic
      
      * Send maybe_batch_tx as a parameter
      
      Send `maybe_batch_tx` as a parameter to `submit_proof()`. This way we
      can deduplicate the logic that submits the extrinsic for
      `messages_source and `messages_target` and we can simplify the logic in
      the race loop a bit.
      
      * Define BatchProofTransaction
      
      Deduplicate BatchConfirmationTransaction and BatchDeliveryTransaction by
      replacing both of them with BatchProofTransaction
      
      * Define ChainWithUtilityPallet and BatchCallBuilderConstructor
      
      - Define `ChainWithUtilityPallet` in order to be able to associate the
        batching functionality with chains
      - Defining `BatchCallBuilderConstructor` in order to have a more reliable
        way of checking whether an end of a messages pipeline supports batching
        or no. `BatchCallBuilderConstructor::new_builder()` returns an
        `Option<BatchCallBuilder>`.This is a bit safer because each time a caller
        tries to start creating a batch call, it will call `new_builder()` and
        will be required to handle the returned `Option`. Before we only had a
        bool `BATCH_CALL_SUPPORTED` the caller could have forgetten to check.
      b9050e90
  15. Dec 22, 2022
  16. Dec 21, 2022
  17. Dec 19, 2022