Skip to content
  1. Sep 05, 2022
  2. Sep 03, 2022
    • Dmitry Markin's avatar
      Use custom type for ProtocolName (#5963) · b3480bd5
      Dmitry Markin authored
      * Use new ProtocolName in peer_set.rs
      
      * Use new ProtocolName for request-response protocols
      
      * Use new ProtocolName in polkadot-network-bridge
      
      * Import and conversion fixes
      
      * Use ProtocolName re-exported in sc_network
      
      * update lockfile for {"substrate"}
      
      Co-authored-by: parity-processbot <>
      b3480bd5
  3. Sep 02, 2022
  4. Sep 01, 2022
    • Shawn Tabrizi's avatar
      Companion for Weight v1.5 Follow Up (#5949) · e28bf2e4
      Shawn Tabrizi authored
      * updates
      
      * remove new
      
      * fix up some stuff
      
      * fix cargo files
      
      * fix
      
      * fix template
      
      * update lockfile for {"substrate"}
      
      * Update block_weights.rs
      
      * remove unused
      
      * remove unused
      
      Co-authored-by: parity-processbot <>
      e28bf2e4
    • Roman Useinov's avatar
      [Feature] Make XCM benchmarks more reusable and remove a redundant bench (#5936) · 75d49dfe
      Roman Useinov authored
      * [Feature] Make XCM benchmarks more reusable and remove a redunant bench
      
      * implement track balances flag
      
      * little comment fix
      
      * Revert "little comment fix"
      
      This reverts commit 6d0d1bb4d74752aa518c4d71718c1b71673bcca8.
      
      * Revert "implement track balances flag"
      
      This reverts commit e7884cbc57d053c5d57a80aab4caa42e78cfdc17.
      
      * fix unused
      75d49dfe
    • Kian Paimani's avatar
      companion `try-state` (#5907) · f2020208
      Kian Paimani authored
      * bunch of changes for now
      
      * companion for sanity-checks
      
      * Fix
      
      * remove bridges
      
      * better logging
      
      * revert spec change
      
      * fmt
      
      * fix
      
      * update lockfile for {"substrate"}
      
      Co-authored-by: parity-processbot <>
      f2020208
    • Robert Klotzner's avatar
      Don't store available data on disputes (#5950) · 254582df
      Robert Klotzner authored
      
      
      * Don't store available data on disputes
      
      If there are lots of disputes, this leads to blowing up disk space on
      validators. Rob luckily remembered that we do store the full
      availability in participation.
      
      The argument in the code does not make too much sense with the current
      implementation, as no validator will ever request anything else from us,
      than the one piece we are meant to posess.
      
      * Fix warnings.
      
      * Fix compile warnings
      
      * Remove redundant field.
      
      Co-authored-by: default avatarVsevolod Stakhov <[email protected]>
      254582df
  5. Aug 31, 2022
    • Shawn Tabrizi's avatar
      Companion for Weight v1.5 (#5943) · 28e94d97
      Shawn Tabrizi authored
      * fix to latest substrate pr
      
      * update weights
      
      * cargo build -p polkadot-runtime-parachains
      
      * fix xcm-builder
      
      * fix import
      
      * fix a bunch
      
      * fix a bunch of weight stuff
      
      * kusama compile
      
      * unused
      
      * builds
      
      * maybe fix
      
      * cargo test -p polkadot-runtime-parachains
      
      * xcm simulator example
      
      * fix tests
      
      * xcm sim fuzz
      
      * fix runtime tests
      
      * remove unused
      
      * fix integration tests
      
      * scalar div
      
      * update lockfile for {"substrate"}
      
      Co-authored-by: parity-processbot <>
      28e94d97
  6. Aug 30, 2022
  7. Aug 29, 2022
  8. Aug 28, 2022
  9. Aug 26, 2022
  10. Aug 25, 2022
  11. Aug 24, 2022
  12. Aug 23, 2022
  13. Aug 22, 2022
  14. Aug 18, 2022
    • Bastian Köcher's avatar
      Companion for new Trie cache (#5897) · c3404d10
      Bastian Köcher authored
      * Switch to Substrate branch
      
      * Make everything compile
      
      * Revert "Switch to Substrate branch"
      
      This reverts commit cbbab7431a07cfd645428a9f4c130362a8e7588b.
      
      * Remove stuff
      
      * More fixes
      
      * Fix branch
      
      * Update Substrate
      
      * FMT
      c3404d10
  15. Aug 17, 2022
  16. Aug 16, 2022
    • Shawn Tabrizi's avatar
      Governance 2 (Part 1, Non-Controversial Changes) (#5892) · 1f0a1cc0
      Shawn Tabrizi authored
      
      
      * initial stuff
      
      * make copy data from kusama
      
      * Update runtime/kusama/src/governance/old.rs
      
      Co-authored-by: default avatarBastian Köcher <[email protected]>
      
      * Update runtime/kusama/src/governance/mod.rs
      
      Co-authored-by: default avatarBastian Köcher <[email protected]>
      
      Co-authored-by: default avatarBastian Köcher <[email protected]>
      1f0a1cc0
    • Joakim Nyman's avatar
    • Robert Klotzner's avatar
      16a35652
    • Robert Klotzner's avatar
      Don't request votes if there is nothing to request. (#5888) · 05a79665
      Robert Klotzner authored
      * Don't request votes if there is nothing to request.
      
      * Add trace log
      05a79665
    • Robert Klotzner's avatar
      Reduce dispute coordinator load (#5785) · ca6297c8
      Robert Klotzner authored
      
      
      * Don't import backing statements directly
      
      into the dispute coordinator. This also gets rid of a redundant
      signature check. Both should have some impact on backing performance.
      In general this PR should make us scale better in the number of parachains.
      
      Reasoning (aka why this is fine):
      
      For the signature check: As mentioned, it is a redundant check. The
      signature has already been checked at this point. This is even made
      obvious by the used types. The smart constructor is not perfect as
      discussed [here](https://github.com/paritytech/polkadot/issues/3455),
      but is still a reasonable security.
      
      For not importing to the dispute-coordinator: This should be good as the
      dispute coordinator does scrape backing votes from chain. This suffices
      in practice as a super majority of validators must have seen a backing
      fork in order for a candidate to get included and only included
      candidates pose a threat to our system. The import from chain is
      preferable over direct import of backing votes for two reasons:
      
      1. The import is batched, greatly improving import performance. All
         backing votes for a candidate are imported with a single import.
         And indeed we were able to see in metrics that importing votes
         from chain is fast.
      2. We do less work in general as not every candidate for which
         statements are gossiped might actually make it on a chain. The
         dispute coordinator as with the current implementation would still
         import and keep those votes around for six sessions.
      
      While redundancy is good for reliability in the event of bugs, this also
      comes at a non negligible cost. The dispute-coordinator right now is the
      subsystem with the highest load, despite the fact that it should not be
      doing much during mormal operation and it is only getting worse
      with more parachains as the load is a direct function of the number of statements.
      
      We'll see on Versi how much of a performance improvement this PR
      
      * Get rid of dead code.
      
      * Dont send approval vote
      
      * Make it pass CI
      
      * Bring back tests for fixing them later.
      
      * Explicit signature check.
      
      * Resurrect approval-voting tests (not fixed yet)
      
      * Send out approval votes in dispute-distribution.
      
      Use BTreeMap for ordered dispute votes.
      
      * Bring back an important warning.
      
      * Fix approval voting tests.
      
      * Don't send out dispute message on import + test
      
      + Some cleanup.
      
      * Guide changes.
      
      Note that the introduced complexity is actually redundant.
      
      * WIP: guide changes.
      
      * Finish guide changes about dispute-coordinator
      
      conceputally. Requires more proof read still.
      
      Also removed obsolete implementation details, where the code is better
      suited as the source of truth.
      
      * Finish guide changes for now.
      
      * Remove own approval vote import logic.
      
      * Implement logic for retrieving approval-votes
      
      into approval-voting and approval-distribution subsystems.
      
      * Update roadmap/implementers-guide/src/node/disputes/dispute-coordinator.md
      
      Co-authored-by: default avatarasynchronous rob <[email protected]>
      
      * Review feedback.
      
      In particular: Add note about disputes of non included candidates.
      
      * Incorporate Review Remarks
      
      * Get rid of superfluous space.
      
      * Tidy up import logic a bit.
      
      Logical vote import is now separated, making the code more readable and
      maintainable.
      
      Also: Accept import if there is at least one invalid signer that has not
      exceeded its spam slots, instead of requiring all of them to not exceed
      their limits. This is more correct and a preparation for vote batching.
      
      * We don't need/have empty imports.
      
      * Fix tests and bugs.
      
      * Remove error prone redundancy.
      
      * Import approval votes on dispute initiated/concluded.
      
      * Add test for approval vote import.
      
      * Make guide checker happy (hopefully)
      
      * Another sanity check + better logs.
      
      * Reasoning about boundedness.
      
      * Use `CandidateIndex` as opposed to `CoreIndex`.
      
      * Remove redundant import.
      
      * Review remarks.
      
      * Add metric for calls to request signatures
      
      * More review remarks.
      
      * Add metric on imported approval votes.
      
      * Include candidate hash in logs.
      
      * More trace log
      
      * Break cycle.
      
      * Add some tracing.
      
      * Cleanup allowed messages.
      
      * fmt
      
      * Tracing + timeout for get inherent data.
      
      * Better error.
      
      * Break cycle in all places.
      
      * Clarified comment some more.
      
      * Typo.
      
      * Break cycle approval-distribution - approval-voting.
      
      Co-authored-by: default avatarasynchronous rob <[email protected]>
      ca6297c8
  17. Aug 15, 2022