Skip to content
  1. Apr 10, 2024
    • Hernando Castano's avatar
      Use GrandpaJustification instead of Vec<u8> in Pallet API (#847) · 67cdca8a
      Hernando Castano authored and Bastian Köcher's avatar Bastian Köcher committed
      * Stop passing raw encoded justifications to pallet API
      
      By having the API accept a struct-ified justification we are able to
      better utilize the justifications fields for weight calculations.
      
      * Update relayer code to use decoded justifications
      
      * Add justification to `expect()` statement
      
      * Fix some imports
      
      * Make justification wrapper contain decoded justification
      
      * Rename some fields
      
      * Get rid of warnings
      
      * Appease Clippy
      
      * Only decode justification once at init time
      
      * Remove unnecessary method
      
      * Remove justification wrapper
      
      This became kinda unnecessary since we could implement the FinalityProof
      trait on GrandpaJustification directly.
      67cdca8a
    • Hernando Castano's avatar
      Larger Test Keyring Support (#842) · 78a9cdca
      Hernando Castano authored and Bastian Köcher's avatar Bastian Köcher committed
      * Allow creation of authority lists with any number of authorities
      
      * Move keyring helpers into their own module
      
      * Add helper for generating list of test accounts
      
      * Fix import names in tests
      
      * Rename Keyring trait to Signer
      
      * Get list of accounts in a more functional way
      
      * Clarify meaning of `test_keyring` return type
      
      * Use concrete test account type instead of generics
      
      * Make sure voter set contains all authorities which signed off on pre-commits
      78a9cdca
    • Hernando Castano's avatar
      Rename Finality Verifier and Call Dispatch Pallets (#838) · 8d122b03
      Hernando Castano authored and Bastian Köcher's avatar Bastian Köcher committed
      * Rename `pallet-finality-verifier` to `pallet-bridge-grandpa`
      
      * Missed some CamelCase ones
      
      * Update logging target in GRANDPA pallet
      
      * Rename `pallet-bridge-call-dispatch` to `pallet-bridge-dispatch`
      
      * Rename the dispatch pallet folder
      
      * Update logging target in Dispatch pallet
      
      * Missed a couple
      
      * Format the repo
      
      * Stop listing individual pallets in Compose logs
      
      * Use correct pallet name in module doc comments
      
      * Add `pallet-bridge-dispatch` to README project layout
      
      * Sort crate names in TOML files
      
      * Rename `pallet-bridge-grandpa` runtime Call alias
      8d122b03
    • Serban Iorga's avatar
      Remove bridges subtree · 9a3e2c8c
      Serban Iorga authored and Bastian Köcher's avatar Bastian Köcher committed
      9a3e2c8c
  2. Apr 02, 2024
  3. Mar 26, 2024
    • Dcompoze's avatar
      Fix spelling mistakes across the whole repository (#3808) · 002d9260
      Dcompoze authored
      **Update:** Pushed additional changes based on the review comments.
      
      **This pull request fixes various spelling mistakes in this
      repository.**
      
      Most of the changes are contained in the first **3** commits:
      
      - `Fix spelling mistakes in comments and docs`
      
      - `Fix spelling mistakes in test names`
      
      - `Fix spelling mistakes in error messages, panic messages, logs and
      tracing`
      
      Other source code spelling mistakes are separated into individual
      commits for easier reviewing:
      
      - `Fix the spelling of 'authority'`
      
      - `Fix the spelling of 'REASONABLE_HEADERS_IN_JUSTIFICATION_ANCESTRY'`
      
      - `Fix the spelling of 'prev_enqueud_messages'`
      
      - `Fix the spelling of 'endpoint'`
      
      - `Fix the spelling of 'children'`
      
      - `Fix the spelling of 'PenpalSiblingSovereignAccount'`
      
      - `Fix the spelling of 'PenpalSudoAccount'`
      
      - `Fix the spelling of 'insufficient'`
      
      - `Fix the spelling of 'PalletXcmExtrinsicsBenchmark'`
      
      - `Fix the spelling of 'subtracted'`
      
      - `Fix the spelling of 'CandidatePendingAvailability'`
      
      - `Fix the spelling of 'exclusive'`
      
      - `Fix the spelling of 'until'`
      
      - `Fix the spelling of 'discriminator'`
      
      - `Fix the spelling of 'nonexistent'`
      
      - `Fix the spelling of 'subsystem'`
      
      - `Fix the spelling of 'indices'`
      
      - `Fix the spelling of 'committed'`
      
      - `Fix the spelling of 'topology'`
      
      - `Fix the spelling of 'response'`
      
      - `Fix the spelling of 'beneficiary'`
      
      - `Fix the spelling of 'formatted'`
      
      - `Fix the spelling of 'UNKNOWN_PROOF_REQUEST'`
      
      - `Fix the spelling of 'succeeded'`
      
      - `Fix the spelling of 'reopened'`
      
      - `Fix the spelling of 'proposer'`
      
      - `Fix the spelling of 'InstantiationNonce'`
      
      - `Fix the spelling of 'depositor'`
      
      - `Fix the spelling of 'expiration'`
      
      - `Fix the spelling of 'phantom'`
      
      - `Fix the spelling of 'AggregatedKeyValue'`
      
      - `Fix the spelling of 'randomness'`
      
      - `Fix the spelling of 'defendant'`
      
      - `Fix the spelling of 'AquaticMammal'`
      
      - `Fix the spelling of 'transactions'`
      
      - `Fix the spelling of 'PassingTracingSubscriber'`
      
      - `Fix the spelling of 'TxSignaturePayload'`
      
      - `Fix the spelling of 'versioning'`
      
      - `Fix the spelling of 'descendant'`
      
      - `Fix the spelling of 'overridden'`
      
      - `Fix the spelling of 'network'`
      
      Let me know if this structure is adequate.
      
      **Note:** The usage of the words `Merkle`, `Merkelize`, `Merklization`,
      `Merkelization`, `Merkleization`, is somewhat inconsistent but I left it
      as it is.
      
      ~~**Note:** In some places the term `Receival` is used to refer to
      message reception, IMO `Reception` is the correct word here, but I left
      it as it is.~~
      
      ~~**Note:** In some places the term `Overlayed` is used instead of the
      more acceptable version `Overlaid` but I also left it as it is.~~
      
      ~~**Note:** In some places the term `Applyable` is used instead of the
      correct version `Applicable` but I also left it as it is.~~
      
      **Note:** Some usage of British vs American english e.g. `judgement` vs
      `judgment`, `initialise` vs `initialize`, `optimise` vs `optimize` etc.
      are both present in different places, but I suppose that's
      understandable given the number of contributors.
      
      ~~**Note:** There is a spelling mistake in `.github/CODEOWNERS` but it
      triggers errors in CI when I make changes to it, so I left it as it
      is.~~
      002d9260
    • Serban Iorga's avatar
      Update bridges subtree (#3841) · b839c995
      Serban Iorga authored
      Updating the bridges subtree hopefully just one last time in this
      formula in order to make the final migration less verbose.
      b839c995
  4. Mar 17, 2024
  5. Mar 15, 2024
  6. Feb 12, 2024
  7. Feb 06, 2024
  8. Jan 26, 2024
  9. Jan 19, 2024
  10. Dec 13, 2023
  11. Dec 06, 2023
  12. Dec 01, 2023
  13. Nov 15, 2023
  14. Oct 20, 2023
    • Bastian Köcher's avatar
      `xcm`: Change `TypeInfo::path` to not include `staging` (#1948) · f3bf5c1a
      Bastian Köcher authored
      The `xcm` crate was renamed to `staging-xcm` to be able to publish it to
      crates.io as someone as squatted `xcm`. The problem with this rename is
      that the `TypeInfo` includes the crate name which ultimately lands in
      the metadata. The metadata is consumed by downstream users like
      `polkadot-js` or people building on top of `polkadot-js`. These people
      are using the entire `path` to find the type in the type registry. Thus,
      their code would break as the type path would now be [`staging_xcm`,
      `VersionedXcm`] instead of [`xcm`, `VersionedXcm`]. This pull request
      fixes this by renaming the path segment `staging_xcm` to `xcm`.
      
      This requires: https://github.com/paritytech/scale-info/pull/197
      
      
      
      ---------
      
      Co-authored-by: default avatarFrancisco Aguirre <[email protected]>
      f3bf5c1a
  15. Oct 17, 2023
  16. Oct 10, 2023
  17. Sep 15, 2023
  18. Sep 11, 2023
    • Lulu's avatar
      Set bridge crates to no-publish (#1488) · 00259b1c
      Lulu authored
      00259b1c
    • Serban Iorga's avatar
      Update bridges subtree (#1392) · 142a11ad
      Serban Iorga authored
      * Move the bridges subtree under root
      
      * Squashed 'bridges/' changes from 277f0d5496..e50398d1c5
      
      e50398d1c5 bridges subtree fixes (#2528)
      99af07522d Markdown linter (#1309) (#2526)
      733ff0fe7a `polkadot-staging` branch: Use polkadot-sdk dependencies (#2524)
      e8a59f141e Fix benchmark with new XCM::V3 `MAX_INSTRUCTIONS_TO_DECODE` (#2514)
      62b185de15 Backport `polkadot-sdk` changes to `polkadot-staging` (#2518)
      d9658f4d5b Fix equivocation detection containers startup (#2516) (#2517)
      d65db28a8f Backport: building images from locally built binaries (#2513)
      5fdbaf45f6 Start the equivocation detection loop from the complex relayer (#2507) (#2512)
      7fbb67de46 Backport: Implement basic equivocations detection loop (#2375)
      cb7efe245c Manually update deps in polkadot staging (#2371)
      d17981fc33 #2351 to polkadot-staging (#2359)
      
      git-subtree-dir: bridges
      git-subtree-split: e50398d1c594e4e96df70b0bd376e565d17e8558
      
      * Reapply diener workspacify
      
      * Fix Cargo.toml
      
      * Fix test
      
      * Adjustments
      142a11ad